more information: current isolation level defined in Websphere app server is
4 (REPEATABLE READ),
--
View this message in context:
http://openjpa.208410.n2.nabble.com/Version-for-sqlserver-timpstamp-datatype-tp6267241p6274909.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
Hi Mike,
Implicit locking is same as Optimistic locking?
~chintan
--
View this message in context:
http://openjpa.208410.n2.nabble.com/Version-for-sqlserver-timpstamp-datatype-tp6267241p6274638.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
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
In WebSphere you can just enable the trace group "openjpa=all" and OpenJPA
trace will go to the normal WebSphere trace file.
The trace groups you want are openjpa.jdbc.SQL=all:openjpa.jdbc.JDBC=all.
Here's more on how to enable the trace in WebSphere :
http://publib.boulder.ibm.com/infocenter/wa
Hi Mike,
Thanks for the reply.
Uploaded persistent.xml file
http://openjpa.208410.n2.nabble.com/file/n6273992/persistence.xml
persistence.xml
Added logging propery, but could not see any logging on websphere console.
Am i missing something?
thanks
chintan
--
View this message in context:
htt
Hi Chintan,
We're getting a LockTimeoutException from SQLServer, which is why you're
seeing a different exception.
OpenJPA handles locking on SQLServer a little differently from other
databases. Instead of a FOR UPDATE clause we obtain a table lock.
It would be most helpful if you could enable l
Few more details: Loan object has one-to-one relation with other object and i
have already queried parent object which contains loan object.
so Parent p = em.find(Parent.class, pId);
Loan loan = p.getLoan();
//setting loan values
//lock loan object with optimistic lock
//persist it.
--
View th
Hi,
I got an @Embedded object with an @ElementCollection (Map) inside.
And in persistence.xml, the following property is set:
When I start my application for the second time (without clearing the
database) I get the following exception:
org.apache.openjpa.persistence.PersistenceException: Dopp
Thanks Mike. I just tried another approach by selecting one datetime field
for versioning. Howerver i am getting below exception. Full details are as
below. can you please advise me what is wrong?
I am trying to implement optimistic locking using JPA. I am using container
manged transaction.
Loa
Hi Joep,
I think there's a problem obtaining a connection - maybe a security setting
that's different for macs? I don't have access to one to try, and
unfortunately the exception closing a connection appears to be hiding the
root cause.
I'll fix the problem with closing a connection and that will
Hi Chintan,
I'm not very familiar with SQLServer, and I can't recommend a JDBC driver.
It's possible that DataDirect or Microsoft have other workarounds that will
convert a timestamp to another Java type, but it's probably unlikely.
If you cannot introduce a new column it's very hard to do optimi
Alright I created https://issues.apache.org/jira/browse/OPENJPA-1980
Thank you,
Henno
-Oorspronkelijk bericht-
Van: Michael Dick [mailto:michael.d.d...@gmail.com]
Verzonden: woensdag 13 april 2011 16:19
Aan: users@openjpa.apache.org
Onderwerp: Re: two issues when not using a DetachedStat
12 matches
Mail list logo
