[
https://jira.jboss.org/jira/browse/JBESB-2631?page=com.atlassian.jira.plu...
]
Tomohisa igarashi commented on JBESB-2631:
------------------------------------------
I think invoking JMS ESB Service with ServiceInvoker#deliverSync() is not enlisted in JTA
Tx context by default. InVM ESB Service seems to be enlisted force, no choice.
Support synchronous call to InVM ESB service under JTA transaction
context
--------------------------------------------------------------------------
Key: JBESB-2631
URL:
https://jira.jboss.org/jira/browse/JBESB-2631
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4 CP2
Reporter: Taro Yasuma
AS-IS)
Under JTA transaction context, assume you call ServiceInvoker#deliverSync() to call InVM
ESB service. Then the call is in dead-locked because the operation regarding InVM queue is
enlisted in the transaction.
As a workaround, you need to suspend the transaction before ServiceInvoker#deliverSync()
but it's inconvenient that you always do this workaround in application.
TO-BE)
1. To have a configuration option on ESB to avoid enlisting operation regarding InVM
queue in the transaction.
2. To have a configuration option on ESB to have no transaction boundaries between
operation of calling ESB service and operations of processing ActionPipeline. I.e. an
operation regarding ActionPipeline is enlisted in the same transaction of the operation of
calling ESB service.
If you enable #2, it will be much flexible for usecase that having fine grained services
but no transaction boundaries among them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira