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

[BZ-1094380] Multi threaded ejb invocations via remote-naming produce EJBCLIENT000025 if the Context is closed #23

Merged
merged 1 commit into from Mar 12, 2015

Conversation

@elguardian
Copy link
Contributor

commented Dec 4, 2014

Adding the EJBClientHandler to the CacheKey for avoiding mixing
EJBClientContext among threads if the flag "jboss.naming.client.ejb.context" in the properties is set to "true"
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1094380
Jira: https://issues.jboss.org/browse/WFLY-3316

EJBCLIENT000025 if the Context is closed
Adding the EJBClientHandler to the CacheKey for avoiding mixing
EJBClientContext among threads if the flag
"jboss.naming.client.ejb.context" in the properties is set to "true"
dmlloyd added a commit that referenced this pull request Mar 12, 2015
[BZ-1094380] Multi threaded ejb invocations via remote-naming produce EJBCLIENT000025 if the Context is closed
@dmlloyd dmlloyd merged commit 103426b into jbossas:1.0 Mar 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.