-
Bug
-
Resolution: Obsolete
-
Major
-
7.0.1.GA
If EJB invocations can't be completed the ejb-client mark the channel/connection as broken and therefore a hickup is seen in the logfiles. If it is a single server there might be some invocations rejected with an EJBCLIENT000025 failure.
The client should make a difference for logical issues and not invalidate the channel/connection.
The log might show an error and after that the server is not available, the messages look like this:
DEBUG org.jboss.ejb.client.EJBClientContext: MyServer is excluded from handling appname=,modulename=myEJB,distinctname= in invocation context org.jboss.ejb.client.EJBClientInvocationContext@4b66500b
- clones
-
JBEAP-5413 [GSS](7.1.0) EJB client unnecessary mark a channel/connection as broken if can't read a message
- Verified
- incorporates
-
EJBCLIENT-162 EJB client unnecessary mark a channel/connection as broken if can't read a message
- Resolved
- is incorporated by
-
JBEAP-9963 [GSS](7.0.z) Upgrade ejb-client from 2.1.8 to 2.1.9
- Closed