This one time, at band camp, Mark Thill said:
MT>I have read through all the archives that I can find,
MT>and have seen several users with this error, but
MT>nobody seemed to be able to solve it. I read that it
MT>could be a problem with the key-generator="MAX" and
MT>that the solution was to specify something other than
MT>the generic engine, but I am unsure how to do this and
MT>there was no response from anyone else.
MT>
MT>I started seeing this error this morning. I restarted
MT>tomcat (4.0.4) and the error went away, but I have a
MT>feeling it will return. I am using Sybase 12.x. Has
MT>anyone found the answer to this error?
MT>
MT>Key Generator Failure. Duplicated Identity is
MT>generated!
Mark,
If this error is occurring upon commit() or update() when using
setAutoStore( true ), I believe this to be a bug, but it's not been
officially filed in Bugzilla yet. The only workaround of which I'm aware
would be to manually traverse the object graph and handle the updates
manually. However, sometimes changing the lock type (via the 'access'
attribute of the <class> element in the mapping descriptor) to be more
restrictive can help. But this option isn't workable for everyone and
can even cause additional problems when used incorrectly.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
