'
Subject: Re: Derby XA, Hibernate 2.1.6, WebSphere 5.1 - Server returned
XAER_NOTA at commit time
Johan Hoogenboezem wrote:
Hi Stanley
1. I will try to initiate a support case, but in my experience they drag
their feet if they think the problem does not lie with WAS. They are also
very likely
Johan Hoogenboezem wrote:
Hi Stanley
1. I will try to initiate a support case, but in my experience they drag
their feet if they think the problem does not lie with WAS. They are also
very likely to tell me to move to WAS 6.
2. Like I said before, the trace logs are meaningless to me. And you are
written in Java.
Regards
Johan
-Original Message-
From: Stanley Bradbury [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 21, 2005 2:09 AM
To: Derby Discussion
Subject: Re: Derby XA, Hibernate 2.1.6, WebSphere 5.1 - Server returned
XAER_NOTA at commit time
Hi Johan -
I had hoped to find
-Original Message-
From: Stanley Bradbury [mailto:[EMAIL PROTECTED]
Sent: Monday, October 17, 2005 12:19 AM
To: Johan Hoogenboezem
Cc: derby-user@db.apache.org
Subject: Re: Derby XA, Hibernate 2.1.6, WebSphere 5.1 - Server returned
XAER_NOTA at commit time
Johan Hoogenboezem wrote:
Hi
Hi Johan -
I will be able to look into this error more later today but wanted to
get this observation to you ASAP since this issue seems to have set for
a week. The root cause of the failure is this exception taken from one
of the repeated stack traces from the MCWrapper class:
original
4:19 PM
To: Derby Discussion
Subject: Re: Derby XA, Hibernate 2.1.6, WebSphere 5.1 - Server returned
XAER_NOTA at commit time
Hi Johan -
I will be able to look into this error more later today but wanted to
get this observation to you ASAP since this issue seems to have set for
a week. The root
Hi,
I'm using Derby 10.1.1.0 with derbyclient in a WebSphere 5.1 server
environment. Here's the first part of the console output that shows some
versioning info:
**Start
WebSphere Platform 5.1 [BASE 5.1.0.3 cf30412.02]
