Apple

On 2016-04-05, 7:38 AM, "webobjects-dev-bounces+chill=email@hidden on behalf of OC" <webobjects-dev-bounces+chill=email@hidden on behalf of email@hidden> wrote:

>Benjamin,
>
>On 5. 4. 2016, at 11:02, Benjamin Chew <email@hidden> wrote:
>
>> I’m in Singapore working off a VPN connection to the States, and while waiting for some database-intensive components to display, I keep getting “No Instance Available” because it’s taking so long to complete all the queries (ping times ~ 200ms).
>
>As others have pointed out, ping times could hardly affect this.
>
>> I’ve tried going to WOMonitor on my local machine (localhost:56789) and modified the Send, Receive and Connect timeouts, but that didn’t seem to help.
>
>Far as I can say with my very limited knowledge,
>
>(a) “No Instance Available” is most time (if not always) caused by the receive timeout at the server side;
>(b) and thus, increasing it enough should help.
>
>> Does anyone have any ideas?
>
>First thing, I would try some ludicrously high receive timeout. For us, it always helped (in the sense that the rendered page did always return, presumed the user had the patience to wait long enough, especially when by a mistake I had computed some results in O(2^N) :))
>
>It might also help to check the adaptor log -- touch /tmp/logWebObjects as root, and the log should appear in /tmp/WebObjectsLog.
>
>The ultimate solution, of course, would be background processing and/or paging, as others already recommended; but first you need to find the particular cause of the long processing, which might be sometimes a bit hairy.
>
>All the best and good luck,
>OC
>
>

References:
	> Extending the “No Instance Available” timeout (From: Benjamin Chew <email@hidden>)
	>Re: Extending the “No Instance Available” timeout (From: OC <email@hidden>)
	> Re: Extending the “No Instance Available” timeout (From: Chuck Hill <email@hidden>)