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

Unhelpful error messages from EJB client

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.1.0.ER2
    • 7.1.0.DR12, 7.1.0.DR15, 7.1.0.ER2
    • EJB, User Experience
    • None
    • User Experience

    Description

      Error messages from EJB client currently provide little to no hints about what might be wrong.
      When an EJB lookup fails, usually the only message you might get is:

       EJBCLIENT000024: Not able to find EJB matching "StatelessEJBLocator for "/basic-echo-test/EchoBeanStateless", view is interface org.jboss.qa.ejbclient.tests.echo.echobean.EchoBeanRemote, affinity is None"

      or for stateful beans the equivalent is:

       EJBCLIENT000062: Failed to look up "/basic-echo-test//EchoBeanStateful!org.jboss.qa.ejbclient.tests.echo.echobean.EchoBeanRemote?stateful"

      This should provide some more hints about what happened:

      • Was the connection refused by the remote machine?
      • Was authentication rejected?
      • Is there no deployment of this name on the server?
      • Is there such deployment, but no such EJB in it?

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10963 Wrong URI protocol in EJB client context produces StackOverflowException with EJB Client 4

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12439 Elytron failed authentication results in different exceptions for stateless and stateful EJBs

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12415 Unhelpful error message from EJB client when wrong OAUTHBEARER token is used

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12416 [GSS](7.1.z) EJBCLIENT-293 - EJB client exception when authentication fails is too long

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9967 EJB client doesn't work with connections configured in wildfly-config.xml

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              dlloyd@redhat.com David Lloyd
              jmartisk@redhat.com Jan Martiska
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: