I'll try to write a patch when I find the time. In the meantime I've
made my XAResource more robust to know how to reset its state when
there's a problem.
I've tried upgrading to 3.1 but there are API changes that I can't
understand immediately how to work around:
Previously, when instantiating a
https://issues.apache.org/jira/browse/GERONIMO-5870
On Wed, Mar 16, 2011 at 2:10 PM, Florent Guillaume f...@nuxeo.com wrote:
I'll try to write a patch when I find the time. In the meantime I've
made my XAResource more robust to know how to reset its state when
there's a problem.
I've tried
Hi David, all,
I have the following situation using txmanager (2.1.3) as a standalone
component in my application.
ConnectionFactory.getConnection
- GenericConnectionManager.allocateConnection
- TransactionEnlistingInterceptor.getConnection
- TransactionImpl.enlistResource
- xaRes.start
In my
Hi Florent,
Thanks for finding this and figuring out what is going on! A Jira would be
great and a patch even better!
BTW you might want to switch to a newer tm as 2.2.x and 3.x have much better
error handling and recovery when a resource is not available on startup or
disappears midway
