Re: Extending the “No Instance Available” timeout

[Chuck Hill]

So the negative instance/port number is, IIRC, a signal to wotask to shortcut 
the configuration and go directly to the instance.  So that might be why 
setting the Receive Timeout in JavaMonitor is not working.   I don’t recall if 
that C code looks for the site config in this case or not.  That might also be 
why setting the app up in JavaMonitor is not picking this up either.


From: Lon Varscsak <lon.varsc...@gmail.com<mailto:lon.varsc...@gmail.com>>
Date: Wednesday, April 6, 2016 at 10:28 AM
To: Chuck Hill <ch...@gevityinc.com<mailto:ch...@gevityinc.com>>
Cc: OC <o...@ocs.cz<mailto:o...@ocs.cz>>, WebObjects-Dev Mailing List 
<webobjects-dev@lists.apple.com<mailto:webobjects-dev@lists.apple.com>>
Subject: Re: Extending the “No Instance Available” timeout

1) Direct Connect isn’t really an option for us (nor should it be for anyone ).
2) The URLs look like:  
http://localhost/Apps/WebObjects/SmartPractice.woa/-20001
3) We always set a port for development.
4) I did have him set the application up in Monitor with timeouts and he claims 
it didn’t work.
5) I swear I’ve done this before both ways and had it work. :(

-Lon

On Wed, Apr 6, 2016 at 10:03 AM, Chuck Hill 
<ch...@gevityinc.com<mailto:ch...@gevityinc.com>> wrote:
Ben, what do the URLs look like?  It has been ages since I set this up.  I 
think you might need to set the WOPort in Eclipse and then configure an 
application in JavaMonitor and create an instance on that port for the Receive 
Timeout to have any effect.  Or, if you are not using Apache to serve resources 
or do SSL, using DirectConnect will also avoid this error message.

Chuck





On 2016-04-06, 9:02 AM, 
"webobjects-dev-bounces+chill=gevityinc@lists.apple.com<mailto:gevityinc@lists.apple.com>
 on behalf of OC" 
<webobjects-dev-bounces+chill=gevityinc@lists.apple.com<mailto:gevityinc@lists.apple.com>
 on behalf of o...@ocs.cz<mailto:o...@ocs.cz>> wrote:

>Aha, I see — I thought Eclipse uses Direct Connect, just as Xcode used to (and 
>mine still does).
>
>In that case, beside the adaptor log, I would probably
>
>(a) try Direct Connect; no timeouts in this mode;
>(b) add extra logs to show when the R/R loop begins, how it runs, and when it 
>ends, to see what takes that long (and how long precisely).
>
>All the best,
>OC
>
>On 6. 4. 2016, at 17:55, Lon Varscsak 
><lon.varsc...@gmail.com<mailto:lon.varsc...@gmail.com>> wrote:
>
>> Just to help Ben while he’s sleeping… This is while he’s running the 
>> application from within Eclipse (still through Apache) while he’s 
>> testing/debugging.
>>
>> -Lon
>>
>> On Wed, Apr 6, 2016 at 8:37 AM, OC <o...@ocs.cz<mailto:o...@ocs.cz>> wrote:
>> Benjamin,
>>
>> On 6. 4. 2016, at 10:19, Benjamin Chew 
>> <bc...@smarthealth.com<mailto:bc...@smarthealth.com>> wrote:
>>
>> > I did change Receive Timeout to 999,999 under “Site”, and restarted 
>> > wotaskd and monitor, but that didn’t help.
>>
>> The only thing which should need to be restarted is your application.
>>
>> > I also tried creating an app in monitor with the same name as the one 
>> > running in Eclipse, and changing the Receive Timeout, but that didn’t work 
>> > either.
>>
>> I am afraid I do not quite get your setup; what has Eclipse to do with that?
>>
>> Anyway, it is really weird if setting a super-high receive timeout for an 
>> application does not affect that application's “No Instance Available“ 
>> report; that does not make any sense to me. If the application locks, you 
>> still might not get the desired page, but (a) that is extremely improbable 
>> if it does run all right in a different setup, (b) at the very least, you 
>> should be waiting for the “No Instance Available“ report much, much longer.
>>
>> Sorry for an extremely dumb question, but is there perhaps any possibility 
>> you are changing the timeouts of another application, or the same 
>> application but on a different server, or something like that?
>>
>> Is there anything of interest in the adaptor log?
>>
>> All the best,
>> OC
>>
>>
>> > On Wed, Apr 6, 2016 at 2:59 PM, Chuck Hill 
>> > <ch...@gevityinc.com<mailto:ch...@gevityinc.com>> wrote:
>> > Receive Timeout is set in JavaMonitor.
>> >
>> > From: Benjamin Chew <bc...@smarthealth.com<mailto:bc...@smarthealth.com>>
>> > Date: Tuesday, April 5, 2016 at 11:52 PM
>> > To: Chuck Hill <ch...@gevityinc.com<mailto:ch...@gevityinc.com>>
>> > Cc: OC <o...@ocs.cz<mailto:o...@ocs.cz>>, WebObjects-Dev Mail

Re: Extending the “No Instance Available” timeout

[Lon Varscsak]

1) Direct Connect isn’t really an option for us (nor should it be for
anyone ).
2) The URLs look like:
http://localhost/Apps/WebObjects/SmartPractice.woa/-20001
3) We always set a port for development.
4) I did have him set the application up in Monitor with timeouts and he
claims it didn’t work.
5) I swear I’ve done this before both ways and had it work. :(

-Lon

On Wed, Apr 6, 2016 at 10:03 AM, Chuck Hill <ch...@gevityinc.com> wrote:

> Ben, what do the URLs look like?  It has been ages since I set this up.  I
> think you might need to set the WOPort in Eclipse and then configure an
> application in JavaMonitor and create an instance on that port for the
> Receive Timeout to have any effect.  Or, if you are not using Apache to
> serve resources or do SSL, using DirectConnect will also avoid this error
> message.
>
> Chuck
>
>
>
>
>
> On 2016-04-06, 9:02 AM, "webobjects-dev-bounces+chill=
> gevityinc@lists.apple.com on behalf of OC"
> <webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of
> o...@ocs.cz> wrote:
>
> >Aha, I see — I thought Eclipse uses Direct Connect, just as Xcode used to
> (and mine still does).
> >
> >In that case, beside the adaptor log, I would probably
> >
> >(a) try Direct Connect; no timeouts in this mode;
> >(b) add extra logs to show when the R/R loop begins, how it runs, and
> when it ends, to see what takes that long (and how long precisely).
> >
> >All the best,
> >OC
> >
> >On 6. 4. 2016, at 17:55, Lon Varscsak <lon.varsc...@gmail.com> wrote:
> >
> >> Just to help Ben while he’s sleeping… This is while he’s running the
> application from within Eclipse (still through Apache) while he’s
> testing/debugging.
> >>
> >> -Lon
> >>
> >> On Wed, Apr 6, 2016 at 8:37 AM, OC <o...@ocs.cz> wrote:
> >> Benjamin,
> >>
> >> On 6. 4. 2016, at 10:19, Benjamin Chew <bc...@smarthealth.com> wrote:
> >>
> >> > I did change Receive Timeout to 999,999 under “Site”, and restarted
> wotaskd and monitor, but that didn’t help.
> >>
> >> The only thing which should need to be restarted is your application.
> >>
> >> > I also tried creating an app in monitor with the same name as the one
> running in Eclipse, and changing the Receive Timeout, but that didn’t work
> either.
> >>
> >> I am afraid I do not quite get your setup; what has Eclipse to do with
> that?
> >>
> >> Anyway, it is really weird if setting a super-high receive timeout for
> an application does not affect that application's “No Instance Available“
> report; that does not make any sense to me. If the application locks, you
> still might not get the desired page, but (a) that is extremely improbable
> if it does run all right in a different setup, (b) at the very least, you
> should be waiting for the “No Instance Available“ report much, much longer.
> >>
> >> Sorry for an extremely dumb question, but is there perhaps any
> possibility you are changing the timeouts of another application, or the
> same application but on a different server, or something like that?
> >>
> >> Is there anything of interest in the adaptor log?
> >>
> >> All the best,
> >> OC
> >>
> >>
> >> > On Wed, Apr 6, 2016 at 2:59 PM, Chuck Hill <ch...@gevityinc.com>
> wrote:
> >> > Receive Timeout is set in JavaMonitor.
> >> >
> >> > From: Benjamin Chew <bc...@smarthealth.com>
> >> > Date: Tuesday, April 5, 2016 at 11:52 PM
> >> > To: Chuck Hill <ch...@gevityinc.com>
> >> > Cc: OC <o...@ocs.cz>, WebObjects-Dev Mailing List <
> webobjects-dev@lists.apple.com>
> >> > Subject: Re: Extending the “No Instance Available” timeout
> >> >
> >> > Thanks guys, I appreciate all the other suggestions, but I’m quite
> positive it is the ping time that is killing me.
> >> >
> >> > I have tried multiple apps, and all the apps have the same problem.
> They worked fine when I was in the US, but I encountered this problem once
> I got to Singapore. I’ve verified this by pinging servers in the US, and
> I’m getting ~300ms ping times, with some jitter, which does not help.
> >> >
> >> > OC and Chuck: could you tell me how to adjust my Receive Timeout?
> >> >
> >> > Thanks,
> >> > Ben
> >> >
> >> > On Wed, Apr 6, 2016 at 2:26 AM, Chuck Hill <ch...@gevityinc.com>
> wrote:
> >> > I assume that you are running the app locally 

Re: Extending the “No Instance Available” timeout

[Chuck Hill]

Ben, what do the URLs look like?  It has been ages since I set this up.  I 
think you might need to set the WOPort in Eclipse and then configure an 
application in JavaMonitor and create an instance on that port for the Receive 
Timeout to have any effect.  Or, if you are not using Apache to serve resources 
or do SSL, using DirectConnect will also avoid this error message.

Chuck 





On 2016-04-06, 9:02 AM, 
"webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of OC" 
<webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of 
o...@ocs.cz> wrote:

>Aha, I see — I thought Eclipse uses Direct Connect, just as Xcode used to (and 
>mine still does).
>
>In that case, beside the adaptor log, I would probably
>
>(a) try Direct Connect; no timeouts in this mode;
>(b) add extra logs to show when the R/R loop begins, how it runs, and when it 
>ends, to see what takes that long (and how long precisely).
>
>All the best,
>OC
>
>On 6. 4. 2016, at 17:55, Lon Varscsak <lon.varsc...@gmail.com> wrote:
>
>> Just to help Ben while he’s sleeping… This is while he’s running the 
>> application from within Eclipse (still through Apache) while he’s 
>> testing/debugging.
>> 
>> -Lon
>> 
>> On Wed, Apr 6, 2016 at 8:37 AM, OC <o...@ocs.cz> wrote:
>> Benjamin,
>> 
>> On 6. 4. 2016, at 10:19, Benjamin Chew <bc...@smarthealth.com> wrote:
>> 
>> > I did change Receive Timeout to 999,999 under “Site”, and restarted 
>> > wotaskd and monitor, but that didn’t help.
>> 
>> The only thing which should need to be restarted is your application.
>> 
>> > I also tried creating an app in monitor with the same name as the one 
>> > running in Eclipse, and changing the Receive Timeout, but that didn’t work 
>> > either.
>> 
>> I am afraid I do not quite get your setup; what has Eclipse to do with that?
>> 
>> Anyway, it is really weird if setting a super-high receive timeout for an 
>> application does not affect that application's “No Instance Available“ 
>> report; that does not make any sense to me. If the application locks, you 
>> still might not get the desired page, but (a) that is extremely improbable 
>> if it does run all right in a different setup, (b) at the very least, you 
>> should be waiting for the “No Instance Available“ report much, much longer.
>> 
>> Sorry for an extremely dumb question, but is there perhaps any possibility 
>> you are changing the timeouts of another application, or the same 
>> application but on a different server, or something like that?
>> 
>> Is there anything of interest in the adaptor log?
>> 
>> All the best,
>> OC
>> 
>> 
>> > On Wed, Apr 6, 2016 at 2:59 PM, Chuck Hill <ch...@gevityinc.com> wrote:
>> > Receive Timeout is set in JavaMonitor.
>> >
>> > From: Benjamin Chew <bc...@smarthealth.com>
>> > Date: Tuesday, April 5, 2016 at 11:52 PM
>> > To: Chuck Hill <ch...@gevityinc.com>
>> > Cc: OC <o...@ocs.cz>, WebObjects-Dev Mailing List 
>> > <webobjects-dev@lists.apple.com>
>> > Subject: Re: Extending the “No Instance Available” timeout
>> >
>> > Thanks guys, I appreciate all the other suggestions, but I’m quite 
>> > positive it is the ping time that is killing me.
>> >
>> > I have tried multiple apps, and all the apps have the same problem. They 
>> > worked fine when I was in the US, but I encountered this problem once I 
>> > got to Singapore. I’ve verified this by pinging servers in the US, and I’m 
>> > getting ~300ms ping times, with some jitter, which does not help.
>> >
>> > OC and Chuck: could you tell me how to adjust my Receive Timeout?
>> >
>> > Thanks,
>> > Ben
>> >
>> > On Wed, Apr 6, 2016 at 2:26 AM, Chuck Hill <ch...@gevityinc.com> wrote:
>> > I assume that you are running the app locally through Apache as that 
>> > message is from wotaskd.  As OC pointed out, the Receive Timeout is what 
>> > you need to adjust up and up and up.
>> >
>> > It sounds like latency is what is killing you, I don’t recall how chatty 
>> > JDBC is but it is probably along the lines of ODBC which is quite chatty 
>> > indeed.  Latency kills its performance.  Another possibility is to run a 
>> > local copy of the DB.
>> >
>> > Chuck
>> >
>> >
>> >
>> >
>> > On 2016-04-05, 7:38 AM, 
>> > "webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf 

Re: Extending the “No Instance Available” timeout

[OC]

Aha, I see — I thought Eclipse uses Direct Connect, just as Xcode used to (and 
mine still does).

In that case, beside the adaptor log, I would probably

(a) try Direct Connect; no timeouts in this mode;
(b) add extra logs to show when the R/R loop begins, how it runs, and when it 
ends, to see what takes that long (and how long precisely).

All the best,
OC

On 6. 4. 2016, at 17:55, Lon Varscsak <lon.varsc...@gmail.com> wrote:

> Just to help Ben while he’s sleeping… This is while he’s running the 
> application from within Eclipse (still through Apache) while he’s 
> testing/debugging.
> 
> -Lon
> 
> On Wed, Apr 6, 2016 at 8:37 AM, OC <o...@ocs.cz> wrote:
> Benjamin,
> 
> On 6. 4. 2016, at 10:19, Benjamin Chew <bc...@smarthealth.com> wrote:
> 
> > I did change Receive Timeout to 999,999 under “Site”, and restarted wotaskd 
> > and monitor, but that didn’t help.
> 
> The only thing which should need to be restarted is your application.
> 
> > I also tried creating an app in monitor with the same name as the one 
> > running in Eclipse, and changing the Receive Timeout, but that didn’t work 
> > either.
> 
> I am afraid I do not quite get your setup; what has Eclipse to do with that?
> 
> Anyway, it is really weird if setting a super-high receive timeout for an 
> application does not affect that application's “No Instance Available“ 
> report; that does not make any sense to me. If the application locks, you 
> still might not get the desired page, but (a) that is extremely improbable if 
> it does run all right in a different setup, (b) at the very least, you should 
> be waiting for the “No Instance Available“ report much, much longer.
> 
> Sorry for an extremely dumb question, but is there perhaps any possibility 
> you are changing the timeouts of another application, or the same application 
> but on a different server, or something like that?
> 
> Is there anything of interest in the adaptor log?
> 
> All the best,
> OC
> 
> 
> > On Wed, Apr 6, 2016 at 2:59 PM, Chuck Hill <ch...@gevityinc.com> wrote:
> > Receive Timeout is set in JavaMonitor.
> >
> > From: Benjamin Chew <bc...@smarthealth.com>
> > Date: Tuesday, April 5, 2016 at 11:52 PM
> > To: Chuck Hill <ch...@gevityinc.com>
> > Cc: OC <o...@ocs.cz>, WebObjects-Dev Mailing List 
> > <webobjects-dev@lists.apple.com>
> > Subject: Re: Extending the “No Instance Available” timeout
> >
> > Thanks guys, I appreciate all the other suggestions, but I’m quite positive 
> > it is the ping time that is killing me.
> >
> > I have tried multiple apps, and all the apps have the same problem. They 
> > worked fine when I was in the US, but I encountered this problem once I got 
> > to Singapore. I’ve verified this by pinging servers in the US, and I’m 
> > getting ~300ms ping times, with some jitter, which does not help.
> >
> > OC and Chuck: could you tell me how to adjust my Receive Timeout?
> >
> > Thanks,
> > Ben
> >
> > On Wed, Apr 6, 2016 at 2:26 AM, Chuck Hill <ch...@gevityinc.com> wrote:
> > I assume that you are running the app locally through Apache as that 
> > message is from wotaskd.  As OC pointed out, the Receive Timeout is what 
> > you need to adjust up and up and up.
> >
> > It sounds like latency is what is killing you, I don’t recall how chatty 
> > JDBC is but it is probably along the lines of ODBC which is quite chatty 
> > indeed.  Latency kills its performance.  Another possibility is to run a 
> > local copy of the DB.
> >
> > Chuck
> >
> >
> >
> >
> > On 2016-04-05, 7:38 AM, 
> > "webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of 
> > OC" <webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf 
> > of o...@ocs.cz> wrote:
> >
> > >Benjamin,
> > >
> > >On 5. 4. 2016, at 11:02, Benjamin Chew <bc...@smarthealth.com> 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 wi

Re: Extending the “No Instance Available” timeout

[Lon Varscsak]

Just to help Ben while he’s sleeping… This is while he’s running the
application from within Eclipse (still through Apache) while he’s
testing/debugging.

-Lon

On Wed, Apr 6, 2016 at 8:37 AM, OC <o...@ocs.cz> wrote:

> Benjamin,
>
> On 6. 4. 2016, at 10:19, Benjamin Chew <bc...@smarthealth.com> wrote:
>
> > I did change Receive Timeout to 999,999 under “Site”, and restarted
> wotaskd and monitor, but that didn’t help.
>
> The only thing which should need to be restarted is your application.
>
> > I also tried creating an app in monitor with the same name as the one
> running in Eclipse, and changing the Receive Timeout, but that didn’t work
> either.
>
> I am afraid I do not quite get your setup; what has Eclipse to do with
> that?
>
> Anyway, it is really weird if setting a super-high receive timeout for an
> application does not affect that application's “No Instance Available“
> report; that does not make any sense to me. If the application locks, you
> still might not get the desired page, but (a) that is extremely improbable
> if it does run all right in a different setup, (b) at the very least, you
> should be waiting for the “No Instance Available“ report much, much longer.
>
> Sorry for an extremely dumb question, but is there perhaps any possibility
> you are changing the timeouts of another application, or the same
> application but on a different server, or something like that?
>
> Is there anything of interest in the adaptor log?
>
> All the best,
> OC
>
>
> > On Wed, Apr 6, 2016 at 2:59 PM, Chuck Hill <ch...@gevityinc.com> wrote:
> > Receive Timeout is set in JavaMonitor.
> >
> > From: Benjamin Chew <bc...@smarthealth.com>
> > Date: Tuesday, April 5, 2016 at 11:52 PM
> > To: Chuck Hill <ch...@gevityinc.com>
> > Cc: OC <o...@ocs.cz>, WebObjects-Dev Mailing List <
> webobjects-dev@lists.apple.com>
> > Subject: Re: Extending the “No Instance Available” timeout
> >
> > Thanks guys, I appreciate all the other suggestions, but I’m quite
> positive it is the ping time that is killing me.
> >
> > I have tried multiple apps, and all the apps have the same problem. They
> worked fine when I was in the US, but I encountered this problem once I got
> to Singapore. I’ve verified this by pinging servers in the US, and I’m
> getting ~300ms ping times, with some jitter, which does not help.
> >
> > OC and Chuck: could you tell me how to adjust my Receive Timeout?
> >
> > Thanks,
> > Ben
> >
> > On Wed, Apr 6, 2016 at 2:26 AM, Chuck Hill <ch...@gevityinc.com> wrote:
> > I assume that you are running the app locally through Apache as that
> message is from wotaskd.  As OC pointed out, the Receive Timeout is what
> you need to adjust up and up and up.
> >
> > It sounds like latency is what is killing you, I don’t recall how chatty
> JDBC is but it is probably along the lines of ODBC which is quite chatty
> indeed.  Latency kills its performance.  Another possibility is to run a
> local copy of the DB.
> >
> > Chuck
> >
> >
> >
> >
> > On 2016-04-05, 7:38 AM, "webobjects-dev-bounces+chill=
> gevityinc@lists.apple.com on behalf of OC"
> <webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of
> o...@ocs.cz> wrote:
> >
> > >Benjamin,
> > >
> > >On 5. 4. 2016, at 11:02, Benjamin Chew <bc...@smarthealth.com> 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 

Re: Extending the “No Instance Available” timeout

[OC]

Benjamin,

On 6. 4. 2016, at 10:19, Benjamin Chew <bc...@smarthealth.com> wrote:

> I did change Receive Timeout to 999,999 under “Site”, and restarted wotaskd 
> and monitor, but that didn’t help.

The only thing which should need to be restarted is your application.

> I also tried creating an app in monitor with the same name as the one running 
> in Eclipse, and changing the Receive Timeout, but that didn’t work either. 

I am afraid I do not quite get your setup; what has Eclipse to do with that?

Anyway, it is really weird if setting a super-high receive timeout for an 
application does not affect that application's “No Instance Available“ report; 
that does not make any sense to me. If the application locks, you still might 
not get the desired page, but (a) that is extremely improbable if it does run 
all right in a different setup, (b) at the very least, you should be waiting 
for the “No Instance Available“ report much, much longer.

Sorry for an extremely dumb question, but is there perhaps any possibility you 
are changing the timeouts of another application, or the same application but 
on a different server, or something like that?

Is there anything of interest in the adaptor log?

All the best,
OC


> On Wed, Apr 6, 2016 at 2:59 PM, Chuck Hill <ch...@gevityinc.com> wrote:
> Receive Timeout is set in JavaMonitor.
> 
> From: Benjamin Chew <bc...@smarthealth.com>
> Date: Tuesday, April 5, 2016 at 11:52 PM
> To: Chuck Hill <ch...@gevityinc.com>
> Cc: OC <o...@ocs.cz>, WebObjects-Dev Mailing List 
> <webobjects-dev@lists.apple.com>
> Subject: Re: Extending the “No Instance Available” timeout
> 
> Thanks guys, I appreciate all the other suggestions, but I’m quite positive 
> it is the ping time that is killing me. 
> 
> I have tried multiple apps, and all the apps have the same problem. They 
> worked fine when I was in the US, but I encountered this problem once I got 
> to Singapore. I’ve verified this by pinging servers in the US, and I’m 
> getting ~300ms ping times, with some jitter, which does not help.
> 
> OC and Chuck: could you tell me how to adjust my Receive Timeout?
> 
> Thanks,
> Ben
> 
> On Wed, Apr 6, 2016 at 2:26 AM, Chuck Hill <ch...@gevityinc.com> wrote:
> I assume that you are running the app locally through Apache as that message 
> is from wotaskd.  As OC pointed out, the Receive Timeout is what you need to 
> adjust up and up and up.
> 
> It sounds like latency is what is killing you, I don’t recall how chatty JDBC 
> is but it is probably along the lines of ODBC which is quite chatty indeed.  
> Latency kills its performance.  Another possibility is to run a local copy of 
> the DB.
> 
> Chuck
> 
> 
> 
> 
> On 2016-04-05, 7:38 AM, 
> "webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of OC" 
> <webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of 
> o...@ocs.cz> wrote:
> 
> >Benjamin,
> >
> >On 5. 4. 2016, at 11:02, Benjamin Chew <bc...@smarthealth.com> 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
> >
> >
> > _

Re: Extending the “No Instance Available” timeout

[Benjamin Chew]

I did change Receive Timeout to 999,999 under “Site”, and restarted wotaskd
and monitor, but that didn’t help.

I also tried creating an app in monitor with the same name as the one
running in Eclipse, and changing the Receive Timeout, but that didn’t work
either.

Am I missing something?

Thanks,
Ben

On Wed, Apr 6, 2016 at 2:59 PM, Chuck Hill <ch...@gevityinc.com> wrote:

> Receive Timeout is set in JavaMonitor.
>
> From: Benjamin Chew <bc...@smarthealth.com>
> Date: Tuesday, April 5, 2016 at 11:52 PM
> To: Chuck Hill <ch...@gevityinc.com>
> Cc: OC <o...@ocs.cz>, WebObjects-Dev Mailing List <
> webobjects-dev@lists.apple.com>
> Subject: Re: Extending the “No Instance Available” timeout
>
> Thanks guys, I appreciate all the other suggestions, but I’m quite
> positive it is the ping time that is killing me.
>
> I have tried multiple apps, and all the apps have the same problem. They
> worked fine when I was in the US, but I encountered this problem once I got
> to Singapore. I’ve verified this by pinging servers in the US, and I’m
> getting ~300ms ping times, with some jitter, which does not help.
>
> OC and Chuck: could you tell me how to adjust my Receive Timeout?
>
> Thanks,
> Ben
>
> On Wed, Apr 6, 2016 at 2:26 AM, Chuck Hill <ch...@gevityinc.com> wrote:
>
>> I assume that you are running the app locally through Apache as that
>> message is from wotaskd.  As OC pointed out, the Receive Timeout is what
>> you need to adjust up and up and up.
>>
>> It sounds like latency is what is killing you, I don’t recall how chatty
>> JDBC is but it is probably along the lines of ODBC which is quite chatty
>> indeed.  Latency kills its performance.  Another possibility is to run a
>> local copy of the DB.
>>
>> Chuck
>>
>>
>>
>>
>> On 2016-04-05, 7:38 AM, "webobjects-dev-bounces+chill=
>> gevityinc@lists.apple.com on behalf of OC"
>> <webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of
>> o...@ocs.cz> wrote:
>>
>> >Benjamin,
>> >
>> >On 5. 4. 2016, at 11:02, Benjamin Chew <bc...@smarthealth.com> 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
>> >
>> >
>> > ___
>> >Do not post admin requests to the list. They will be ignored.
>> >Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
>> >Help/Unsubscribe/Update your Subscription:
>> >
>> https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com
>> >
>> >This email sent to ch...@gevityinc.com
>>
>
>
 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Extending the “No Instance Available” timeout

[Chuck Hill]

Receive Timeout is set in JavaMonitor.

From: Benjamin Chew <bc...@smarthealth.com<mailto:bc...@smarthealth.com>>
Date: Tuesday, April 5, 2016 at 11:52 PM
To: Chuck Hill <ch...@gevityinc.com<mailto:ch...@gevityinc.com>>
Cc: OC <o...@ocs.cz<mailto:o...@ocs.cz>>, WebObjects-Dev Mailing List 
<webobjects-dev@lists.apple.com<mailto:webobjects-dev@lists.apple.com>>
Subject: Re: Extending the “No Instance Available” timeout

Thanks guys, I appreciate all the other suggestions, but I’m quite positive it 
is the ping time that is killing me.

I have tried multiple apps, and all the apps have the same problem. They worked 
fine when I was in the US, but I encountered this problem once I got to 
Singapore. I’ve verified this by pinging servers in the US, and I’m getting 
~300ms ping times, with some jitter, which does not help.

OC and Chuck: could you tell me how to adjust my Receive Timeout?

Thanks,
Ben

On Wed, Apr 6, 2016 at 2:26 AM, Chuck Hill 
<ch...@gevityinc.com<mailto:ch...@gevityinc.com>> wrote:
I assume that you are running the app locally through Apache as that message is 
from wotaskd.  As OC pointed out, the Receive Timeout is what you need to 
adjust up and up and up.

It sounds like latency is what is killing you, I don’t recall how chatty JDBC 
is but it is probably along the lines of ODBC which is quite chatty indeed.  
Latency kills its performance.  Another possibility is to run a local copy of 
the DB.

Chuck




On 2016-04-05, 7:38 AM, 
"webobjects-dev-bounces+chill=gevityinc@lists.apple.com<mailto:gevityinc@lists.apple.com>
 on behalf of OC" 
<webobjects-dev-bounces+chill=gevityinc@lists.apple.com<mailto:gevityinc@lists.apple.com>
 on behalf of o...@ocs.cz<mailto:o...@ocs.cz>> wrote:

>Benjamin,
>
>On 5. 4. 2016, at 11:02, Benjamin Chew 
><bc...@smarthealth.com<mailto:bc...@smarthealth.com>> 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
>
>
> ___
>Do not post admin requests to the list. They will be ignored.
>Webobjects-dev mailing list  
>(Webobjects-dev@lists.apple.com<mailto:Webobjects-dev@lists.apple.com>)
>Help/Unsubscribe/Update your Subscription:
>https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com
>
>This email sent to ch...@gevityinc.com<mailto:ch...@gevityinc.com>

 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Extending the “No Instance Available” timeout

[Benjamin Chew]

Thanks guys, I appreciate all the other suggestions, but I’m quite positive
it is the ping time that is killing me.

I have tried multiple apps, and all the apps have the same problem. They
worked fine when I was in the US, but I encountered this problem once I got
to Singapore. I’ve verified this by pinging servers in the US, and I’m
getting ~300ms ping times, with some jitter, which does not help.

OC and Chuck: could you tell me how to adjust my Receive Timeout?

Thanks,
Ben

On Wed, Apr 6, 2016 at 2:26 AM, Chuck Hill  wrote:

> I assume that you are running the app locally through Apache as that
> message is from wotaskd.  As OC pointed out, the Receive Timeout is what
> you need to adjust up and up and up.
>
> It sounds like latency is what is killing you, I don’t recall how chatty
> JDBC is but it is probably along the lines of ODBC which is quite chatty
> indeed.  Latency kills its performance.  Another possibility is to run a
> local copy of the DB.
>
> Chuck
>
>
>
>
> On 2016-04-05, 7:38 AM, "webobjects-dev-bounces+chill=
> gevityinc@lists.apple.com on behalf of OC"
>  o...@ocs.cz> wrote:
>
> >Benjamin,
> >
> >On 5. 4. 2016, at 11:02, Benjamin Chew  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
> >
> >
> > ___
> >Do not post admin requests to the list. They will be ignored.
> >Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
> >Help/Unsubscribe/Update your Subscription:
> >
> https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com
> >
> >This email sent to ch...@gevityinc.com
>
 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Extending the “No Instance Available” timeout

[Chuck Hill]

I assume that you are running the app locally through Apache as that message is 
from wotaskd.  As OC pointed out, the Receive Timeout is what you need to 
adjust up and up and up.

It sounds like latency is what is killing you, I don’t recall how chatty JDBC 
is but it is probably along the lines of ODBC which is quite chatty indeed.  
Latency kills its performance.  Another possibility is to run a local copy of 
the DB.

Chuck




On 2016-04-05, 7:38 AM, 
"webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of OC" 
 wrote:

>Benjamin,
>
>On 5. 4. 2016, at 11:02, Benjamin Chew  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
>
>
> ___
>Do not post admin requests to the list. They will be ignored.
>Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
>Help/Unsubscribe/Update your Subscription:
>https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com
>
>This email sent to ch...@gevityinc.com

 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Extending the “No Instance Available” timeout

[OC]

Benjamin,

On 5. 4. 2016, at 11:02, Benjamin Chew  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


 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Extending the "No Instance Available" timeout

[CHRISTOPH WICK | i4innovation GmbH, Bonn]

My understanding is that a "No instance available" comes from your Apache's 
WOAdaptor. Therefore it shouldn't basically have nothing to do with your VPN or 
slow internet connection.

Daniele has already suggested using a ERXLongResponsePage.

Sometimes the problem is not a single database operation, but a WORepetition 
iterating over a huge array of objects and then - inside the WORepetition - 
calling another db/eof-intensive method on each item, like e.g. 
'item.littleDatabaseWork()'.

While each 'item.littleDatabaseWork()' may only take some ms, iterating over a 
lot of items may be too much. In this case, 'pagination' of large arrays may be 
the best solution. Use a ERXDisplayGroup in this case.

C.U.CW
--
The three great virtues of a programmer are Laziness, Impatience and Hubris. 
(Randal Schwartz)

> On 05.04.2016, at 11:23, Daniele Corti  wrote:
> 
> Hi Benjamin,
> if I understand correctly the problem is a intensive work on the DB, that, 
> added to the slow connection, make WOMonitor return the "No Instance 
> Available" error.
> 
> if used in local network, these pages use more than 3/4 seconds to load? I'm 
> asking this, because I think it's a good practice in these scenarios to 
> introduce an intermediate page with a 
> ERXLongResponseTask.DefaultImplementation subclass and a ERXLongResponsePage 
> component to let the user see a loading page while fetching from the DB 
> (example Search Result in large DB), before render the component.
> 
> Is it possible to you to alterate the WO App to do this?
> 
> Another solution can be to optimize the DB (maybe moving on a dedicate 
> machine, physical or virtual, configured to speedup db results), making the 
> fetch result in few seconds.
> 
> Bye
> 
> Il giorno mar 5 apr 2016 alle ore 11:03 Benjamin Chew  
> ha scritto:
> Hi Everyone,
> 
> I’m wondering if any of you kind souls can help me. :)
> 
> 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).
> 
> 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. I’ve also tried changing WOMaxSocketIdleTime and WOLifebeatInterval in 
> my Eclipse debugging profile, but that didn’t help either.
> 
> Does anyone have any ideas?
> 
> Thanks,
> Ben
>  ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/ildenae%40gmail.com
> 
> This email sent to ilde...@gmail.com
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/cw%40i4innovation.de
> 
> This email sent to c...@i4innovation.de



signature.asc
Description: Message signed with OpenPGP using GPGMail
 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Extending the “No Instance Available” timeout

[Theodore Petrosky]

are you able to look at the logs of the VPN box? Is this an issue where the VPN 
is not permitting traffic on the port you are trying to use? My VPN box is very 
restrictive. I have a web server  in the office for testing, and I forget which 
port it’s web server is using, but it is not port 80. When I VPN into the 
office I can not see this server even when I use the IP (dns is set up with 
both forward and reverse dns). I had to take over a machine in the office and 
use that as my eyes on the server in question.

Looking at the VPN logs pointed to the fact that the web server was not using a 
standard port. (80)

Just an idea.

Ted


> On Apr 5, 2016, at 5:02 AM, Benjamin Chew  wrote:
> 
> Hi Everyone,
> 
> I’m wondering if any of you kind souls can help me. :)
> 
> 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). 
> 
> 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. I’ve also tried changing WOMaxSocketIdleTime and WOLifebeatInterval in 
> my Eclipse debugging profile, but that didn’t help either.
> 
> Does anyone have any ideas?
> 
> Thanks,
> Ben
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com
> 
> This email sent to tedp...@yahoo.com


 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Extending the “No Instance Available” timeout

[Dev WO]

Hi Ben,

Your ping time isn’t the issue for sure, as far as I remember the time out is 
something like a minute…
I think the issue is more on the “application” side.
Try to see if you have anyway to get some log. Eventually output the SQL for 
your app to see if you forget to do some batch when accessing the database (if 
you see a row by row select, that is probably the primary issue to fix)
If it’s a Wonder app: 
log4j.logger.er.transaction.adaptor.EOAdaptorDebugEnabled=INFO either on your 
Property file or as a launch argument.

