So its time you investigate what this MuxServlet is doing... regards Leon
On Wed, Jan 12, 2011 at 9:31 AM, Amol Puglia <amolcpug...@yahoo.com> wrote: > Hello Rainer Jung, > > Thanks for the response. > > I can see there are many threads like below which are in sleep state. > > I have taken thread dumps 4 or 5 times and can see this threads in all the > dumps. > > For the instance i am pasting some of similar kind of threads from the thread > dump. > > I have to show this to developers but before that i have to be very much sure > there is no issue from apache web server or tomcat application server end. > > "TP-Processor1" daemon prio=5 tid=0x000a8538 nid=0x24 waiting on condition > [9747e000..9747fc30] > at java.lang.Thread.sleep(Native Method) > at com.ericsson.eai.b2b.MUXServlet.doPost(MUXServlet.java:506) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:307) > at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385) > at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748) > at > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678) > at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) > at java.lang.Thread.run(Thread.java:534) > > > "TP-Processor2" daemon prio=5 tid=0x000a90c0 nid=0x25 waiting on condition > [9737e000..9737fc30] > at java.lang.Thread.sleep(Native Method) > at com.ericsson.eai.b2b.MUXServlet.doPost(MUXServlet.java:506) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:307) > at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385) > at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748) > at > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678) > at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) > at java.lang.Thread.run(Thread.java:534) > > > > > > > --- On Tue, 1/11/11, Rainer Jung <rainer.j...@kippdata.de> wrote: > > From: Rainer Jung <rainer.j...@kippdata.de> > Subject: Re: Apache Process going high even after restart of backend server > tomcat > To: "Tomcat Users List" <users@tomcat.apache.org> > Date: Tuesday, January 11, 2011, 10:51 PM > > On 10.01.2011 17:00, Amol Puglia wrote: >> Hello Team, >> >> I am facing very weird problem of apache porcess going high upto 259 and >> increasing again even after restart of backend server ie. tomcat. >> >> Apache version :- 2.0.59 >> >> Tomcat Version :- 5.5.9 >> >> Apache/Tomcat connectivity :- mod_jk >> >> when i have checked mod_jk.log file i am seeing this messages in the logs. >> >> [Mon Jan 10 08:14:52 2011] worker1 erib2bdev.ericsson.net 0.001122 >> [Mon Jan 10 08:14:55 2011] worker1 erib2bdev.ericsson.net 0.000732 >> [Mon Jan 10 08:14:57 2011] worker1 erib2bdev.ericsson.net 0.000740 >> [Mon Jan 10 08:15:00 2011] worker1 erib2bdev.ericsson.net 0.000846 >> [Mon Jan 10 08:15:02 2011] worker1 erib2bdev.ericsson.net 0.000952 > > As I already wrote on the httpd users list: > > The lines come from the JkRequestLogFormat configuration setting that you > must have added somewhere (default: no such setting, no lines). The > configured format will tell you, what the entry means. Likely it is either > the name of the virtual host, or the value of the host header the client > sent. Cleartext: this is requests being processed by your Apache server. The > client sends these requests to "erib2bdev.ericsson.net" and they are received > by your server. Or you configured your server to carry the name > "erib2bdev.ericsson.net". > > For details see: > > http://tomcat.apache.org/connectors-doc/reference/apache.html > > and look for "JkRequestLogFormat" in that page. > > The use of that directive is no longer recommended, because it is easier to > include request log information into the usual access log via mod_log_config. > Look for "mod_log_config" in the same page. > >> I am not sure what does it mean when the name "erib2bdev.ericsson.net" is >> not refereed anywhere in my apache and tomcat configuration files and not >> even in workers.properties file. Can anyone help me torubleshoot this issue? > > Furthermore this might not have to do with your issue, namely that you think > the number of Apache processes is to big. From the other thread you posted > containing the Java thread Dump excerpt we think that the reason for the > growing number of processes is, that your MUXServlet doesn't handle the > request and instead enters sleep. To make this assumption a fact, you would > need to tell us, whether there are many threads in the same dump, that have > the same stack (sleep in MUXServlet), more precisely how many and what the > names of the threads are. If you find let's say 200 of those, then you are > close to an explanation. > > Finally you have to do more than one dump to understand, whether the sleep() > was only lasting for a short time, or it is happening all the time. Then you > have to start talking to the developers of the MUXServlet showing them those > dumps. > > Regards, > > Rainer > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
