You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Rajika Kumarasiri (JIRA)" <ji...@apache.org> on 2009/08/24 10:56:01 UTC
[jira] Created: (SYNAPSE-573) Using UserTransaction interfacr
instead of TransactionManager interface in tx mediator
Using UserTransaction interfacr instead of TransactionManager interface in tx mediator
--------------------------------------------------------------------------------------
Key: SYNAPSE-573
URL: https://issues.apache.org/jira/browse/SYNAPSE-573
Project: Synapse
Issue Type: Wish
Components: Core
Environment: All
Reporter: Rajika Kumarasiri
I am not sure why the TransactionManager interface was used when implementing the tx mediator. But the documentation says when we need to move the tx mangement boundries to application server we need to use TransactionManager interface.
How ever using this(TransactionManager) with more that one data sources caused me resource enlist exception. So I just switched to UserTransaction Interface and then it works fine with more than one datasources. I am attaching the changes as a patch. (If anybody interested I can attach the configuration files used.)
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-573) Using UserTransaction interfacr
instead of TransactionManager interface in tx mediator
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton reassigned SYNAPSE-573:
------------------------------------
Assignee: Ruwan Linton
> Using UserTransaction interfacr instead of TransactionManager interface in tx mediator
> --------------------------------------------------------------------------------------
>
> Key: SYNAPSE-573
> URL: https://issues.apache.org/jira/browse/SYNAPSE-573
> Project: Synapse
> Issue Type: Wish
> Components: Core
> Environment: All
> Reporter: Rajika Kumarasiri
> Assignee: Ruwan Linton
> Attachments: SYNAPSE-573.patch
>
>
> I am not sure why the TransactionManager interface was used when implementing the tx mediator. But the documentation says when we need to move the tx mangement boundries to application server we need to use TransactionManager interface.
> How ever using this(TransactionManager) with more that one data sources caused me resource enlist exception. So I just switched to UserTransaction Interface and then it works fine with more than one datasources. I am attaching the changes as a patch. (If anybody interested I can attach the configuration files used.)
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-573) Using UserTransaction interfacr
instead of TransactionManager interface in tx mediator
Posted by "Rajika Kumarasiri (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajika Kumarasiri updated SYNAPSE-573:
--------------------------------------
Attachment: SYNAPSE-573.patch
This is the patch for the changes. BTW, we no more require the axis2.xml configuration which we use to look up TxManger.
> Using UserTransaction interfacr instead of TransactionManager interface in tx mediator
> --------------------------------------------------------------------------------------
>
> Key: SYNAPSE-573
> URL: https://issues.apache.org/jira/browse/SYNAPSE-573
> Project: Synapse
> Issue Type: Wish
> Components: Core
> Environment: All
> Reporter: Rajika Kumarasiri
> Attachments: SYNAPSE-573.patch
>
>
> I am not sure why the TransactionManager interface was used when implementing the tx mediator. But the documentation says when we need to move the tx mangement boundries to application server we need to use TransactionManager interface.
> How ever using this(TransactionManager) with more that one data sources caused me resource enlist exception. So I just switched to UserTransaction Interface and then it works fine with more than one datasources. I am attaching the changes as a patch. (If anybody interested I can attach the configuration files used.)
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-573) Using UserTransaction interfacr
instead of TransactionManager interface in tx mediator
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton resolved SYNAPSE-573.
----------------------------------
Resolution: Fixed
Fix Version/s: NIGHTLY
Fixed on the trunk, thanks for the contribution Rajika
> Using UserTransaction interfacr instead of TransactionManager interface in tx mediator
> --------------------------------------------------------------------------------------
>
> Key: SYNAPSE-573
> URL: https://issues.apache.org/jira/browse/SYNAPSE-573
> Project: Synapse
> Issue Type: Wish
> Components: Core
> Environment: All
> Reporter: Rajika Kumarasiri
> Assignee: Ruwan Linton
> Fix For: NIGHTLY
>
> Attachments: SYNAPSE-573.patch
>
>
> I am not sure why the TransactionManager interface was used when implementing the tx mediator. But the documentation says when we need to move the tx mangement boundries to application server we need to use TransactionManager interface.
> How ever using this(TransactionManager) with more that one data sources caused me resource enlist exception. So I just switched to UserTransaction Interface and then it works fine with more than one datasources. I am attaching the changes as a patch. (If anybody interested I can attach the configuration files used.)
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-573) Using UserTransaction interfacr
instead of TransactionManager interface in tx mediator
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759029#action_12759029 ]
Ruwan Linton commented on SYNAPSE-573:
--------------------------------------
Rajika, seems you are correct, let me go through the patch and apply it. :-)
> Using UserTransaction interfacr instead of TransactionManager interface in tx mediator
> --------------------------------------------------------------------------------------
>
> Key: SYNAPSE-573
> URL: https://issues.apache.org/jira/browse/SYNAPSE-573
> Project: Synapse
> Issue Type: Wish
> Components: Core
> Environment: All
> Reporter: Rajika Kumarasiri
> Assignee: Ruwan Linton
> Attachments: SYNAPSE-573.patch
>
>
> I am not sure why the TransactionManager interface was used when implementing the tx mediator. But the documentation says when we need to move the tx mangement boundries to application server we need to use TransactionManager interface.
> How ever using this(TransactionManager) with more that one data sources caused me resource enlist exception. So I just switched to UserTransaction Interface and then it works fine with more than one datasources. I am attaching the changes as a patch. (If anybody interested I can attach the configuration files used.)
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org