cancel
Showing results for 
Search instead for 
Did you mean: 

Can't stop Alfresco properly

simon
Champ in-the-making
Champ in-the-making
Hi,

We installed Alfresco 1.2.1 on a RHEL 4 with the Java JRE and JDK 1.5.0_06. Alfresco starts and runs properly, no problems there and when I stop Tomcat with "./alfresco.sh stop" the server goes down like it should.

Problem is that the Java process keeps running. I get this in my process list (even if I ran the stop command):

root      3176     1  0 May17 ?        00:09:14 /usr/java/jre1.5.0_06/bin/java -Xms128m -Xmx640m -server -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/opt/alfresco/tomcat/conf/logging.properties -Djava.endorsed.dirs=/opt/alfresco/tomcat/common/endorsed -classpath :/opt/alfresco/tomcat/bin/bootstrap.jar:/opt/alfresco/tomcat/bin/commons-logging-api.jar -Dcatalina.base=/opt/alfresco/tomcat -Dcatalina.home=/opt/alfresco/tomcat -Djava.io.tmpdir=/opt/alfresco/tomcat/temp org.apache.catalina.startup.Bootstrap start

If I try the stop command again I get the "server not running" message and if I run the start command a new process is created and Alfresco will start (this process also keeps running when I try to shut it down). We don't have this problem on a RHEL 3 server with Alfresco 1.2, any idea's?
4 REPLIES 4

steve
Champ in-the-making
Champ in-the-making
Hi,

This could be because one of the Tomcat threads has not shut down correctly, which causes the shutdown to stall before it can complete.

Steve

simon
Champ in-the-making
Champ in-the-making
Thanks Steve.

How should I go on from here? How my I find which thread is causing this and if I find it what can I do about it?

steve
Champ in-the-making
Champ in-the-making
Hi,

Can you look in your log files to see if you have the same log entry as contained in this bug?

http://www.alfresco.org/jira/browse/AR-501

If so, it is scheduled to be fixed in the Enterprise release of 1.3

Thanks,

Steve

simon
Champ in-the-making
Champ in-the-making
It's not the same issue as the bug you refer to but we upgraded to 1.3 in development and the issue is solved. Don't know why but it's gone now. Consider this topic closed.