• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Deadlock
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Deadlock


  • Subject: Re: Deadlock
  • From: Anjo Krank <email@hidden>
  • Date: Sat, 1 Dec 2007 10:05:17 +0100

Seeing that your error goes away when you give the app more mem, you can fix up logging to use ERXPatternLayout and use

 %V{u used/f free} ... normal stuff

This will output

 75.22 MB used/12.86 MB free .. normal stuff

So you can see how much the app really takes. I also recently added some stuff in ERXApp to refuse new sessions if a certain free mem threshold is reached. This has made our deployments way more reliable.

Cheers, Anjo


Am 30.11.2007 um 22:14 schrieb Simon McLean:

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

_______________________________________________ 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
  • Prev by Date: Re: WO 54 Wonder-WebObjects fails to launch when network is down.
  • Next by Date: reverse engineer stored procedures & reorder wo components
  • Previous by thread: Re: WO 54 Wonder-WebObjects fails to launch when network is down.
  • Next by thread: reverse engineer stored procedures & reorder wo components
  • Index(es):
    • Date
    • Thread