Re: Tomcat stops responding

Stéphane Croisier <[email protected]> Wed, 21 Feb 2007 09:18:45 +0100
Newsgroups gmane.comp.cms.jahia.install
Message-ID <[email protected]>
At 00:18 21.02.2007, you wrote:

>I found the output it's in the catalina.out. How 
>do I make sense of the output?
>
>I see several entries like the following:
>
>-- Blocked trying to get lock: 
>org/jahia/services/fields/JahiaFieldBaseService@0x108e2db8[fat lock]
>
>Where can I forward the zip file of the thread dump contents?


Do you have some internet web site/FTP server to 
upload it? Then you can just make a link on this 
url in this mailing list. If this is less than 
10Mb (if I rememember correctly) you can also 
open a JIRA (www.jahia.net/jira).

Stéphane


>Daryl
>
>Daryl Gerlach wrote:
>>Benjamin,
>>
>>I tried the Kill -QUIT <pid> But it didn't 
>>work, process kept running with no output. I'm running Red Hat ES4. Confused
>>
>>Daryl
>>
>>Benjamin Papez wrote:
>>>Hello Daryl,
>>>
>>>we had similar problems, because Jahia 4.1 was 
>>>running out of database connections. There 
>>>were also some deadlock issues. Most of these 
>>>problems will be fixed with the forthcoming 
>>>Jahia 4.2 release, which will be out very 
>>>soon. Meanwhile you could try to reserve 
>>>enough DB connections. What you could also do 
>>>is to create a thread dump ( kill -QUIT 
>>>process_id) of the tomcat java process, when 
>>>such a situation occurs. This will help 
>>>determining, what the threads are doing and 
>>>why they are not finishing their work.
>>>
>>>Greetings,
>>>Benjamin
>>>
>>>2007/2/6, Daryl Gerlach 
>>><<mailto:[email protected]>[email protected]>: 
>>>
>>>We are having issues running Jahia 4.1.1 in production. We recently
>>>upgraded our servers to Red Hat ES 4 and added apache 2.0.52 with mod_jk
>>>1.2.20 to front  end the whole thing. Under load the server stops
>>>responding to requests. Here are the settings for workers.properties,
>>>server.xml, and httpd.conf
>>>
>>>worker.properties
>>>============
>>>worker.list=consumer,builder
>>>
>>># Set properties for consumer (ajp13)
>>>worker.consumer.type=ajp13
>>>worker.consumer.host=localhost
>>>worker.consumer.port=8019
>>>
>>>worker.builder.type=ajp13
>>>worker.builder.host=localhost
>>>worker.builder.port=8009
>>>
>>>
>>>httpd.conf
>>>=======
>>><IfModule mod_jk.c>
>>>    JkWorkersFile conf/workers.properties
>>>    JkShmFile    logs/mod_jk.shm
>>>    JkLogFile    logs/mod_jk.log
>>>    JkLogLevel   info
>>>    JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
>>></IfModule>
>>>
>>><VirtualHost *:80>
>>>...
>>>    <IfModule mod_jk.c>
>>>        # Send everything for context /examples to worker named worker1
>>>(ajp13)
>>>        JkMount  /jahia/* builder
>>>        JkMount  /pdfgenerator/* builder
>>>    </IfModule>
>>></VirtualHost>
>>>
>>>
>>>server.xml
>>>=======
>>><Connector className="org.apache.ajp.tomcat4.Ajp13Connector "
>>>               port="8009" minProcessors="5" maxProcessors="75"
>>>               acceptCount="10" debug="0"/>
>>>
>>>What settings are other people using in production?
>>>
>>
>>
>>--
>>Daryl Gerlach
>>Consultant
>>Collective Intelligence, Inc.
>>Phone: 717-545-9234
>>Fax: 717-545-9232
>>Cell: 717-649-3499
>
>
>--
>Daryl Gerlach
>Consultant
>Collective Intelligence, Inc.
>Phone: 717-545-9234
>Fax: 717-545-9232
>Cell: 717-649-3499
>
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.412 / Virus Database: 268.18.3/693 - Release Date: 19.02.2007



No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.412 / Virus Database: 268.18.3/693 - Release Date: 19.02.2007