I think I found the problem, the fork paramter in tomcat was set to true for precompilation.
But, I think the trouble comes from mod_jk which open sessions and waiting response from Tomcat and If Tomcat don't is compiling a JSP page all the httpd sessions remains opened. Do you I'm in the good direction ? If yes, do you have a solution to avoid this ? -----Message d'origine----- De : Philippe Vollenweider [mailto:[EMAIL PROTECTED] Envoy� : vendredi 2 juillet 2004 14:19 � : [EMAIL PROTECTED] Objet : RE : RE : Trouble with Tomcat sessions The page or file http://intradev.interne.regioncentre.fr:8080/jahia/Jahia/pid/images/new_imag es/puce_ssm.gif ? Please try to change the maxProcessors (for exemple double the value) on tomcat/conf/server.xml file and also change the CATALINA_OPTS value (in tomcat/bin/catalina.sh) and set the Xmx to 1500m. /P. At 02.07.2004 12:16, you wrote: >That's means that you have an increase number of openings sessions and >you cannot reach an existing page. > >In fact this is a 404 error but the page really exists. > >When we are in this context, tomcat freeze means that you cannot >compile other JSP page; only the previous pages alreasy compiled are >available. > > > >-----Message d'origine----- >De : Philippe Vollenweider [mailto:[EMAIL PROTECTED] Envoy� : >vendredi 2 juillet 2004 12:11 � : [EMAIL PROTECTED] >Objet : RE : Trouble with Tomcat sessions > > >This error is only a 404 file not found... >I think that there is nothing to do with your problem... > >When you say that Tomcat freeze, what do you mean? that there is no >more avaliable connection (so you could change this setting in >tomcat/conf/server.xml), or no more memory? > >What about your CPU usage? > >Philippe. > > >At 02.07.2004 11:55, you wrote: > >Sun j2sdk1.4.2_04 > > > >Here is a sample error : > > > >2004-07-01 18:49:55 Your Jahia Server has generated an error. Please > >review the details below for additional information: Severity : ERROR > >Error : 404 Not found - Page:images, 404 error - page [images] could > >not be found in the database or is no longer accessible. URL : > >http://intradev.interne.regioncentre.fr:8080/jahia/Jahia/pid/images/new_ima >g > >es/puce_ssm.gif Method : GET > >Remote host : 10.40.1.11 Remote Address : 10.40.1.11 > >Request headers : > > accept:*/* > > referer:http://intradev.interne.regioncentre.fr:8080/jahia/Jahia/pid/86 > > accept-language:fr > > accept-encoding:gzip, deflate > > user-agent:Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; > >Q312461; .NET CLR 1.1.4322) > > host:intradev.interne.regioncentre.fr:8080 > > connection:Keep-Alive > > cookie:JSESSIONID=0734AB29CF617DB6F4B327B7005C11FF > >Stack trace : > >Cause level : 0 (level 0 is the most precise exception) > >org.jahia.exceptions.JahiaPageNotFoundException: 404 Not found - > >Page:images, 404 error - page [images] could not be found in the > >database >or > >is no longer accessible. > > at org.jahia.params.ParamBean.resolvePageID(ParamBean.java:3016) > > at org.jahia.params.ParamBean.<init>(ParamBean.java:474) > > at org.jahia.bin.Jahia.service(Jahia.java:760) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > > at > >org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl > >icatio >n > >FilterChain.java:247) > > at > >org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF > >ilterC >h > >ain.java:193) > > at > >org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV > >alve.j >a > >va:256) > > at > >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex > >t.invo >k > >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(StandardContextV > >alve.j >a > >va:191) > > at > >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex > >t.invo >k > >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:2416) > > at > >org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j > >ava:18 >0 > >) > > at > >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex > >t.invo >k > >eNext(StandardPipeline.java:643) > > at > >org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche > >rValve >. > >java:171) > > at > >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex > >t.invo >k > >eNext(StandardPipeline.java:641) > > at > >org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j > >ava:17 >2 > >) > > at > >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex > >t.invo >k > >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(StandardEngineVal > >ve.jav >a > >:174) > > at > >org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex > >t.invo >k > >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:223) > > at > >org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:601) > > at > >org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce > >ssConn >e > >ction(Http11Protocol.java:392) > > at > >org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) > > at > >org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP > >ool.ja >v > >a:619) > > at java.lang.Thread.run(Thread.java:534) > > > > > > > > > > > > > >-----Message d'origine----- > >De : Philippe Vollenweider [mailto:[EMAIL PROTECTED] Envoy� : > >vendredi 2 juillet 2004 11:49 � : [EMAIL PROTECTED] Objet : Re: > >Trouble with Tomcat sessions > > > > > >Hello, > > > >What kind of messages do you have in your console (or catalina.out) > >file? Which java virtual machine do you use? > > > >Philippe. > > > >At 02.07.2004 11:35, you wrote: > > >Hi, > > > My configuration : > > > Apache 2.0.46 /mod.jk2 > > > Tomcat 4.1.27 > > > Jahia 4.04 > > > Linux redhat enterprise 3.0 > > > RAM : 1 Go > > > Xeon Bi-processor > > > Oracle 8i on an other server > > > > > > > > > When all the JSP pages of the site are not compiled, if > > > somebody click several times on every links, multiple sessions are > > > created on Tomcat and Tomcat freeze. > > > > > > I tune apache with for keeping the sessions active. For > > > tomcat, it seems that the sessions opened on Tomcat don't expire. > > > > > >Do you have a solution ? > > > > > > > > >Franck > > > >-------=[ pvollenweider at jahia dot com ]=--------- > >Jahia : A collaborative source CMS and Portal Server www.jahia.org > >Community and product web site www.jahia.com Commercial services > >company > >-------=[ pvollenweider at jahia dot com ]=--------- >Jahia : A collaborative source CMS and Portal Server www.jahia.org >Community and product web site www.jahia.com Commercial services >company -------=[ pvollenweider at jahia dot com ]=--------- Jahia : A collaborative source CMS and Portal Server www.jahia.org Community and product web site www.jahia.com Commercial services company
