[jboss-jira] [JBoss JIRA] Resolved: (JBAS-7379) UpgradeException when concurrently accessing the session after failover with buddy replication

Brian Stansberry (JIRA) jira-events at lists.jboss.org
Fri Oct 23 15:16:05 EDT 2009


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

Brian Stansberry resolved JBAS-7379.
------------------------------------

    Fix Version/s: JBossAS-5.2.0.Beta1
                   JBossAS-6.0.0.Alpha1
       Resolution: Done


Fixed on Branch_5_x and trunk.

Dennis, if you port this to the EAP branches, be aware that a previous commit (r 95441 on Branch_5_x) rearranged some classes in the testsuite. You'll need to port that as well to get the test to compile.

> UpgradeException when concurrently accessing the session after failover with buddy replication
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-7379
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7379
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.1.0.GA
>            Reporter: Dennis Reed
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1
>
>
> When using buddy replication, when multiple concurrent requests are made with the same session ID after failover, most abort with an org.jboss.cache.lock.UpgradeException while trying to migrate the cache data to the local node.

-- 
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

        



More information about the jboss-jira mailing list