-
Bug
-
Resolution: Done
-
Critical
-
7.1.0.DR19, 7.1.0.ER1, 7.2.0.GA.CR1
-
User Experience
-
-
-
-
-
-
+
-
When an EJB client application defines a connection URI with protocol with no such corresponding connector on remote side of connection, it freezes up.
This also affects EJBs deployed on one server remotely looking up EJBs on other server, however in such case the whole server gets locked up.
- is blocked by
-
JBEAP-16716 (7.2.z) WFDISC-34 - Add ability to perform a service discovery with timeout
- Closed
- is incorporated by
-
JBEAP-16370 [GSS](7.2.z) Upgrade jboss-ejb-client from 4.0.15 to 4.0.18
- Closed
- is related to
-
JBEAP-10996 org.jboss.remoting3.RemotingOptions.SASL_PROTOCOL make ejb client call hang
- Closed
-
JBEAP-10963 Wrong URI protocol in EJB client context produces StackOverflowException with EJB Client 4
- Closed
-
EJBCLIENT-311 Add timeout for discovering the destination of an EJB request
- Resolved
-
WFDISC-34 Add ability to perform a service discovery with timeout
- Resolved