RE: HP-UX misbehaving AGAIN
Wendy, There are also a number of HP recommended tunes you can do the kernal of HP-UX to improve performance for tomcat & apache httpd - provided you have a busy system. Some easy ones are: maxuprc default=75, recommend 3500 nproc default=(20+8*MAXUSERS), recommend (20+32*MAXUSERS) max_thread_proc default=64, recommend 2048 dbc_max_pct default=50, recommend 30 dbc_min_pct default=2, recommend 15 tcphashsz = 32000 See HP's site for more detail. --Dan > -Original Message- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > Sent: Monday, December 06, 2004 10:51 AM > To: Tomcat Users List > Subject: Re: HP-UX misbehaving AGAIN > > > From: "Tim Funk" <[EMAIL PROTECTED]> > > http://jakarta.apache.org/tomcat/faq/memory.html#why > > > > After a long battle with HP-UX - I love the performance I > get on it. Odds > are > > - your memory issues have to do with process/thread limits. > > Thank you for the tip! It turned out to be that Tomcat was > out of threads, > according to a message in catalina.out. In server.xml, > maxThreads was set > to 75, and I read that it should be set to the same thing as Apache's > MaxClients, which was 150. I probably did that to myself, we > install Apache > and Tomcat from HP's 'depot' but then I replace Tomcat as > they always lag > behind. > > Crisis averted for the moment! Thanks again for your help. > -- > Wendy Smoak > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HP-UX misbehaving AGAIN
From: "Tim Funk" <[EMAIL PROTECTED]> > http://jakarta.apache.org/tomcat/faq/memory.html#why > > After a long battle with HP-UX - I love the performance I get on it. Odds are > - your memory issues have to do with process/thread limits. Thank you for the tip! It turned out to be that Tomcat was out of threads, according to a message in catalina.out. In server.xml, maxThreads was set to 75, and I read that it should be set to the same thing as Apache's MaxClients, which was 150. I probably did that to myself, we install Apache and Tomcat from HP's 'depot' but then I replace Tomcat as they always lag behind. Crisis averted for the moment! Thanks again for your help. -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HP-UX misbehaving AGAIN
Just because the server has 4GB of RAM doesn't mean the JVM is free to take whatever it needs. Increasing the initial and maximum heap sizes. For example, passing the -Xms64m argument to the JVM when starting Tomcat will set the initial heap size to 64MB. Passing -Xmx128m will set the maximum heap size of 128MB. These are just suggestions. You should read up on these options so you can decide what to use based on the demands of your web application. >>> [EMAIL PROTECTED] 12/3/2004 5:40:40 PM >>> I'm beginning to have some REALLY unkind thoughts about HP-UX. Yet again, what works perfectly fine on my [Win2000] development machine, has major problems when deployed to HP-UX. Every single request to this webapp produces the error below. The server has 4 GB of memory, and it's an authentication (login) webapp, it's not doing anything memory intensive. What do you mean, OutOfMemoryError?! I have no idea how to even begin trying to figure out what's wrong. :( 2004-12-03 15:42:35 StandardWrapperValve[action]: Servlet.service() for servlet action threw exception javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2422) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:163 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:199) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:324) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:395) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:683) at java.lang.Thread.run(Thread.java:534) - Root Cause - java.lang.OutOfMemoryError -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HP-UX misbehaving AGAIN
http://jakarta.apache.org/tomcat/faq/memory.html#why After a long battle with HP-UX - I love the performance I get on it. Odds are - your memory issues have to do with process/thread limits. If you are running apache and tomcat on the same machine - run them as different userids since the sum of all the resources of all the process used by both may go over the kernel (or other configurable) limits. 99% of the time, OOM memory have nothing to do with memory but limits on files/sockets etc. -Tim Wendy Smoak wrote: I'm beginning to have some REALLY unkind thoughts about HP-UX. Yet again, what works perfectly fine on my [Win2000] development machine, has major problems when deployed to HP-UX. Every single request to this webapp produces the error below. The server has 4 GB of memory, and it's an authentication (login) webapp, it's not doing anything memory intensive. What do you mean, OutOfMemoryError?! I have no idea how to even begin trying to figure out what's wrong. :( 2004-12-03 15:42:35 StandardWrapperValve[action]: Servlet.service() for servlet action threw exception javax.servlet.ServletException: Servlet execution threw an exception a:683) at java.lang.Thread.run(Thread.java:534) - Root Cause - java.lang.OutOfMemoryError - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
