: Monday, February 19, 2007 6:54 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: WebSphere and transaction managers
Craig,
On 2/19/07, Craig L Russell [EMAIL PROTECTED] wrote:
On Feb 19, 2007, at 4:37 PM, Kevin Sutter wrote:
On 2/19/07, Patrick Linskey [EMAIL PROTECTED] wrote
]
Sent: Friday, February 16, 2007 11:21 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: WebSphere and transaction managers
This is known problem in WAS. The reason is data source
created in WAS is
always enlisted in the current global transaction, therefore
RESOURCE_LOCAL
persistence unit
in error, please immediately return
this
by email and then delete it.
-Original Message-
From: Albert Lee [mailto:[EMAIL PROTECTED]
Sent: Friday, February 16, 2007 11:21 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: WebSphere and transaction managers
This is known problem
@incubator.apache.org
Subject: Re: WebSphere and transaction managers
This is known problem in WAS. The reason is data source
created in WAS is
always enlisted in the current global transaction, therefore
RESOURCE_LOCAL
persistence unit using WAS data source triggers the observed
in error, please immediately return
this
by email and then delete it.
-Original Message-
From: Albert Lee [mailto:[EMAIL PROTECTED]
Sent: Friday, February 16, 2007 11:21 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: WebSphere and transaction managers
This is known
: Albert Lee [mailto:[EMAIL PROTECTED]
Sent: Friday, February 16, 2007 11:21 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: WebSphere and transaction managers
This is known problem in WAS. The reason is data source
created in WAS is
always enlisted in the current global
, please immediately return this
by email and then delete it.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, February 19, 2007 8:33 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: WebSphere and transaction managers
It is possible to suspend
This is known problem in WAS. The reason is data source created in WAS is
always enlisted in the current global transaction, therefore RESOURCE_LOCAL
persistence unit using WAS data source triggers the observed behavior.
This limitation will be corrected in the WAS EJB3 Feature Pack and future
are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
-Original Message-
From: Albert Lee [mailto:[EMAIL PROTECTED]
Sent: Friday, February 16, 2007 11:21 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: WebSphere
