Fix for SessionHandlerTestBase#doTestSessionRetryTimeout

Since session flushing is an asynchronous process, the session data may not be removed from the store when the next request is handled.

With manual flushing, we make sure the session store has destroyed the data before responding to the request.
So the next one never gets stale session data.

This will help with Infinispan SharedData map session store testing.

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

vertx-web/src/test/java/io/vertx/ext/web/tests/handler/SessionHandlerTestBase.java

@@ -359,7 +359,8 @@ public void testSessionCookieInvalidatedOnError() throws Exception {
 	}
 
 	protected long doTestSessionRetryTimeout() throws Exception {
-		router.route().handler(SessionHandler.create(store));
+    SessionHandler sessionHandler = SessionHandler.create(store);
+		router.route().handler(sessionHandler);
 		AtomicReference<Session> rid = new AtomicReference<>();
 
 		router.get("/0").handler(rc -> {
@@ -370,8 +371,8 @@ protected long doTestSessionRetryTimeout() throws Exception {
 		router.get("/1").handler(rc -> {
 			rid.set(rc.session());
 			assertEquals("foo_value", rc.session().get("foo"));
-			rc.session().destroy();
-			rc.response().end();
+      rc.session().destroy();
+      sessionHandler.flush(rc).onComplete(v -> rc.response().end(), rc::fail);
 		});
 		router.get("/2").handler(rc -> {
 			rid.set(rc.session());