Re: Beating request-response cycle on debug?
Re: Beating request-response cycle on debug?
- Subject: Re: Beating request-response cycle on debug?
- From: Chuck Hill <email@hidden>
- Date: Wed, 2 Jun 2004 16:05:02 -0700
Art's right. It is the Connect and Receive timeouts that need to be
increased. On a dev machine you might need to fire up an instance of
JavaMonitor to set these. Unless you particularly enjoy hand editing
XML.
Chuck
On Jun 2, 2004, at 3:11 PM, Art Isbell wrote:
On Jun 2, 2004, at 11:03 AM, Geoff Hopson wrote:
Have a look at this:
http://www.unsanity.com/products/free
You'll want the SafariNoTimeout
This is certainly a godsend for preventing Safari from timing out
after 60 seconds.
On 2 Jun 2004, at 21:30, Kieran Kelleher wrote:
Is it possible to configure my development setup so I don't get a
time-out "No instance available" error on my browser when I am
debugging code in the middle of the request-response cycle?
I don't think a browser timeout causes the "No instance available"
message. This has occurred when I try to debug while when my app is
using a Web server; i.e., when my app's not running in Direct Connect
mode. I was never able to avoid this "No instance available" message,
but I didn't try very hard. Increasing the lifebeat interval didn't
seem to help, but maybe I didn't increase it enough. The WO HTTP
Adaptor has some hardcoded connection, send, and receive timeout
values which might be involved. These can be overridden in
JavaMonitor's Adaptor Settings.
Aloha,
Art
_______________________________________________
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.
_______________________________________________
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.