You are viewing a plain text version of this content. The canonical link for it is here.

Posted to fx-dev@ws.apache.org by "Andrew Gatford (JIRA)" <ji...@apache.org> on 2006/11/03 11:56:16 UTC

[jira] Created: (SANDESHA2-39) The CreateSequence message when sent creates a new transaction inside the second SandeshaOutHandler when it is already part of the application message transaction.

The CreateSequence message when sent creates a new transaction inside the second SandeshaOutHandler when it is already part of the application message transaction.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: SANDESHA2-39
                 URL: http://issues.apache.org/jira/browse/SANDESHA2-39
             Project: Apache Sandesha2
          Issue Type: Bug
            Reporter: Andrew Gatford


The process out message for the application message processor creates a new CreateSequence message and sends it.  This then flows through the SandeshaOutHandler which creates a new transaction for sending the message.
As this message is still inside a transaction it should have the flag
		// Set that the create sequence message is part of a transaction.
		createSeqMsg.setProperty(Sandesha2Constants.WITHIN_TRANSACTION, Sandesha2Constants.VALUE_TRUE);
added.

Also, the create sequence sender bean is not marked as a create sequence message


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

[jira] Updated: (SANDESHA2-39) The CreateSequence message when sent creates a new transaction inside the second SandeshaOutHandler when it is already part of the application message transaction.

Posted by "Andrew Gatford (JIRA)" <ji...@apache.org>.

     [ http://issues.apache.org/jira/browse/SANDESHA2-39?page=all ]

Andrew Gatford updated SANDESHA2-39:
------------------------------------

    Attachment: multipletransaction.patch

> The CreateSequence message when sent creates a new transaction inside the second SandeshaOutHandler when it is already part of the application message transaction.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SANDESHA2-39
>                 URL: http://issues.apache.org/jira/browse/SANDESHA2-39
>             Project: Apache Sandesha2
>          Issue Type: Bug
>            Reporter: Andrew Gatford
>         Attachments: multipletransaction.patch
>
>
> The process out message for the application message processor creates a new CreateSequence message and sends it.  This then flows through the SandeshaOutHandler which creates a new transaction for sending the message.
> As this message is still inside a transaction it should have the flag
> 		// Set that the create sequence message is part of a transaction.
> 		createSeqMsg.setProperty(Sandesha2Constants.WITHIN_TRANSACTION, Sandesha2Constants.VALUE_TRUE);
> added.
> Also, the create sequence sender bean is not marked as a create sequence message

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

[jira] Commented: (SANDESHA2-39) The CreateSequence message when sent creates a new transaction inside the second SandeshaOutHandler when it is already part of the application message transaction.

Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.

    [ http://issues.apache.org/jira/browse/SANDESHA2-39?page=comments#action_12447103 ] 
            
Chamikara Jayalath commented on SANDESHA2-39:
---------------------------------------------

Applied.

Chamikara

> The CreateSequence message when sent creates a new transaction inside the second SandeshaOutHandler when it is already part of the application message transaction.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SANDESHA2-39
>                 URL: http://issues.apache.org/jira/browse/SANDESHA2-39
>             Project: Apache Sandesha2
>          Issue Type: Bug
>            Reporter: Andrew Gatford
>         Attachments: multipletransaction.patch
>
>
> The process out message for the application message processor creates a new CreateSequence message and sends it.  This then flows through the SandeshaOutHandler which creates a new transaction for sending the message.
> As this message is still inside a transaction it should have the flag
> 		// Set that the create sequence message is part of a transaction.
> 		createSeqMsg.setProperty(Sandesha2Constants.WITHIN_TRANSACTION, Sandesha2Constants.VALUE_TRUE);
> added.
> Also, the create sequence sender bean is not marked as a create sequence message

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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