[#MULE-788] Oracle AQ does not support single resource transactions

Mule

Oracle AQ does not support single resource transactions

Created: 21/Apr/06 07:36 AM Updated: 24/Jan/08 05:57 AM

Component/s:

Transport: JMS

Affects Version/s:

1.3-rc2

Fix Version/s:

None

Time Tracking:

Not Specified

File Attachments:

jms-provider-1.3-rc2.diff (2 kB)
2.

jms-provider-1.3.3.patch.MULE-788.diff (2 kB)
3.

mule-transport-jms-1.3.3-patch.MULE-788.jar (77 kB)
4.

oaq-provider-1.3-rc2.diff (0.7 kB)

Environment:

« Hide

Java 1.4.2
Oracle 9.2.0.6

Issue Links:

Block

This issue blocks:

MULE-1079 Fix JMS Session association for the StringToXMLMessage transformer

Duplicate

This issue is duplicated by:

~~MULE-888~~ java.lang.NullPointerException when setting transactionConfig property to an inbound mule end point configured to receive messages from Oracle AQ messaging queue.

~~MULE-871~~ Oracle JMS Connector should not access the generic JMSConnector connection property

Labels:

Configuration:

« Hide

I configured the following inbound endpoint with a transaction

<inbound-router>
<endpoint address="oaq://distribution" transformers="TextMessageToString XmlToDomDocument">
<transaction action="ALWAYS_BEGIN" factory="org.mule.providers.jms.JmsTransactionFactory" />
</endpoint>
</inbound-router>

Description

« Hide

I configured transaction management on an inbound router.
Mules throws an exception

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Klaas Eikelboom added a comment - 26/Apr/06 05:06 AM

Created a workaround for my situation

[ Permlink | « Hide ]

Klaas Eikelboom added a comment - 06/Jan/07 01:54 PM

The reported bug stil exists in MULE 1.3.3. I just created a new patch to fix it and attach it to this issue. The base problem is that the JMS connector makes the assumption that only one connection exists for a provider. Thus the connection can be used for identification of the transaction. The fix is to use the connector itself.
It is possible that I forget something but it works for my situation.

Installation

Remove the file mule-transport-jms-1.3.3.jar from the lib/mule directory.
Add the attached jar to the directory.

Can this bug be fixed in te 1.3.4. release. Because what is the use of Oracle Advanced Queueing without transactions.