axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajika Kumarasiri (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AXIS2-4735) Signal the JMS transport to rollback any transaction(if any) in cause of an error
Date Fri, 11 Jun 2010 09:07:13 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rajika Kumarasiri updated AXIS2-4735:
-------------------------------------

    Attachment: AXIS2-4735.patch

> Signal the JMS transport to rollback any transaction(if any) in cause of an error 
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4735
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4735
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rajika Kumarasiri
>         Attachments: AXIS2-4735.patch
>
>
> When using the JMS transport with axis2 and if we use local or distributed JMS transactions
there is no way to signal the transport to rollback the transaction. The decision to roll
back or commit the transaction is based on the out come of   jmsMessageReceiver.onMessage()
in ServiceTaskManager class and the property "SET_ROLLBACK_ONLY". 
> We need to set the property SET_ROLLBACK_ONLY to true in case the message receiver hit
any error so that at the transport we can rollback the transaction (if any). 
> A small patch will follow. 
> Rajika

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message