Hello Bob, as it could be linked to an installation or environment problem, I'd say its a good place to post here.
The ServerOverloadedException in Jahia can have several reasons: 1.) After server startup the first request has to be processed alone. We are ensuring that by holding back and queueing the next requests, but if the first request takes too long (> pageGenerationWaitTimeOnStartup), the log will display a ServerOverloadedException, while the clients will get a message like "Page is being loaded..." and will automatically retrigger the request after the configured suggestedRetryTimeAfterTimeoutOnStartup. We suggest that you allow access to the server only after the first request has finished. 2.) Most probably you refer to the ServerOverloadedException, which does not come on server startup. It could have several reasons and you could try to determine it with creating and analyzing JVM thread dumps (kill -QUIT <pid>). We already experienced the following reasons: * If you see many JahiaSearchBaseService.checkFieldsScoreBoost references in the thread dump, then your exception is caused by a bug in the 5.0.3 release. It is fixed in the forthcoming 5.0.4, but a workaround would be to either change a configuration parameter in WEB-INF\etc\spring\applicationcontext-basejahiaconfig.xml to 2 hours: <prop key="scoreBoostRefreshDelayTime">2h</prop> Customers with a service contract may also get a patch, which fixes the problem in 5.0.3. * From the thread dump you may also see that you are perhaps running out of database connections. As you have configured 200 concurrent processing requests, you should ensure that the DB connection pool is large enough and that also your DB server is configured to handle that many concurrent requests. Many databases have a default setting of just maximum 100 concurrent connections. * Regarding the right value for maxParallelProcessings it depends on the hardware environment and the complexity of your templates. So you should identify the ideal value by stress testing your application. It could also be that the solution is not to raise but to lower the maxParallelProcessings, as a too high value may provoke the problem that the application or the DB server is running out of resources and e.g. doing too much garbage collection. You could switch on garbage collection logging (-verbose:gc) to see, whether garbage collection is blocking and causing the slow response of your server. * Perhaps you will have to optimize your templates, as e.g. wrong API usage may cause unnecessary or too heavy DB calls. This could be identified by profiling the rendering of the most visited pages. * Also read and try to apply suggestions from our Performance Tuning Guide available on our homepage. * For 5.0.3 you should also check, that the servername configured for your site (in the Administration center) matches the used domain name, as otherwise this may cause some unnecessary DB calls. So these are some reasons from the top of my head and from the experiences I made. The 5.0.4 release should be out this month, I am recommending you to upgrade if you can, as we fixed some bugs and made many improvements using less memory. Regards, Benjamin On 06.06.2008 15:47 Stauffer, Robert G wrote: > Hi all. A newbie here. If I'm posting to the wrong place, please point > me in the right direction. Thanks. > > Our environment: > Jahia 5.0.3 > WebSphere App Server (WAS) 6.0.2.23 > Red Hat Linux ES 4 > 32-bit > 4 GB memory > jvm 1538 MB > > jahia.properties: > maxParallelProcessings = 200 > pageGenerationWaitTime = 60000 > suggestedRetryTimeAfterTimeout = 60 > pageGenerationWaitTimeOnStartup = 10000 > suggestedRetryTimeAfterTimeoutOnStartup = 15 > > WAS Web Container thread pool max threads is set to 400. > > We're getting lots of 503 server overloaded errors at times. I'd like > to be able to increase the jvm above 1538 MB, but we're restricted to > that at the moment because of other apps running on the machine. We're > preparing a 12 GB, 64-bit server but it'll be a week or two until it's > ready. > > In the meantime, how do I reduce the 503 server overloaded problems? Is > it just a matter of increasing maxParallelProcessings? > > Here's an example of an entry in the app server logs. I had set the > logging level of root in log4j.xml to "info" instead of "error" for a > time to get this info. > [6/5/08 21:24:37:786 EDT] 0000089b SystemOut O 2008-06-05 > 21:24:37,786: WARN [org.jahia.bin.JahiaAction] - Server is overloaded. > Request : /jahia/Jahia queryString=null was not processed > [6/5/08 21:24:37:787 EDT] 0000089b SystemOut O 2008-06-05 > 21:24:37,786: ERROR [org.jahia.bin.JahiaErrorDisplay] - ERROR : 503 - > server overloaded, 503 - Server Overloaded > org.jahia.exceptions.JahiaServerOverloadedException: User message=503 - > server overloaded, System message=503 - Server Overloaded > at > org.jahia.operations.valves.EngineValve.avoidParallelProcessingOfSamePag > e(EngineValve.java:255) > at > org.jahia.operations.valves.EngineValve.processEngineRequest(EngineValve > .java(Compiled Code)) > at > org.jahia.operations.valves.EngineValve.invoke(EngineValve.java(Compiled > Code)) > at > org.jahia.pipelines.impl.GenericPipeline.invokeNext(GenericPipeline.java > (Inlined Compiled Code)) > at > org.jahia.operations.valves.J2ProcessActionValve.invoke(J2ProcessActionV > alve.java(Compiled Code)) > at > org.jahia.pipelines.impl.GenericPipeline.invokeNext(GenericPipeline.java > (Inlined Compiled Code)) > ... > > > Bob Stauffer > DBA > D&E Communications > Ephrata, PA > [EMAIL PROTECTED] > 717-738-8737 > > **DISCLAIMER > This e-mail message and any files transmitted with it are intended for the > use of the individual or entity to which they are addressed and may contain > information that is privileged, proprietary and confidential. If you are not > the intended recipient, you may not use, copy or disclose to anyone the > message or any information contained in the message. If you have received > this communication in error, please notify the sender and delete this e-mail > message. The contents do not represent the opinion of D&E except to the > extent that it relates to their official business. > _______________________________________________ > install_list mailing list > install_list@jahia.org > http://lists.jahia.org/cgi-bin/mailman/listinfo/install_list > _______________________________________________ install_list mailing list install_list@jahia.org http://lists.jahia.org/cgi-bin/mailman/listinfo/install_list
