On Thu, Jan 29, 2009 at 2:20 PM, is_maximum <mnr...@gmail.com> wrote:
> > I really don't know why after about 6 months working with OpenJPA and > inserting near a million records we should face this problem? what have > changed that cause optimistic locking to be activated spontaneously!!! Hmmm... Not sure. What has changed in the last six months? That is, what version of OpenJPA did you start with and what version are you currently running with? As you move from release to release, there are bound to be changes. And, in some cases, the changes may actually have closed some holes that you were accidentally avoiding. That is, maybe you were "lucky"... :-) We do have quite an extensive test bucket and we do attempt to avoid any type of regressions. But, our test bucket (like any other test bucket) is not exhaustive. You could be exercising an area of code that just hasn't been covered to the extent it should be. There are so many variables with databases, configurations, jvms, environmental, openjpa, etc. If you can help identify and isolate the changes that caused your concerns, then maybe we can help out. Thanks, Kevin > > > Pinaki Poddar wrote: > > > > Hi, > >> but using build-time enhancer. I tried ant-runner for maven but was > >> unable to enhance my classes > >> if I don't give any class name I get this message: > > > > A few minutes of digging with classpath and other beasts to enhance at > > build-time will save you a lot of pain and gain performance. Enhancer > > fails mostly with classpath issues and availability of > > META-INF/persistence.xml etc. > > > > If you have access to OpenJPA source code, follow the trail at > > ./openjpa-persistence-jdbc/pom.xml and > > ./openjpa-persistence-jdbc/src/main/ant/enhancer.xml > > > > It shows one way to enhance 100's of Entity classes used for testing. > > > > > > > > -- > View this message in context: > http://n2.nabble.com/-URGENT--performance-issues-tp2232295p2241065.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. > >
