Re: No Instance Available vs. "Requested Application Not Found on this Server."
Re: No Instance Available vs. "Requested Application Not Found on this Server."
- Subject: Re: No Instance Available vs. "Requested Application Not Found on this Server."
- From: "Andrew R. Kinnie" <email@hidden>
- Date: Thu, 02 Sep 2010 08:46:31 -0400
On Sep 1, 2010, at 8:02 PM, Chuck Hill wrote:
> Hi Andrew,
> ...
>> Now, I am attempting to work from home via VPN (which is slow, but I never had issues before), and when I try and debug the app from Eclipse through apache instead of Direct Connect, I get "No Instance Available" every time.
>
> Meaning that you are running the app locally and accessing the DB over VPN? SQL is VERY chatty so a slow connection will make this painful.
>
Yeah, I'm connecting to a remote DB over a VPN, but the app is local. It's slow at the office too (as you saw last week), but this is over the top.
>> NSLog - <WOWorkerThread id=12 socket=Socket[addr=/127.0.0.1,port=65356,localport=5557]> Exception while sending response: java.net.
>> SocketException: Broken pipe
>
> That is normal, it just means the browser stopped waiting.
>
That's what I figured.
>>
>> I am not sure if the different ports shown in the above line is relevant (my launch arguments set the port 5557): addr=/127.0.0.1,port=65356,localport=5557
>
> You can safely ignore that.
Cool, thanks.
>> This follows a "request did take too long" exception which I have gotten for months, but which never caused the app to fail before this. Yes, I know, ideally, logging in should not take nearly as long as it does, but I have no control over that. The design of the app (several of our apps have this issue) requires fairly complex visibility determinations, which require many database rows and schemas to be touched. In any event, people way above my pay grade have control over these things.
>
> I will strongly suggest that you use a WOLongReponsePage (or Wonder equivalent) then to process login
>
I will bring that up to the powers that be. Apparently, in production, it's fast enough that people don't complain. It's just the poor hopeless devs that have to suffer. Does seem that if WO offers a better way we should take it though.
>
>> Sep 01 09:33:28 MyApp[5557] ERROR er.extensions.statistics.ERXStatisticsStore - Request did take too long : 107901ms request was: login
>
> That IS too long ;-)
On the other hand, while waiting for the app to run, I can do the laundry, walk the dog, invest, etc. All works out I guess.
...
>> Per Chuck's suggestion last week, I went into JavaMonitor and set the site timeout to 180 seconds. That did not seem to have much effect. I do not have the applications set up in JavaMonitor, as they are running from Eclipse, and in any event, I am not sure how one would do that, without a build to point the executable to. Presumably, there is one, but I am not certain how I should proceed.
>
> I still think the woadaptor should pay attention to that, I don't have the time to rest right now.
>
>
> Chuck
Thanks. The immediate issue is resolved, so now I just have to discover the no doubt irrefutable logic for why they're making me suffer.
Andrew
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden