[jboss-jira] [JBoss JIRA] (AS7-3143) JMS Messages with CMP and transactional=true are not commited to the queue

[Tom Eicher (JIRA)]

    [ https://issues.jboss.org/browse/AS7-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771093#comment-12771093 ] 

Tom Eicher commented on AS7-3143:
---------------------------------

So using JmsXA will will fix the problem of messages not being received (at all) in the MDB.
However, the parameter is still not completely ignored since transacted=false will work with multiple MDBs (ActivationConfigProperty maxSessions) as configured,
whereas transacted=true will only have one (single-threaded) MDB working on the queue, i.e. the message posting/receiving is serialized.
Is this expected behaviour or maybe another bug ?


                
> JMS Messages with CMP and transactional=true are not commited to the queue
> --------------------------------------------------------------------------
>
>                 Key: AS7-3143
>                 URL: https://issues.jboss.org/browse/AS7-3143
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 7.0.1.Final, 7.1.0.CR1, 7.1.0.CR1b
>         Environment: Windows 7, Java 1.6 update 24
>            Reporter: Markus Döring
>            Assignee: Carlo de Wolf
>             Fix For: 7.1.0.Final
>
>         Attachments: TestEAR.ear.zip, TestEAR.ear.zip, TestEAR.ear.zip
>
>
> When sending a message to a JMS queue using container managed transactions and setting transactional=true (connection.createSession(true, Session.AUTO_ACKNOWLEDGE)), the message is never added to the queue.
> Using transactional=false is not an option because the message is added to the queue immediately and not after transaction commit.
> This can be reproduced with the attached EAR (exploded deployment, so just unpack the .zip in the deployments directory) and the standalone-full.xml (JBoss 7.1.0.CR1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira