[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-881) IsLocalInterceptor not detecting local container after failover

[Brian Stansberry (JIRA)]

     [ http://jira.jboss.com/jira/browse/EJBTHREE-881?page=all ]

Brian Stansberry updated EJBTHREE-881:
--------------------------------------

    Fix Version/s: AS 4.2.0 CR2
      Description: 
Some unit tests I've written are showing a problem with nested SFSBs where the IsLocalInterceptor doesn't treat a call from a parent SFSB to a nested SFSB as local, but Remoting still handles it locally. This leads to an exception in the transaction propagation handling.

See forum thread for details.

  was:
Some unit tests I've written are showing a problem with nested SFSBs where the IsLocalInterceptor doesn't treat a call from a parent SFSB to a nested SFSB as local, but Remoting optimizes it locally. This leads to an exception in the transaction propagation handling.

What's strange is for the call that fails AFAICT IsLocalInterceptor and AOPRemotingInvocationHandler are both dealing with Dispatcher using the same Invocation and the same metadata. But when IsLocalInterceptor queries Dispatcher, it says the container isn't registered, while when AOPRemotingInvocationHandler asks Dispatcher to handle the invocation, it finds the container just fine. 

See forum thread for details.


> IsLocalInterceptor not detecting local container after failover
> ---------------------------------------------------------------
>
>                 Key: EJBTHREE-881
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-881
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: EJB 3.0 RC9 - Patch 1
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: AS 4.2.0 CR2
>
>
> Some unit tests I've written are showing a problem with nested SFSBs where the IsLocalInterceptor doesn't treat a call from a parent SFSB to a nested SFSB as local, but Remoting still handles it locally. This leads to an exception in the transaction propagation handling.
> See forum thread for details.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira