openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dick <>
Subject Re: @Version for sqlserver "timpstamp" datatype
Date Fri, 15 Apr 2011 14:18:56 GMT
Hi Chintan,

This issue might be best handled through the WebSphere support channels.

I'm assuming you changed the
 persistence property. This has the effect of changing the isolation level
after a connection is obtained from WebSphere's connection pool. Subsequent
requests for a connection will get a new connection from the pool and
promptly change the isolation level. As a result you end up with multiple
connections associated with the same tran, and the transaction needs to be
upgraded to XA.

What you probably want to do is change the default isolation level on the
WebSphere DataSource. The best way to do this is to use a resource reference
in your application, and set the isolation on the resource ref. There is
also a custom property that you can set on the DataSource documented
down a little bit to see the custom property).

If you read the link about the custom property you'll see there are a few
more options, but the resource ref and custom property are the two that I've
seen work in the past.

Hope this helps,

On Thu, Apr 14, 2011 at 3:54 PM, chintan4181 <> wrote:

> Hi Mike,
> enabled loggin and searched for "WITH (UPDLOCK) but i could not find any
> such entry. How can i remove implicit locking by changing isoloation level.
> I tried adding
>  In this case i am getting below exception.
>  org.apache.openjpa.lib.jdbc.ReportingSQLException: enlist: caught
> Exception
> Illegal
> attempt to enlist multiple 1PC XAResources
> can you please help me to resolve error?
> thanks
> chintan
> --
> View this message in context:
> Sent from the OpenJPA Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message