[jboss-jira] [JBoss JIRA] Resolved: (JBAS-6194) Move transaction sticky logic in proxy to interceptors to avoid bottleneck

[Galder Zamarreno (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreno resolved JBAS-6194.
------------------------------------

    Resolution: Done


> Move transaction sticky logic in proxy to interceptors to avoid bottleneck
> --------------------------------------------------------------------------
>
>                 Key: JBAS-6194
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6194
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Transaction Manager (JBossTM)
>    Affects Versions: JBossAS-5.0.0.CR2
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: JBossAS-5.0.0.GA
>
>
> With the current user transaction sticky tpc retrieval method, a bottleneck can be formed when invocation 
> returns are too big. To avoid such bottleneck, we'll separate the transaction sticky logic in proxy into two
> separate interceptors, one for EJBs, one for ClientUserTransactionService's clustered proxy.
> By doing this, we're able to provide a cleaner solution, separating this logic from the proxy, and making it
> even more optional, reducing the risks of affecting normal (non user transaction sticky) invocations.
> Another interesting idea for the future would be to use a synchronised version of a weak IdentiyHashMap.

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