You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Rajika Kumarasiri (JIRA)" <ji...@apache.org> on 2010/06/11 10:56:13 UTC

[jira] Created: (AXIS2-4735) Signal the JMS transport to rollback any transaction(if any) in cause of an error

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


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


[jira] Commented: (AXIS2-4735) Signal the JMS transport to rollback any transaction(if any) in cause of an error

Posted by "Rajeev Verma (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924787#action_12924787 ] 

Rajeev Verma commented on AXIS2-4735:
-------------------------------------

Hi,

I was expecting this fix to be available with release 1.5.2. But I do not see it source code. Any reason for not releasing it?

Thanks,
Rajeev

> 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


[jira] Updated: (AXIS2-4735) Signal the JMS transport to rollback any transaction(if any) in cause of an error

Posted by "Rajika Kumarasiri (JIRA)" <ji...@apache.org>.
     [ 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


[jira] Resolved: (AXIS2-4735) Signal the JMS transport to rollback any transaction(if any) in cause of an error

Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amila Chinthaka Suriarachchi resolved AXIS2-4735.
-------------------------------------------------

    Resolution: Fixed

Applied the patch with revision 953944.

> 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


[jira] Updated: (AXIS2-4735) Signal the JMS transport to rollback any transaction(if any) in cause of an error

Posted by "Rajika Kumarasiri (JIRA)" <ji...@apache.org>.
     [ 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


[jira] Resolved: (AXIS2-4735) Signal the JMS transport to rollback any transaction(if any) in cause of an error

Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amila Chinthaka Suriarachchi resolved AXIS2-4735.
-------------------------------------------------

    Resolution: Fixed

Applied the patch with revision 953944.

> 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


[jira] Updated: (AXIS2-4735) Signal the JMS transport to rollback any transaction(if any) in cause of an error

Posted by "Rajika Kumarasiri (JIRA)" <ji...@apache.org>.
     [ 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


[jira] Resolved: (AXIS2-4735) Signal the JMS transport to rollback any transaction(if any) in cause of an error

Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amila Chinthaka Suriarachchi resolved AXIS2-4735.
-------------------------------------------------

    Resolution: Fixed

Applied the patch with revision 953944.

> 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


[jira] Updated: (AXIS2-4735) Signal the JMS transport to rollback any transaction(if any) in cause of an error

Posted by "Rajika Kumarasiri (JIRA)" <ji...@apache.org>.
     [ 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


[jira] Resolved: (AXIS2-4735) Signal the JMS transport to rollback any transaction(if any) in cause of an error

Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amila Chinthaka Suriarachchi resolved AXIS2-4735.
-------------------------------------------------

    Resolution: Fixed

Applied the patch with revision 953944.

> 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


[jira] Resolved: (AXIS2-4735) Signal the JMS transport to rollback any transaction(if any) in cause of an error

Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amila Chinthaka Suriarachchi resolved AXIS2-4735.
-------------------------------------------------

    Resolution: Fixed

Applied the patch with revision 953944.

> 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


[jira] Updated: (AXIS2-4735) Signal the JMS transport to rollback any transaction(if any) in cause of an error

Posted by "Rajika Kumarasiri (JIRA)" <ji...@apache.org>.
     [ 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