Xavier


> On 05 Apr 2016, at 11:02, Benjamin Chew  wrote:
> 
> Hi Everyone,
> 
> I’m wondering if any of you kind souls can help me. :)
> 
> 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). 
> 
> 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. I’ve also tried changing WOMaxSocketIdleTime and WOLifebeatInterval in 
> my Eclipse debugging profile, but that didn’t help either.
> 
> Does anyone have any ideas?
> 
> Thanks,
> Ben
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/webobjects%40anazys.com
> 
> This email sent to webobje...@anazys.com


 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Extending the "No Instance Available" timeout

[Daniele Corti]

Hi Benjamin,
if I understand correctly the problem is a intensive work on the DB, that,
added to the slow connection, make WOMonitor return the "No Instance
Available" error.

if used in local network, these pages use more than 3/4 seconds to load?
I'm asking this, because I think it's a good practice in these scenarios to
introduce an intermediate page with a
ERXLongResponseTask.DefaultImplementation subclass and a
ERXLongResponsePage component to let the user see a loading page while
fetching from the DB (example Search Result in large DB), before render the
component.

Is it possible to you to alterate the WO App to do this?

Another solution can be to optimize the DB (maybe moving on a dedicate
machine, physical or virtual, configured to speedup db results), making the
fetch result in few seconds.

Bye

Il giorno mar 5 apr 2016 alle ore 11:03 Benjamin Chew 
ha scritto:

> Hi Everyone,
>
> I’m wondering if any of you kind souls can help me. :)
>
> 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).
>
> 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. I’ve also tried changing WOMaxSocketIdleTime and WOLifebeatInterval
> in my Eclipse debugging profile, but that didn’t help either.
>
> Does anyone have any ideas?
>
> Thanks,
> Ben
>  ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/ildenae%40gmail.com
>
> This email sent to ilde...@gmail.com
 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com