[jboss-jira] [JBoss JIRA] (WFLY-3316) Multi threaded ejb invocations via remote-naming produce EJBCLIENT000025 if the Context is closed
Kabir Khan (JIRA)
issues at jboss.org
Wed Dec 6 12:27:06 EST 2017
[ https://issues.jboss.org/browse/WFLY-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kabir Khan updated WFLY-3316:
-----------------------------
Fix Version/s: 11.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Multi threaded ejb invocations via remote-naming produce EJBCLIENT000025 if the Context is closed
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-3316
> URL: https://issues.jboss.org/browse/WFLY-3316
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.0.0.Final
> Reporter: Wolf-Dieter Fink
> Assignee: Enrique González Martínez
> Labels: ejb, naming, remote-clients, remote-ejb-connection
> Fix For: 11.0.0.Final
>
> Attachments: reproducer.zip
>
>
> If a client run multi threads and each Thread use it's own InitialContext the behaviour is unexpected.
> The behaviour is as followed:
> if each invocation create it's own IC and lookup the EJB there is sometimes a EJBCLIENT000025 because one of the one thread has closed the IC until another thread try to invoke an EJB.
> If the IC is reused the failure might happen only if the first Thread has finished the invocations and close the IC during other Threads are still running.
> It looks that the underlying remote connection will be closed if the first IC is closed without respect that there are different IC's created and still in use.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list