[
https://issues.apache.org/jira/browse/TRANSPORTS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen moved WSCOMMONS-524 to TRANSPORTS-40:
-----------------------------------------------------
Fix Version/s: (was: Transports 1.1)
1.6.0
Component/s: (was: Transport)
JMS
Affects Version/s: (was: Transports 1.1)
(was: Transports 1.0)
1.0.0
Key: TRANSPORTS-40 (was: WSCOMMONS-524)
Project: Axis2 Transports (was: WS-Commons)
> ServiceTaskManager fails to commit if session is transacted and always
> rollsback when using swiftMQ 2.1.3
> ---------------------------------------------------------------------------------------------------------
>
> Key: TRANSPORTS-40
> URL: https://issues.apache.org/jira/browse/TRANSPORTS-40
> Project: Axis2 Transports
> Issue Type: Bug
> Components: JMS
> Affects Versions: 1.0.0
> Environment: SwiftMQ 2.1.3,
> Reporter: Paul Inglis
> Assignee: Ruwan Linton
> Priority: Minor
> Fix For: 1.6.0
>
> Attachments: ServiceTaskManager.patch.txt
>
>
> Hi,
> I have an issue reading JMS messages from an old JMS 1.0 implementation
> provided by swiftMQ as part of a transaction. The transaction always rolls
> back and never commits a read from the queue.
> Looking at ServiceTaskManager, in the method handleMessage, the logic it
> takes is:
> 1. pass message to jmsMessageReceiver for processing
> 2. close the consumer
> 3. commit or rollback transaction on session.
> 4. close session
> 5. close connection
> It appears though that at stage 2 with swiftMQ the open transaction is
> rolledback. This means the commit in stage 3 does nothing.
> The solution is swap stages 2 and 3 such that the open transaction is
> commited before the consumer is closed.
> I noticted this issue on the verison of Transports (1.0) that ships with
> WSO2's ESB product but it appears that the same issue applies to 1.1 as well.
> Paul Inglis
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
