-
Bug
-
Resolution: Done
-
Critical
-
7.1.0.DR12, 7.1.0.DR15, 7.1.0.ER2
-
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?
- is related to
-
JBEAP-10963 Wrong URI protocol in EJB client context produces StackOverflowException with EJB Client 4
- Closed
-
JBEAP-12439 Elytron failed authentication results in different exceptions for stateless and stateful EJBs
- Closed
-
JBEAP-12415 Unhelpful error message from EJB client when wrong OAUTHBEARER token is used
- Closed
-
JBEAP-12416 [GSS](7.1.z) EJBCLIENT-293 - EJB client exception when authentication fails is too long
- Closed
- relates to
-
JBEAP-9967 EJB client doesn't work with connections configured in wildfly-config.xml
- Closed