[ 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
