Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EJBCLIENT-324] Fix Phantom NoSuchEJBExceptions and retry mechanism #387

Merged
merged 1 commit into from
Apr 4, 2019

Conversation

rachmatowicz
Copy link
Contributor

This PR addresses the issue described in: https://issues.jboss.org/browse/EJBCLIENT-324

@rachmatowicz
Copy link
Contributor Author

rachmatowicz commented Apr 3, 2019

This test causes one test in EAP clustering testsuite to fail:

[INFO] Running org.jboss.as.test.clustering.cluster.ejb2.stateless.RemoteStatelessFailoverTestCase
[ERROR] Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 108.076 s <<< FAILURE! - in org.jboss.as.test.clustering.cluster.ejb2.stateless.RemoteStatelessFailoverTestCase
[ERROR] testFailoverOnUndeployAnnotatedBean(org.jboss.as.test.clustering.cluster.ejb2.stateless.RemoteStatelessFailoverTestCase) Time elapsed: 11.461 s <<< ERROR!
javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/RemoteStatelessFailoverTestCase/StatelessBean", view is interface org.jboss.as.test.clustering.cluster.ejb2.stateless.bean.StatelessRemoteHome, affinity is Cluster "ejb"
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:607)

However, when running the failing test in isolation, it passes. It looks as though the DNR is being contaminated from a previous test, so that the test starts out with a non-empty DNR, which is incorrect. Will investigate.

@tadamski tadamski merged commit 32ecc4f into wildfly:4.0 Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants