[jboss-jira] [JBoss JIRA] Closed: (JBAS-7786) DataSourcePersistentManager storeSessionData attempts to continue using a db connection after an exception

[Brian Stansberry (JIRA)]

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

Brian Stansberry closed JBAS-7786.
----------------------------------

    Resolution: Done


> DataSourcePersistentManager storeSessionData attempts to continue using a db connection after an exception
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-7786
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7786
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-6.0.0.M1, JBossAS-6.0.0.M2
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-6.0.0.M3
>
>
> RDBMSStoreBase.storeSessionData has some logic to try to handle situations where a new session insert fails because the db already has a record[1] by instead updating that existing record. This logic is flawed because it doesn't rollback the existing db connection and get a new one before attempting this. Result is the error shown in the forum thread. 
> Fix is to rollback the connection and get a new one.
> [1] This scenario can occur if an expired session is still in the db, the client browser presents the old session cookie, and JBoss Web allows a new session with the old id. I'm not certain but I believe JBW 3 actually no longer allows this???

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