Thanks Pinaki, I was really stuck and abandoned any hope but your useful hints on classpath issues saved me.
but today we had another weird day!!! First I create version field for some tables and put @Version on them and awfully everything got worst. even a simple insert with different account (different account number in DB) encountered optimistic locking exception!!! I am wondered why this never happened before. Then I tried to disable optimistic locking and set the LockManager to 'pessimistic' but nothing has changed and we still experience the same exception 'OptimisticLockException'. the problem remained even I set that value to 'none'. After hours of toiling I gain nothing and gave up. 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!!! 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.
