Starting second instance=app not available
Starting second instance=app not available
- Subject: Starting second instance=app not available
- From: Jeffrey Schmitz <email@hidden>
- Date: Mon, 03 Mar 2014 18:57:32 -0600
Hello,
Here's one I don't think I've seen. When I start a second instance on my server (mac OS Maverick Server), I start getting app not avaliable errors. Even if I try to get to the original instance directly through the url (append /1), I still get app not available. If I then set the new instance to not accept new sessions, or kill it, then the original instance will start taking requests again. Am hoping if nothing else a reboot tonight will fix this situation, but would be good to know what's really going on, and it worries that maybe the reboot won't fix it and I'll be hosed.
Note the new instances start fine, no errors are logged and everything looks good in JavaMonitor. Also, this just started. The server has been running for a couple weeks and I've been starting and stopping new instances all along (using Bounce) just fine. Any ideas?
Thanks!
Jeff
_______________________________________________
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