Our server admin came back and said right before server lock-up there were a bunch of errors in /core/packages/farcry/tree.cfc involving "get real path from connection" if that rings a bell. He also said there might have been other problems, so he's not sure which is cause and which is effect. Thought I'd post anyway.
Tomek On Tue, Apr 19, 2011 at 9:28 AM, Tomek Kott <[email protected]> wrote: > Joel sent this straight to me, but I thought it would be useful for future > reference. Since this hasn't happened to me before, I doubt it's the issue > here, but it is good to know. > > Tomek > > > ---------- Forwarded message ---------- > From: joel.cass <[email protected]> > Date: Mon, Apr 18, 2011 at 9:18 PM > Subject: Re: CF9 Server Deadlock: "Semaphore"? > To: Tomek kott <[email protected]> > > > Hi there, > > Look for code inside a cflock that calls other code containing another > cflock. What happens is that a lock is created in the outer call, and > the inner call containing the other lock will wait indefininately for > the outer lock to close, thus a deadlock occurs. > > A good practise is to always name your locks accordingly so that they > can run independently. Scoped locks or unnamed locks act globally > across the application so can cause issues. > > Joel > > On Apr 19, 7:27 am, Tomek kott <[email protected]> wrote: > > Hi fc, > > > > My server admin says that our server deadlocked this afternoon with the > most > > likely culprit being > > > "edu.emory.mathcs.backport.java.util.concurrent.Semaphore$FairSync.acquire(Semaphore.java:337)". > > Is this used explicitly anywhere in FC6.0.11, and is there a chance this > has > > caused problems for others? > > > > Thanks, > > > > Tomek > > -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
