Re: Tomcat 4.1.29 CoyoteAdapter Exception
Randall, I've often had issues that cause major problems, and my experience is that user groups and mailing lists are normally unable to help without there being an easily reproducible error. For instance, are you able to nail it down to a particular page or servlet? Does it happen regularly or at random? Can you make a test case? Sorry I can't be any help, but good luck finding it. Adam On 02/25/2004 12:03 AM Randall Svancara wrote: What would cause the coyote connector to return a null pointer exception. Every time this happens, mod_jk is unable to communicate with tomcat and as a result our web service is unusable. Is this a tomcat bug, or a problem with running tomcat on Windows XP. Anyway, I have looked through this user group and found some other people with this problem on Solaris, but no real answers. Thanks. I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on Windows XP. Occasionally, I will receive the following error: 2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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:193) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) 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.java:666) at java.lang.Thread.run(Thread.java:534) -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 11:34 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Here is my server.xml in full for anyone interested. It is at the end of this email. -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 11:14 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Hmm...I am unable to find anything in google regarding this error. -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 8:48 AM To: [EMAIL PROTECTED] Subject: Tomcat 4.1.29 CoyoteAdapter Exception Hi, I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on Windows XP. Occasionally, I will receive the following error: 2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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:193) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) 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.java:666) at java.lang.Thread.run(Thread.java:534) At which point the web service becomes UNAVAILABLE on port 80 through apache which forwards the requests via mod_jk to the tomcat 4.1.29 servlet engine. I am including some snippets from my server.xml below for the coyote connector. Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8019 minProcessors=100 maxProcessors=600 enableLookups=false redirectPort=8443 acceptCount=10 debug=10 connectionTimeout=6 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ I have also configured apache with 600 max threads, see snippet below. # WinNT MPM # ThreadsPerChild: constant number of worker threads in the server process # MaxRequestsPerChild: maximum number of requests a server process serves IfModule mpm_winnt.c ThreadsPerChild 600 MaxRequestsPerChild 0 /IfModule If someone has any idea what I have misconfigured
RE: Tomcat 4.1.29 CoyoteAdapter Exception
Thanks, I have had a difficult time reproducing this error on a predictable basis. All I can say is that it happens once per day, and I have temporarily wrote a perl script that checks the service to see if it is working properly, and if not, it shuts down tomcat and restarts it...A bandaid fix at best. I will give you a little more background on the webapp I have deployed. It is just a basic webapp with several jsp pages and a couple of servlets. I am using Database Connection Pooling with Mysql Connector J. The problem does not appear to happen on any one particular jsp or servlet, but I will keep digging further to see if it is or not. If I can create a reproducable test case, I will post it here. I will keep on researching the problem to see if I can pin point the exact error. Thanks for the advice on using news groups. It is my first experience with them. Thanks, Randall -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 2:47 AM To: Tomcat Users List Subject: Re: Tomcat 4.1.29 CoyoteAdapter Exception Randall, I've often had issues that cause major problems, and my experience is that user groups and mailing lists are normally unable to help without there being an easily reproducible error. For instance, are you able to nail it down to a particular page or servlet? Does it happen regularly or at random? Can you make a test case? Sorry I can't be any help, but good luck finding it. Adam On 02/25/2004 12:03 AM Randall Svancara wrote: What would cause the coyote connector to return a null pointer exception. Every time this happens, mod_jk is unable to communicate with tomcat and as a result our web service is unusable. Is this a tomcat bug, or a problem with running tomcat on Windows XP. Anyway, I have looked through this user group and found some other people with this problem on Solaris, but no real answers. Thanks. I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on Windows XP. Occasionally, I will receive the following error: 2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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:193) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) 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.java:666) at java.lang.Thread.run(Thread.java:534) -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 11:34 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Here is my server.xml in full for anyone interested. It is at the end of this email. -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 11:14 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Hmm...I am unable to find anything in google regarding this error. -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 8:48 AM To: [EMAIL PROTECTED] Subject: Tomcat 4.1.29 CoyoteAdapter Exception Hi, I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on Windows XP. Occasionally, I will receive the following error: 2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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:193) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387
RE: Tomcat 4.1.29 CoyoteAdapter Exception
Ok, now I am thinking this error might be caused by Database Connection pooling. I increased Mysql's max connection limit from the default to 500. I hope this enough to satify my hungry application. Also I adjusted the apps xml configuration option maxActive to a value of 400 which is 100 less than the max. We will see if this works. -Original Message- From: Randall Svancara [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 7:47 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Thanks, I have had a difficult time reproducing this error on a predictable basis. All I can say is that it happens once per day, and I have temporarily wrote a perl script that checks the service to see if it is working properly, and if not, it shuts down tomcat and restarts it...A bandaid fix at best. I will give you a little more background on the webapp I have deployed. It is just a basic webapp with several jsp pages and a couple of servlets. I am using Database Connection Pooling with Mysql Connector J. The problem does not appear to happen on any one particular jsp or servlet, but I will keep digging further to see if it is or not. If I can create a reproducable test case, I will post it here. I will keep on researching the problem to see if I can pin point the exact error. Thanks for the advice on using news groups. It is my first experience with them. Thanks, Randall -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 2:47 AM To: Tomcat Users List Subject: Re: Tomcat 4.1.29 CoyoteAdapter Exception Randall, I've often had issues that cause major problems, and my experience is that user groups and mailing lists are normally unable to help without there being an easily reproducible error. For instance, are you able to nail it down to a particular page or servlet? Does it happen regularly or at random? Can you make a test case? Sorry I can't be any help, but good luck finding it. Adam On 02/25/2004 12:03 AM Randall Svancara wrote: What would cause the coyote connector to return a null pointer exception. Every time this happens, mod_jk is unable to communicate with tomcat and as a result our web service is unusable. Is this a tomcat bug, or a problem with running tomcat on Windows XP. Anyway, I have looked through this user group and found some other people with this problem on Solaris, but no real answers. Thanks. I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on Windows XP. Occasionally, I will receive the following error: 2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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:193) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) 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.java:666) at java.lang.Thread.run(Thread.java:534) -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 11:34 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Here is my server.xml in full for anyone interested. It is at the end of this email. -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 11:14 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Hmm...I am unable to find anything in google regarding this error. -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 8:48 AM To: [EMAIL PROTECTED] Subject: Tomcat 4.1.29 CoyoteAdapter Exception Hi, I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on Windows XP. Occasionally, I will receive the following error: 2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke
RE: Tomcat 4.1.29 CoyoteAdapter Exception
After further investigation, I am just going to chalk this one up as a stability issue with windows XP. The same version of tomcat running with same configuration on linux can sustain well over 1+++ hits using jmeter while the same configuration on windows barely handles 2000 hits before tomcat fails. Anyone know of a stable version of tomcat that works with windows. Do I need to downgrade to 4.0.x or upgrade to 5.0.x versions of tomcat for better stability on windowsor do I need to convince my boss what I have know all along, linux is superior to windows. Thanks. Randall -Original Message- From: Randall Svancara [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 8:05 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Ok, now I am thinking this error might be caused by Database Connection pooling. I increased Mysql's max connection limit from the default to 500. I hope this enough to satify my hungry application. Also I adjusted the apps xml configuration option maxActive to a value of 400 which is 100 less than the max. We will see if this works. -Original Message- From: Randall Svancara [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 7:47 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Thanks, I have had a difficult time reproducing this error on a predictable basis. All I can say is that it happens once per day, and I have temporarily wrote a perl script that checks the service to see if it is working properly, and if not, it shuts down tomcat and restarts it...A bandaid fix at best. I will give you a little more background on the webapp I have deployed. It is just a basic webapp with several jsp pages and a couple of servlets. I am using Database Connection Pooling with Mysql Connector J. The problem does not appear to happen on any one particular jsp or servlet, but I will keep digging further to see if it is or not. If I can create a reproducable test case, I will post it here. I will keep on researching the problem to see if I can pin point the exact error. Thanks for the advice on using news groups. It is my first experience with them. Thanks, Randall -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 2:47 AM To: Tomcat Users List Subject: Re: Tomcat 4.1.29 CoyoteAdapter Exception Randall, I've often had issues that cause major problems, and my experience is that user groups and mailing lists are normally unable to help without there being an easily reproducible error. For instance, are you able to nail it down to a particular page or servlet? Does it happen regularly or at random? Can you make a test case? Sorry I can't be any help, but good luck finding it. Adam On 02/25/2004 12:03 AM Randall Svancara wrote: What would cause the coyote connector to return a null pointer exception. Every time this happens, mod_jk is unable to communicate with tomcat and as a result our web service is unusable. Is this a tomcat bug, or a problem with running tomcat on Windows XP. Anyway, I have looked through this user group and found some other people with this problem on Solaris, but no real answers. Thanks. I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on Windows XP. Occasionally, I will receive the following error: 2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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:193) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) 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.java:666) at java.lang.Thread.run(Thread.java:534) -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 11:34 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Here is my server.xml in full for anyone interested. It is at the end of this email. -Original Message- From: Randall Svancara Sent: Tuesday, February 24
Re: Tomcat 4.1.29 CoyoteAdapter Exception
I had an issue with tomcat 4.1.x (don't remember which - but it was Feb. last year) and sun java 1.4 Tomcat would just hang at random times and require a restart. I downgraded to java 1.3 to solve it. Try another Java - perhaps from IBM. Or check bugzilla. Adam On 02/25/2004 07:39 PM Randall Svancara wrote: After further investigation, I am just going to chalk this one up as a stability issue with windows XP. The same version of tomcat running with same configuration on linux can sustain well over 1+++ hits using jmeter while the same configuration on windows barely handles 2000 hits before tomcat fails. Anyone know of a stable version of tomcat that works with windows. Do I need to downgrade to 4.0.x or upgrade to 5.0.x versions of tomcat for better stability on windowsor do I need to convince my boss what I have know all along, linux is superior to windows. Thanks. Randall -Original Message- From: Randall Svancara [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 8:05 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Ok, now I am thinking this error might be caused by Database Connection pooling. I increased Mysql's max connection limit from the default to 500. I hope this enough to satify my hungry application. Also I adjusted the apps xml configuration option maxActive to a value of 400 which is 100 less than the max. We will see if this works. -Original Message- From: Randall Svancara [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 7:47 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Thanks, I have had a difficult time reproducing this error on a predictable basis. All I can say is that it happens once per day, and I have temporarily wrote a perl script that checks the service to see if it is working properly, and if not, it shuts down tomcat and restarts it...A bandaid fix at best. I will give you a little more background on the webapp I have deployed. It is just a basic webapp with several jsp pages and a couple of servlets. I am using Database Connection Pooling with Mysql Connector J. The problem does not appear to happen on any one particular jsp or servlet, but I will keep digging further to see if it is or not. If I can create a reproducable test case, I will post it here. I will keep on researching the problem to see if I can pin point the exact error. Thanks for the advice on using news groups. It is my first experience with them. Thanks, Randall -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 2:47 AM To: Tomcat Users List Subject: Re: Tomcat 4.1.29 CoyoteAdapter Exception Randall, I've often had issues that cause major problems, and my experience is that user groups and mailing lists are normally unable to help without there being an easily reproducible error. For instance, are you able to nail it down to a particular page or servlet? Does it happen regularly or at random? Can you make a test case? Sorry I can't be any help, but good luck finding it. Adam On 02/25/2004 12:03 AM Randall Svancara wrote: What would cause the coyote connector to return a null pointer exception. Every time this happens, mod_jk is unable to communicate with tomcat and as a result our web service is unusable. Is this a tomcat bug, or a problem with running tomcat on Windows XP. Anyway, I have looked through this user group and found some other people with this problem on Solaris, but no real answers. Thanks. I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on Windows XP. Occasionally, I will receive the following error: 2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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:193) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) 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.java:666) at java.lang.Thread.run(Thread.java:534) -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 11:34 AM To: Tomcat Users List
RE: Tomcat 4.1.29 CoyoteAdapter Exception
Adam, thanks for the response, I will try your suggestions. Thanks again, Randall -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 3:50 PM To: Tomcat Users List Subject: Re: Tomcat 4.1.29 CoyoteAdapter Exception I had an issue with tomcat 4.1.x (don't remember which - but it was Feb. last year) and sun java 1.4 Tomcat would just hang at random times and require a restart. I downgraded to java 1.3 to solve it. Try another Java - perhaps from IBM. Or check bugzilla. Adam On 02/25/2004 07:39 PM Randall Svancara wrote: After further investigation, I am just going to chalk this one up as a stability issue with windows XP. The same version of tomcat running with same configuration on linux can sustain well over 1+++ hits using jmeter while the same configuration on windows barely handles 2000 hits before tomcat fails. Anyone know of a stable version of tomcat that works with windows. Do I need to downgrade to 4.0.x or upgrade to 5.0.x versions of tomcat for better stability on windowsor do I need to convince my boss what I have know all along, linux is superior to windows. Thanks. Randall -Original Message- From: Randall Svancara [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 8:05 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Ok, now I am thinking this error might be caused by Database Connection pooling. I increased Mysql's max connection limit from the default to 500. I hope this enough to satify my hungry application. Also I adjusted the apps xml configuration option maxActive to a value of 400 which is 100 less than the max. We will see if this works. -Original Message- From: Randall Svancara [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 7:47 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Thanks, I have had a difficult time reproducing this error on a predictable basis. All I can say is that it happens once per day, and I have temporarily wrote a perl script that checks the service to see if it is working properly, and if not, it shuts down tomcat and restarts it...A bandaid fix at best. I will give you a little more background on the webapp I have deployed. It is just a basic webapp with several jsp pages and a couple of servlets. I am using Database Connection Pooling with Mysql Connector J. The problem does not appear to happen on any one particular jsp or servlet, but I will keep digging further to see if it is or not. If I can create a reproducable test case, I will post it here. I will keep on researching the problem to see if I can pin point the exact error. Thanks for the advice on using news groups. It is my first experience with them. Thanks, Randall -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 2:47 AM To: Tomcat Users List Subject: Re: Tomcat 4.1.29 CoyoteAdapter Exception Randall, I've often had issues that cause major problems, and my experience is that user groups and mailing lists are normally unable to help without there being an easily reproducible error. For instance, are you able to nail it down to a particular page or servlet? Does it happen regularly or at random? Can you make a test case? Sorry I can't be any help, but good luck finding it. Adam On 02/25/2004 12:03 AM Randall Svancara wrote: What would cause the coyote connector to return a null pointer exception. Every time this happens, mod_jk is unable to communicate with tomcat and as a result our web service is unusable. Is this a tomcat bug, or a problem with running tomcat on Windows XP. Anyway, I have looked through this user group and found some other people with this problem on Solaris, but no real answers. Thanks. I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on Windows XP. Occasionally, I will receive the following error: 2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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:193) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673
RE: Tomcat 4.1.29 CoyoteAdapter Exception
Hmm...I am unable to find anything in google regarding this error. -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 8:48 AM To: [EMAIL PROTECTED] Subject: Tomcat 4.1.29 CoyoteAdapter Exception Hi, I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on Windows XP. Occasionally, I will receive the following error: 2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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:193) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) 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.java:666) at java.lang.Thread.run(Thread.java:534) At which point the web service becomes UNAVAILABLE on port 80 through apache which forwards the requests via mod_jk to the tomcat 4.1.29 servlet engine. I am including some snippets from my server.xml below for the coyote connector. Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8019 minProcessors=100 maxProcessors=600 enableLookups=false redirectPort=8443 acceptCount=10 debug=10 connectionTimeout=6 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ I have also configured apache with 600 max threads, see snippet below. # WinNT MPM # ThreadsPerChild: constant number of worker threads in the server process # MaxRequestsPerChild: maximum number of requests a server process serves IfModule mpm_winnt.c ThreadsPerChild 600 MaxRequestsPerChild 0 /IfModule If someone has any idea what I have misconfigured or if you need more information, let me know. I am desperate at this point to find the root of this problem that has been plaguing our website since its release January. Thank you, Randall Svancara - 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: Tomcat 4.1.29 CoyoteAdapter Exception
Here is my server.xml in full for anyone interested. It is at the end of this email. -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 11:14 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Hmm...I am unable to find anything in google regarding this error. -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 8:48 AM To: [EMAIL PROTECTED] Subject: Tomcat 4.1.29 CoyoteAdapter Exception Hi, I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on Windows XP. Occasionally, I will receive the following error: 2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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:193) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) 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.java:666) at java.lang.Thread.run(Thread.java:534) At which point the web service becomes UNAVAILABLE on port 80 through apache which forwards the requests via mod_jk to the tomcat 4.1.29 servlet engine. I am including some snippets from my server.xml below for the coyote connector. Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8019 minProcessors=100 maxProcessors=600 enableLookups=false redirectPort=8443 acceptCount=10 debug=10 connectionTimeout=6 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ I have also configured apache with 600 max threads, see snippet below. # WinNT MPM # ThreadsPerChild: constant number of worker threads in the server process # MaxRequestsPerChild: maximum number of requests a server process serves IfModule mpm_winnt.c ThreadsPerChild 600 MaxRequestsPerChild 0 /IfModule If someone has any idea what I have misconfigured or if you need more information, let me know. I am desperate at this point to find the root of this problem that has been plaguing our website since its release January. Thank you, Randall Svancara - 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] !-- Example Server Configuration File -- !-- Note that component elements are nested corresponding to their parent-child relationships with each other -- !-- A Server is a singleton element that represents the entire JVM, which may contain one or more Service instances. The Server listens for a shutdown command on the indicated port. Note: A Server is not itself a Container, so you may not define subcomponents such as Valves or Loggers at this level. -- Server port=8005 shutdown=SHUTDOWN debug=0 !-- Uncomment these entries to enable JMX MBeans support -- Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener debug=0/ !-- Global JNDI resources -- GlobalNamingResources !-- Test entry for demonstration purposes -- Environment name=simpleValue type=java.lang.Integer value=30/ !-- Editable user database that can also be used by UserDatabaseRealm to authenticate users -- Resource name=UserDatabase auth=Container type=org.apache.catalina.UserDatabase description=User database that can be updated and saved /Resource ResourceParams name=UserDatabase parameter namefactory/name valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value /parameter parameter namepathname/name valueconf/tomcat-users.xml/value /parameter /ResourceParams /GlobalNamingResources !-- A Service
RE: Tomcat 4.1.29 CoyoteAdapter Exception
What would cause the coyote connector to return a null pointer exception. Every time this happens, mod_jk is unable to communicate with tomcat and as a result our web service is unusable. Is this a tomcat bug, or a problem with running tomcat on Windows XP. Anyway, I have looked through this user group and found some other people with this problem on Solaris, but no real answers. Thanks. I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on Windows XP. Occasionally, I will receive the following error: 2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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:193) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) 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.java:666) at java.lang.Thread.run(Thread.java:534) -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 11:34 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Here is my server.xml in full for anyone interested. It is at the end of this email. -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 11:14 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.29 CoyoteAdapter Exception Hmm...I am unable to find anything in google regarding this error. -Original Message- From: Randall Svancara Sent: Tuesday, February 24, 2004 8:48 AM To: [EMAIL PROTECTED] Subject: Tomcat 4.1.29 CoyoteAdapter Exception Hi, I am running tomcat 4.1.29, apache 2.0.48, with mod_jk configured on Windows XP. Occasionally, I will receive the following error: 2004-02-23 15:40:07 CoyoteAdapter Requested cookie session id is A02AD09BF242D0D916799B2EBB0FCC92.worker1 2004-02-23 15:40:07 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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:193) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) 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.java:666) at java.lang.Thread.run(Thread.java:534) At which point the web service becomes UNAVAILABLE on port 80 through apache which forwards the requests via mod_jk to the tomcat 4.1.29 servlet engine. I am including some snippets from my server.xml below for the coyote connector. Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8019 minProcessors=100 maxProcessors=600 enableLookups=false redirectPort=8443 acceptCount=10 debug=10 connectionTimeout=6 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ I have also configured apache with 600 max threads, see snippet below. # WinNT MPM # ThreadsPerChild: constant number of worker threads in the server process # MaxRequestsPerChild: maximum number of requests a server process serves IfModule mpm_winnt.c ThreadsPerChild 600 MaxRequestsPerChild 0 /IfModule If someone has any idea what I have misconfigured or if you need more information, let me know. I am desperate at this point to find the root of this problem that has been plaguing our
