Peter

last year we targeted IBMWebsphere war files but experienced deployment 
anomalies
when dual deploying first to IBM-Websphere6 and then to Tomcat6. We noticed 
IBM-Websphere Server pegging stack/heap after just one webapp was deployed

we experienced no resource limitations when redeploying standalone to just 
Tomcat6 (as evidenced by log/output from jheap, jstack and jconsole and top)
does IBMwebsphere have <any> resource limitations that can be overcome by 
porting standalone wars to Tomcat 6.0.6?

my apologies on interrupting thread or any miscommunication carried within
Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.






> Date: Fri, 30 Oct 2009 11:28:34 +0000
> Subject: Re: tomcat utilization is 100 %
> From: peter.crowt...@melandra.com
> To: users@tomcat.apache.org
> 
> 2009/10/30 Vikram S Chauhan <vikram.chau...@in.ibm.com>:
> > I am Vikram Chauhan from New Delhi India and working for one telecom
> > client. i have installed tomcat 6.6 on my one Application server having
> > windows 2003 server environment. from last some days its utilization is
> > going 90% or 95%  . due to this lots of problem are coming . some
> > application are impacting due to low resources of windows memory.
> 
> (There is no Tomcat 6.6.  Do you mean Tomcat 6.0.6?)
> 
> The most likely reason is a problem within your own application.  Take
> a thread dump (the method for doing this varies depending on which
> Java version you're running, but "jstack" will work with a reasonably
> modern JVM).  You'll find the output in one of the Tomcat log files,
> unless your application is doing something very odd with the logging.
> Then ask look at what the running threads are doing - I suspect you'll
> fairly rapidly find the problem.
> 
> Also, check your Java configuration.  If other applications are
> running out of memory, you have given Java too much memory or
> resources other than the Java heap are taking lots of memory.  For
> example, does your application open large numbers of sockets or files
> but never close them properly?
> 
> - Peter
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
                                          
_________________________________________________________________
Windows 7: I wanted more reliable, now it's more reliable. Wow!
http://microsoft.com/windows/windows-7/default-ga.aspx?h=myidea?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_myidea:102009

Reply via email to