On Nov 27, 2007, at 10:42 AM, Simon McLean wrote:
Many thanks to everyone for their help with my recent deadlock
issue. I think we may well have nailed it as we've managed 18
hours now without a blip.
What was the problem?
We use long response pages for connecting to supplier systems via
xml posted over http. We have pojo's that represent the request and
response documents, and we use WOXMLCoder to serialise the objects
in to request documents and deserialise response documents back
into objects. One of the request pojos was carrying an enterprise
object around with it that represented the user logged into the
current session and in certain circumstances WOXMLCoder was
accessing this object. I believe that breaks this rule:
1. You have a WOLongResponsePage that is using an editing context
that is managed (locked and unlocked by the session).
That would do it! :-)
Disappointingly the app did in fact lock up once more this
afternoon. However the logs are plastered with the session
termination scream so I'm going to get rid of that one before
deciding whether to throw myself out of the window :-)
Hopefully you are on the ground floor.
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
