After a connection failure, like server restart, the client need to reconnect with the next invocation attempt.
During this phase it happen that the first thread will start the reconnect and wait for the result. The second thread detect that the reconnects are started and skip this.
Unfortunately this cause errors as the thread is not blocked until the first connection is available again.
Failure of inocation with ERROR messages
Wait until connections are available, or fail if reconnect failed
Richard Achmatowicz <firstname.lastname@example.org> updated the status of jira EJBCLIENT-121 to Coding In Progress
Verified in EAP 6.4.0.ER1.