[
https://issues.apache.org/jira/browse/JCR-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominique Pfister resolved JCR-743.
-----------------------------------
Resolution: Fixed
WebSphere 5.1.1 tries to recover the connection's associated XAResource on
startup, regardless whether it was committed or rolled back. In order to be
interoperable, an anonymous, recoverable-only connection is returned, when this
situation is detected.
Fixed in revision 510465.
> XA Transaction Recovery
> -----------------------
>
> Key: JCR-743
> URL: https://issues.apache.org/jira/browse/JCR-743
> Project: Jackrabbit
> Issue Type: Bug
> Components: jca
> Affects Versions: 1.2.1
> Environment: J2C Resource Adapter on Websphere
> Reporter: Claus Köll
> Assigned To: Dominique Pfister
>
> If i add a node to the repository i get a XAException because i run into a
> Timeout ...
> I see the Warn Message: Transaction rolled back because timeout expired.
> The default Timeout is set to 5 sec and i dont know how to set it to a higher
> value
> The Problem is if i restart my server websphere has a RecoveryManager and he
> try to recover this Transaction
> and then i get a NullpointerException in JCAManagedConnectionFactory.
> createManagedConnection beacuse the given
> ConnectionRequestInfo is null.
> So i dont know why the RecoveryManager tries to recover the Transaction ? The
> only solution for me is to delete the Tran-Log Files wich keep Websphere to
> recvoer
> XA Trasnactions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
