Re: Deadlock [Fixed - we think!]
Re: Deadlock [Fixed - we think!]
- Subject: Re: Deadlock [Fixed - we think!]
- From: Simon McLean <email@hidden>
- Date: Tue, 27 Nov 2007 18:42:35 +0000
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).
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 :-)
Simon
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden