++ This bug is a clone of bug 778955 ++

Date of First Response: 2009-06-23 04:08:22
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/298300
project_key: SOA

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.