Reduce number of connections made in testConnectNoLeak tests

We only need a few of them to verify whether there is a leak.
And we avoid putting to much pressure on the Oracle test DB.

Signed-off-by: Thomas Segismont <[email protected]>

Author: tsegismont

vertx-sql-client/src/test/java/io/vertx/sqlclient/tck/ConnectionTestBase.java

@@ -58,8 +58,8 @@ public void testConnect(TestContext ctx) {
   public void testConnectNoLeak(TestContext ctx) throws Exception {
     Set<SqlConnectionBase<?>> connections = Collections.synchronizedSet(Collections.newSetFromMap(new WeakHashMap<>()));
     Set<ConnectionFactory> factories = Collections.synchronizedSet(Collections.newSetFromMap(new WeakHashMap<>()));
-    Async async = ctx.async(100);
-    for (int i = 0; i < 100; i++) {
+    Async async = ctx.async(10);
+    for (int i = 0; i < 10; i++) {
       connect(ctx.asyncAssertSuccess(conn -> {
         SqlConnectionBase<?> base = (SqlConnectionBase<?>) conn;
         connections.add(base);
@@ -80,11 +80,11 @@ public void testConnectNoLeak(TestContext ctx) throws Exception {
   public void testConnectNoLeakInVerticle(TestContext ctx) throws Exception {
     Set<SqlConnectionBase<?>> connections = Collections.synchronizedSet(Collections.newSetFromMap(new WeakHashMap<>()));
     Set<ConnectionFactory> factories = Collections.synchronizedSet(Collections.newSetFromMap(new WeakHashMap<>()));
-    Async async = ctx.async(100);
+    Async async = ctx.async(10);
     vertx.deployVerticle(new AbstractVerticle() {
       @Override
       public void start() throws Exception {
-        for (int i = 0; i < 100; i++) {
+        for (int i = 0; i < 10; i++) {
           connect(ctx.asyncAssertSuccess(conn -> {
             SqlConnectionBase<?> base = (SqlConnectionBase<?>) conn;
             connections.add(base);