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

Unhelpful error messages from EJB client

XMLWordPrintable

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

      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?

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

              Created:
              Updated:
              Resolved: