[jboss-jira] [JBoss JIRA] (JBMESSAGING-1904) Rolling back current fix for JBMESSAGING-1850

[Yong Hao Gao (Resolved) (JIRA)]

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

Yong Hao Gao resolved JBMESSAGING-1904.
---------------------------------------

    Resolution: Done

    
> Rolling back current fix for JBMESSAGING-1850
> ---------------------------------------------
>
>                 Key: JBMESSAGING-1904
>                 URL: https://issues.jboss.org/browse/JBMESSAGING-1904
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: JMS Facade
>    Affects Versions: 1.4.0.SP3.CP14, 1.4.8.SP3
>            Reporter: Yong Hao Gao
>            Assignee: Yong Hao Gao
>             Fix For: 1.4.0.SP3.CP15, 1.4.8.SP4
>
>
> The fix is not proper and caused performance downgrade.
> Quoting Kevin:
> ...
> While investigating this I realised that the current codebase is unsafe as the background task modify a shared state, possible being used by a subsequent task.  I tried to find a solution to this problem but I believe the only correct fix is to handle the timeout at the JBoss Remoting level.  This will have a larger impact on the codebase, especially in the rollback/recovery code, and will be complicated by the clustering behaviour.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira