Deadlock
Deadlock
- Subject: Deadlock
- From: Simon McLean <email@hidden>
- Date: Fri, 30 Nov 2007 21:14:59 +0000
Thought I would keep the list up-to-date on our deadlock issue, in
case anyone else suffers something similar.
We've narrowed down the problem to ERJGroupsSynchroniser: if we
reduce the number of entities being synchronised to just a few
critical entities, rather than the whole model (which has around 30
entities) then the app runs fine. We are still not sure what is
actually happening to the app to cause the deadlock when we don't
limit the entities. We are sure it isn't actually running out of
memory because there is no hint of it in the logs and we know the JVM
is still alive. However increasing the heap allocated to the app
seems to let us synch more entities ? I'm wondering whether the app
is just getting flooded with updates and if we did actually leave the
"deadlocked" app for a few hours it might actually recover, but alas
we don't have the luxury of a few hours in production and we don't
seem able to load the app enough in development to simulate the
deadlock.
Anyway, we do now have a stable app once again, and I can sleep
tonight :-) Many thanks once again to all those who have helped me
with this one - it's much appreciated.
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