Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-5413

[GSS](7.1.0) EJB client unnecessary mark a channel/connection as broken if can't read a message

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.DR14
    • 7.1.0.DR1
    • EJB
    • None

      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

              dlloyd@redhat.com David Lloyd
              rhn-support-wfink Wolf Fink
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: