Do not hold connection lock while closing channels
Please include more detailed description of the problem linked commit is solving.
SET/GSS - please provide automated test (as discussed on triage) to increase CP throughput.
I will qa_ack afterwards or when the scope of CP01 is clear and we have enough seats.
Please include more detailed description of the problem which is soled by linked commit.
FYI - there is no customer case attached to this BZ.
*** Bug 1230067 has been marked as a duplicate of this bug. ***
Verified with EAP 6.4.2.CP.CR1.
Note: I believe that there are still situations in which an exception during closing may cause a hang. E.g. the `closeAsync` method might be modified in the same way, and maybe it should. I posted a comment in the upstream JIRA (and if I get no reaction, I will open a new upstream JIRA).
That said, I also believe that the patches here _do_ fix a certain class of problems, hence VERIFIED.
Verification note: put `if (true) throw new RuntimeException("!TEST!");` at the beginning of org.jboss.remoting3.ConnectionImpl.closeAction to simulate a problem (it can't happen on this exact place normally, but it's a good enough approximation). Then, run a simple program that invokes a remote EJB. It hangs with Remoting 3.3.4 and it finishes successfully with Remoting 3.3.5. It's enough to change Remoting on the client, no need to change it on the server.
*** Bug 1248299 has been marked as a duplicate of this bug. ***
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.