Yes, it sounds like for some strange reason you lost the ServletExec
license.  It may have inadvertently been stripped at some point by
accident and the reboot caused the server to re-read the config file.
If it happens again go into ServletExec admin tool and check to make
sure it is licensed.  The problem now is that it is fixed by the reboot
so you'll have to probably wait for this to happen again.
:) 
 

Candace DeCou

DOI Remedy Systems Analyst 
Verizon Business 
Office:  (408) 371-1112

Email: [EMAIL PROTECTED] 

 

Verizon Business - global capability, personal accountability. 

This e-mail is strictly confidential and intended only for use by the
addressee unless otherwise indicated

 

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Heider, Stephen
Sent: Monday, February 04, 2008 1:07 PM
To: arslist@ARSLIST.ORG
Subject: ServletExec Max Concurrent Requests Exceeded


** 

All users receiving this error from mid tier server:

 


ServletExec Max Concurrent Requests Exceeded


When not registered, ServletExec supports a maximum of 3 concurrent
requests.

 

 

Nothing has changed on that server for a long time, except flushing the
cache periodically.  I rebooted the mid-tier server and everything
appears fine now.  Any idea as to how this may have occurred?

 

ARS server

ARS 6.3 p22

SQL Server 2000

Windows Server 2003

 

Mid Tier server

Mid Tier 6.3 p22

Windows Server 2003

IIS 6

New Atlanta ServletExec  5.0 (from the ARS 6.3 mid-tier installation
program)

 

Thanks.

 

Stephen 

Remedy Skilled Professional



 

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___ 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to