Bug 1360391 - [GSS](6.4.z) EJB client unnecessary mark a channel/connection as broken if can't read a message
Summary: [GSS](6.4.z) EJB client unnecessary mark a channel/connection as broken if ca...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.3.3,6.4.0,6.3.4,6.4.1,6.4.2,6.4.3,6.4.4,6.4.5,6.4.6,6.4.7,6.4.8,6.4.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.19
Assignee: Radovan STANCEL
QA Contact: Jan Martiska
URL:
Whiteboard:
Depends On:
Blocks: 1436786 eap6419-payload
TreeView+ depends on / blocked
 
Reported: 2016-07-26 14:55 UTC by wfink
Modified: 2019-11-14 08:48 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-16 11:05:28 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EJBCLIENT-162 0 Major Resolved EJB client unnecessary mark a channel/connection as broken if can't read a message 2019-06-25 03:10:21 UTC
Red Hat Issue Tracker JBEAP-5411 0 Major Closed [GSS](7.0.z) EJB client unnecessary mark a channel/connection as broken if can't read a message 2019-06-25 03:10:21 UTC
Red Hat Issue Tracker JBEAP-5413 0 Major Verified [GSS](7.1.0) EJB client unnecessary mark a channel/connection as broken if can't read a message 2019-06-25 03:10:21 UTC
Red Hat Knowledge Base (Solution) 2464611 0 None None None 2016-07-26 15:12:31 UTC

Description wfink 2016-07-26 14:55:32 UTC 
Description of problem:

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

Actual results:
Further EJB invocations are rejected with EJBCLIENT0025 for a time until the connection is re-established.

Expected results:
Log the current failure and Continue with the channel/connection without further errors.
Comment 5 Jiří Bílek 2018-01-24 10:07:21 UTC 
Verified with EAP 6.4.19.CP.CR2
Note You need to log in before you can comment on or make changes to this bug.