Hi Chintan, This issue might be best handled through the WebSphere support channels.
I'm assuming you changed the openjpa.jdbc.TransactionIsolation<http://openjpa.apache.org/builds/latest/docs/manual/manual.html#openjpa.jdbc.TransactionIsolation> 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 here<http://www-01.ibm.com/support/docview.wss?uid=swg21224492> (scroll 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, -mike On Thu, Apr 14, 2011 at 3:54 PM, chintan4181 <[email protected]> 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 > com.ibm.ws.Transaction.IllegalResourceIn2PCTransactionException: Illegal > attempt to enlist multiple 1PC XAResources > > can you please help me to resolve error? > > thanks > chintan > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Version-for-sqlserver-timpstamp-datatype-tp6267241p6274371.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. >
