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

[Markus Döring (Commented) (JIRA)]

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

Markus Döring commented on AS7-3143:
------------------------------------

Ok, this is good to know.

This worked in previous JBoss versions.
Maybe there should be at least something in the log (don't know if it's possible to find out if it's an container managed transaction or an user managed transaction at that point).

What's about the EE spec?
As Stephen Coy mentioned, the transacted attribute should be ignored in EJB container.
So should java:/ConnectionFactory not be used in EJB Container at all? Or is it DIY transactions only in the spec?

                
> 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
>         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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira