• 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: Warning: Request will be REDIRECTED to non-refusing instance
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Warning: Request will be REDIRECTED to non-refusing instance


  • Subject: Re: Warning: Request will be REDIRECTED to non-refusing instance
  • From: Daniel Muller <email@hidden>
  • Date: Wed, 24 Sep 2003 10:28:38 +0200

On Mercredi, sep 24, 2003, at 00:59, Chuck Hill wrote:

It sounds like you may have a deadlocking problem in your app (instance 1 in the explanation below).

Hi Chuck,

After more investigation, the WO Adaptor receives the request and send to application's instance and
wait 45 sec. for a reply. The instance never respond but wotaskd is able to shutdown it. I've changed
the minimum sessions to 10 like that wotaskd is able to restart instances every day.


If you can get a thread dump (see the archives here or on Omnigroup) that should show if this is the case.

Seems to be used only from Terminal, in my case the application is always working fine during development
it's only while running on deployment that this problem happened.


Is it possible to get a thread dump of deployed instance?

Are you being careful to lock and unlock all of your editing contexts correctly?

Yes I do, each new EOEditingContext is lock/unlock:

	ec.lock();

	try {...}
	catch {...}
	finally { ec.unlock(); }

but I never lock/unlock the defaultEditingContext. I'm wondering if it's required in some context?
What is your experiences about the defaultEditingContext?


BTW, I'm using Oracle database and I can see in the ora trace log that there are deadlocks.
EOEditingContext lock/unlock are useful in the same instance but what about between instances,
my application have 10 instances. I've a ILLRequestLock table used when I have to lock
a ILLRequest row to allow only one writer and many readers.


Is it required to lock/unlock editing context where all the entities are read-only in EOModeler?

Thank you for your help.

Cheers,
Daniel
--
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Warning: Request will be REDIRECTED to non-refusing instance
      • From: Chuck Hill <email@hidden>
References: 
 >Re: Warning: Request will be REDIRECTED to non-refusing instance (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: IP Address Log from Direct Action
  • Next by Date: WO, Web service and license
  • Previous by thread: Re: Warning: Request will be REDIRECTED to non-refusing instance
  • Next by thread: Re: Warning: Request will be REDIRECTED to non-refusing instance
  • Index(es):
    • Date
    • Thread