-
Bug
-
Resolution: Won't Do
-
Blocker
-
None
-
7.1.0.DR16
We have following test scenario:
1) transaction is started on a client side (userTransaction.begin())
2) remote ejb call is invoked (updates db)
3) server is commanded to gracefully shutdown with 60s timeout
4) another remote call is invoked (in the same transaction as the first one)
5) transaction commit
but in the step 4) we get "java.net.ConnectException: Connection refused" because server doesn't wait on "in flight transaction" and stops immediately.
Another test (serverShouldNotRefuseSameTx) scenario is similar but before commanding the server to shutdown (with 60s timeout) another remote ejb call is invoked from another thread which only does Thread.sleep for 50s in order to keep server alive. But next remote ejb call is also not proceeds to the server.