Hi Andrew, On Sep 1, 2010, at 9:57 AM, Andrew R. Kinnie wrote:
> Hmm. OK, so I was at WOWODC and could not remember what deployment questions > I wanted to ask in the labs until I got home. :-) > 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. > It seems to no matter how many times I reload. When I was at the office, > I'd usually get it the first time or two, then it would load. It was > annoying, but usable. > > As background, I run the app, get our login page, then when you attempt to > login, eclipse shows the app doing its thing, but eventually it apparently > times out, I get the error page, and the Eclipse console shows "Broken Pipe." > > > 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. > > 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. > 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 > 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 ;-) > In any event, I decided to try and go back to Direct Connect, at least while > on VPN. I looked at what I did to configure it, and it looked like some > apache configuration, and some launch arguments. I thought perhaps the > apache stuff would only be relevant if I actually was running through apache, > so I deleted launch arguments and did not set apache back to the original > settings. However, now I get a different error: "The requested application > is not available on this server." > > I'd like to get the apache configuration to work without timing out as fast > as it does, but if not, I'd like to be able to go back to running through > Direct Connect without having to revert back to the vanilla apache. I see you got that figured out already. > 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 -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
