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 <[email protected]> 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= > [email protected] on behalf of OC" > <[email protected] on behalf of > [email protected]> wrote: > > >Benjamin, > > > >On 5. 4. 2016, at 11:02, Benjamin Chew <[email protected]> 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 ([email protected]) > >Help/Unsubscribe/Update your Subscription: > > > https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com > > > >This email sent to [email protected] >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
