Mid-Tier hangs. Restarting the Apache Tomcat service clears the problem. The 
service doesn't crash so our service monitor doesn't detect it as a failure. 
The client sees a the error information listed below. Anybody else seeing this 
problem?  We're using the servlet and IIS.

Error:

HTTP Status 500

javax.servlet.ServletExceptoin: Servle execution thre an exception

java.lang.OutOfMemoryError: Java heap space


________________________________

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of strauss
Sent: Thursday, March 01, 2007 11:40 AM
To: [email protected]
Subject: Re: Remedy version 7 in production


** 
What problems are you seeing with Tomcat?? Are you using the Tomcat web 
component as well as the servlet, as opposed to using the servlet with IIS 
which requires the JK connector. Using the connector negates any improvements 
over IIS/SE, so we are testing both IIS/SE and the Tomcat 5.5 standalone 
configurations, as recommended by the October 2006 benchmark comparison of the 
ServletExec and Tomcat engines.
 
Tomcat 5.5.17 has been fairly stable during our testing (one JVM-induced crash 
on x64 server) since I set the memory pools to 512 MB and 1536 MB in the Java 
properties. The prefetch process gives you a good stress test - ours runs 35 
minutes (ITSM 7 minus Asset) and keeps the AR server at 30% CPU utilization the 
whole time. The mid-tier server using Tomcat has very little CPU usage during 
this time, but the one using IIS/SE has a steady 10 to 25% CPU usage.

Christopher Strauss, Ph.D.
Remedy Database Administrator
University of North Texas Computing Center
http://remedy.unt.edu/helpdesk/ 

________________________________

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Hendershot,Bruce D.
Sent: Thursday, March 01, 2007 8:29 AM
To: [email protected]
Subject: Re: Remedy version 7 in production 

** 
We are on version 7.0.01 as of 17 February.  Other than some instability of the 
Mid-tier, which is apparently caused by the Apache Tomcat component, we're 
seeing no problems.  We upgraded from 5.1.  We have 20+ applications in 
production, all home-grown.
 
Windows 2003
MS SQL Server 2005

________________________________

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Runar Helle
Sent: Thursday, March 01, 2007 9:03 AM
To: [email protected]
Subject: Remedy version 7 in production


** 

Hi, all

 

I was just wondering if anyone on this list has put Remedy version 7 into live 
production. If so, how is your experience so far? Is it stable once you have it 
up and running?

 

We are thinking about upgrading ARS, Midtier and Service desk. We also have 
some homemade applications that need to work on the new platform. Our ARS is 
currently on version 4 and the Helpdesk is on 6.3 (yes, it's old, but also 
exceptionally stable).

 

Best regards,

Runar

 

***********************************************
Runar Helle - IT-ingeniør, KDA IT 
Kongsberg Defence & Aerospace AS 
P.O. Box 1003, N-3616 Kongsberg 
NORWAY 
Office: (+47) 32 28 66 20 
Mobile: (+47) 951 91 986 
Email:  [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 

Web:   www.kongsberg.com

 ***********************************************

 

__20060125_______________________This posting was submitted with HTML in it___ 
__20060125_______________________This posting was submitted with HTML in it___ 
__20060125_______________________This posting was submitted with HTML in it___ 

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

Reply via email to