Issue Details (XML | Word | Printable)

Key: JCR-861
Type: Bug Bug
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Adam Hatherly
Votes: 4
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
Jackrabbit Content Repository

Connector should support LocalTransaction as well as XATransaction

Created: 23/Apr/07 10:33 AM   Updated: 22/Mar/09 06:57 PM
Return to search
Component/s: jackrabbit-jca
Affects Version/s: 1.2.3, 1.3
Fix Version/s: None

Time Tracking:
Not Specified

Environment: Websphere 5.1 and 6 on Linux, but may also apply on other platforms


 Description  « Hide
According to the Java connector specification, an application server may choose to use a LocalTransaction rather than an XATransaction if it determines that an XATransaction is not needed. Jackrabbit's connector code supports XA transactions but throws an exception if the server requests a LocalTransaction. The JCA code should be able to support LocalTransaction which could be easily mapped internally to calls to the XAResource interface.

I get this problem when I deploy on Websphere 5.1 or WebSphere 6, specifying XATransaction in the ra.xml file - in normal usage Websphere tries to obtain a LocalTransaction resulting in the exception:

[17/04/07 15:32:58:887 BST] 57053d6b LocalTransact E J2CA0077E: An exception was caught
while trying to obtain a javax.resource.cci.LocalTransaction from a ManagedConnection for
resource jcr/local. The exception is: java.lang.UnsupportedOperationException: Local transaction
is not supported

My only workaround at present is to specify NoTransaction, but that may not be a good solution for many people.
See post on jackrabbit users group from Wed, 18 Apr, 13:16 by Dominique Pfister.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no subversion log entries for this issue yet.