Andrus Adamchik <andru..bjectstyle.org> wrote:
> I really can't tell what's causing it. You are right - the usual cause
> is deletion (directly or via CASCADE delete rules). IIRC there were
> some bugs reported (and fixed) in the past that caused quiet change of
> an object state to transient on certain referential integrity problems.
> I don't think we are doing that anymore.
Maybe that's the problem.
> A few suggestions:
>
> 1. Try it with RC1. [v.1.1-dev April 14 2004] - you have a pretty old
> version (I know, you have your own customizations to the source, so
> upgrade is not always easy).
Yeah, I've been planning on upgrading -- I was just hoping to hold off until
after our production deployment and until the official 1.1 release, but our
production deployment has been put off another two weeks.
I'll go ahead and start using RC1.
> 2. To debug, override [...] and Thread.dumpStack()
Yeah, the only problem is that the bug has only happened once. I've used
this technique to track down WebObject context-locking problems and it's
very effective. I'll give it a try if the bug happens again.
Thanks for the suggestions.
-Mike
This archive was generated by hypermail 2.0.0 : Tue Oct 12 2004 - 13:55:03 EDT