• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Starting second instance=app not available
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Starting second instance=app not available

  • Subject: Re: Starting second instance=app not available
  • From: Chuck Hill <email@hidden>
  • Date: Tue, 04 Mar 2014 01:52:46 +0000
  • Thread-topic: Starting second instance=app not available


On 2014-03-03, 5:49 PM, "Jeffrey Schmitz" wrote:

Will have to wait until later tonight when things quiet down for the jstack command

I do have another server setup with the same load that serves a different site and that is functioning fine.

Something is different.  :-)


Would I see any stack traces if it's deadlock?  I'm not seeing anything in any of the log files.

Yes.



Isolation level is set to:
dbConnectURLGLOBAL=jdbc:FrontBase://localhost/netBrackets/isolation=read_committed/locking=optimistic

Looks correct.



Should I be using localhost or the IP or the domain name here?

Should not matter.


Chuck




Thanks!
Jeff

On Mar 3, 2014, at 7:25 PM, Chuck Hill <email@hidden> wrote:

Do a 
Sudo jstack –F <process ID>
On the instances when this happens.  My guess is that they are contending for a resource and neither is able to process requests.   Deadlock would be my guess, maybe the wrong isolation level on the DB connection? This then gets escalated to dead and mis-reported as No Instance Available.


Chuck


On 2014-03-03, 4:57 PM, "Jeffrey Schmitz" wrote:

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

 
 _______________________________________________
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
  • Follow-Ups:
    • Re: Starting second instance=app not available
      • From: Jeffrey Schmitz <email@hidden>
References: 
 >Starting second instance=app not available (From: Jeffrey Schmitz <email@hidden>)
 >Re: Starting second instance=app not available (From: Chuck Hill <email@hidden>)
 >Re: Starting second instance=app not available (From: Jeffrey Schmitz <email@hidden>)

  • Prev by Date: Re: Starting second instance=app not available
  • Next by Date: Re: Starting second instance=app not available
  • Previous by thread: Re: Starting second instance=app not available
  • Next by thread: Re: Starting second instance=app not available
  • Index(es):
    • Date
    • Thread