[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1748) JBoss Messaging creates "Transaction is in ABORT-STATE" when concurrent threads make persistent messages store in the database

[Howard Gao (JIRA)]

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

Howard Gao updated JBMESSAGING-1748:
------------------------------------

        Fix Version/s: 1.4.0.SP3.CP10
    Affects Version/s: 1.4.5.GA
                       1.4.0.SP3.CP09


> JBoss Messaging creates "Transaction is in ABORT-STATE" when concurrent threads make persistent messages store in the database
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1748
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1748
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering, JMS Destination Manager, Messaging Core, Messaging Core Persistence, Tests and Performance
>    Affects Versions: 1.4.0.SP3.CP09, 1.4.5.GA, 1.4.6.GA
>         Environment: Red Enterprise Linux 5 + Sun JDK 5.0 + Oracle 10g (as the SGDBR for message persistence)
>            Reporter: Ricardo Ferreira
>            Assignee: Howard Gao
>            Priority: Critical
>             Fix For: 1.4.0.SP3.CP10, 1.4.6.GA.SP1, 1.4.7.GA
>
>         Attachments: testApp.zip
>
>
> When there are massive concurrent requests asking for message persistence in JBoss Messaging, it generated a transaction rollback in the Messaging transaction since the high volume of threads. The behavior of the application is to respond to locks erros in the target database (Eg: Oracle). The scenario remains the usage of a stateless session bean (ejb3) that make some database actions using several entity managers in a XA transaction. At the same transaction, some JMS messages are sent to the Queue using the PERSISTENT delivery mode to guarantee consistence of the message processing. At overall, the whole transaction must be atomic, and because that, the XA connection factory are looked up from the JNDI engine.

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