[jboss-jira] [JBoss JIRA] (WFLY-3316) Multi threaded ejb invocations via remote-naming produce EJBCLIENT000025 if the Context is closed

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025204#comment-13025204 ] 

RH Bugzilla Integration commented on WFLY-3316:
-----------------------------------------------

Enrique Gonzalez Martinez <egonzale at redhat.com> changed the Status of [bug 1094380|https://bugzilla.redhat.com/show_bug.cgi?id=1094380] from ASSIGNED to POST

> 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
>         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
(v6.3.8#6338)