Econify
asked on
tomcat shutdown problem on debian linux
hello experts
i have tomcat 5.0.16 installed on Debian linux machine
the problem is the tomcat does not shutdown normally
i have to use killall java command to stop it
the error i get is pasted below
debinac:/usr/local/tomcat/
[1] 5161
debinac:/usr/local/tomcat/
Using CATALINA_HOME: /usr/local/tomcat
Using CATALINA_TMPDIR: /usr/local/tomcat/temp
Using JAVA_HOME: /usr/local/jdk
Catalina.stop: java.net.ConnectException:
java.net.ConnectException:
at java.net.PlainSocketImpl.s
at java.net.PlainSocketImpl.d
at java.net.PlainSocketImpl.c
at java.net.PlainSocketImpl.c
at java.net.Socket.connect(So
at java.net.Socket.connect(So
at java.net.Socket.<init>(Soc
at java.net.Socket.<init>(Soc
at org.apache.catalina.startu
at sun.reflect.NativeMethodAc
at sun.reflect.NativeMethodAc
at sun.reflect.DelegatingMeth
at java.lang.reflect.Method.i
at org.apache.catalina.startu
at org.apache.catalina.startu
[1]+ Done . catalina.sh stop
debinac:/usr/local/tomcat/
pls help
i have tomcat 5.0.16 installed on Debian linux machine
the problem is the tomcat does not shutdown normally
i have to use killall java command to stop it
the error i get is pasted below
debinac:/usr/local/tomcat/
[1] 5161
debinac:/usr/local/tomcat/
Using CATALINA_HOME: /usr/local/tomcat
Using CATALINA_TMPDIR: /usr/local/tomcat/temp
Using JAVA_HOME: /usr/local/jdk
Catalina.stop: java.net.ConnectException:
java.net.ConnectException:
at java.net.PlainSocketImpl.s
at java.net.PlainSocketImpl.d
at java.net.PlainSocketImpl.c
at java.net.PlainSocketImpl.c
at java.net.Socket.connect(So
at java.net.Socket.connect(So
at java.net.Socket.<init>(Soc
at java.net.Socket.<init>(Soc
at org.apache.catalina.startu
at sun.reflect.NativeMethodAc
at sun.reflect.NativeMethodAc
at sun.reflect.DelegatingMeth
at java.lang.reflect.Method.i
at org.apache.catalina.startu
at org.apache.catalina.startu
[1]+ Done . catalina.sh stop
debinac:/usr/local/tomcat/
pls help
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
is there a way to check whether tomcat is running
>> ps aux|grep tomcat
and on which port
>> check the tomcat/conf directory in server.xml for
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->
<Connector port="8080"...>
>> ps aux|grep tomcat
and on which port
>> check the tomcat/conf directory in server.xml for
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->
<Connector port="8080"...>
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
is there any script called shutdown.sh? could you try that?
Also how do you start up your tomcat server? which script do you use?
Also how do you start up your tomcat server? which script do you use?
first check if the 8080 port is in use using netstat command for options & synatx please check man pages.
i think itmust be netstat -r i am not sure just check.
If it is in use kill that process and retry.
Thank You.
i think itmust be netstat -r i am not sure just check.
If it is in use kill that process and retry.
Thank You.
@actonwang
>> ps aux|grep tomcat
>>> it will not be named tomcat, it will be "java ..."
>>>> tomcat or java...both will work. Sure, java as search is better...
>> ps aux|grep tomcat
>>> it will not be named tomcat, it will be "java ..."
>>>> tomcat or java...both will work. Sure, java as search is better...
actually, i got your problem now:
go to <tomcat>\conf\server.xml:
look at first line of xml as:
<Server port="8055" shutdown="SHUTDOWN"> <--- 8055 or other is the port for shutdown
This port , 8055 or other is the one which Tomcat is using for shutdowning your server. Try to change this port to different value which is not taken by other processes. then try it.
Enjoy :)
Acton
go to <tomcat>\conf\server.xml:
look at first line of xml as:
<Server port="8055" shutdown="SHUTDOWN"> <--- 8055 or other is the port for shutdown
This port , 8055 or other is the one which Tomcat is using for shutdowning your server. Try to change this port to different value which is not taken by other processes. then try it.
Enjoy :)
Acton
@acton
my first post has what u just now said.
fargo said..
2) the shutdown port used for tomcat is used by some other process
my first post has what u just now said.
fargo said..
2) the shutdown port used for tomcat is used by some other process
>>2) the shutdown port used for tomcat is used by some other process
oops.
oops.
ASKER
hi acton
i made some progress on this
my observation is
i start tomcat using . catalina.sh run &
when i check for whether tomcat is running using ps -ef|grep tomcat i see 40-50 lines
or when i give the command ps -A i see 40-50 java processes started
my app is working fine now
now i do . catalina.sh stop
after this when i do ps -A i still see around 20 processes by name of java
or ps -ef|grep tomcat shows about 20 threads
but my web application stops working
thats fine and that is what is wanted
but what are all these java processes which start with tomcat startup and why dont
they stop on tomcat shutdown.
so to be safe and sure i use killall java always while starting java
pls tell me wheteher its normal behaviour of tomcat
i dont think 40 threads shud be starting
pls guide
i made some progress on this
my observation is
i start tomcat using . catalina.sh run &
when i check for whether tomcat is running using ps -ef|grep tomcat i see 40-50 lines
or when i give the command ps -A i see 40-50 java processes started
my app is working fine now
now i do . catalina.sh stop
after this when i do ps -A i still see around 20 processes by name of java
or ps -ef|grep tomcat shows about 20 threads
but my web application stops working
thats fine and that is what is wanted
but what are all these java processes which start with tomcat startup and why dont
they stop on tomcat shutdown.
so to be safe and sure i use killall java always while starting java
pls tell me wheteher its normal behaviour of tomcat
i dont think 40 threads shud be starting
pls guide
so you resolved the shutdown as fargo and I mentioned :)
20 or 40 different lines?
Could you post them if you don't mind?
20 or 40 different lines?
Could you post them if you don't mind?
ASKER
hi acton
yes there was no port number issue.
it was bcos the server was already shutdown
but why the 40 lines dont know
pls help i dont want to do killall java
below are the process lines
debinac:~# ps -ef|grep tomcat
root 1711 1710 0 01:21 ? 00:00:06 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1756 1711 0 01:21 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1757 1756 0 01:21 ? 00:00:01 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1758 1756 0 01:21 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1759 1756 0 01:21 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1760 1756 0 01:21 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1761 1756 0 01:21 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1762 1756 0 01:21 ? 00:00:01 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1763 1756 0 01:21 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1765 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1768 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1769 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1770 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1771 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1772 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1773 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1774 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1775 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1776 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1777 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1778 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1779 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1780 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1781 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1782 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1783 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1784 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1785 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1786 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1787 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1788 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1789 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1790 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1791 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1792 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1793 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1794 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1795 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1796 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1797 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1798 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1799 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 5085 4893 0 09:17 pts/6 00:00:00 grep tomcat
yes there was no port number issue.
it was bcos the server was already shutdown
but why the 40 lines dont know
pls help i dont want to do killall java
below are the process lines
debinac:~# ps -ef|grep tomcat
root 1711 1710 0 01:21 ? 00:00:06 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1756 1711 0 01:21 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1757 1756 0 01:21 ? 00:00:01 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1758 1756 0 01:21 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1759 1756 0 01:21 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1760 1756 0 01:21 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1761 1756 0 01:21 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1762 1756 0 01:21 ? 00:00:01 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1763 1756 0 01:21 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1765 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1768 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1769 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1770 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1771 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1772 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1773 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1774 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1775 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1776 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1777 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1778 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1779 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1780 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1781 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1782 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1783 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1784 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1785 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1786 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1787 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1788 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1789 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1790 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1791 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1792 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1793 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1794 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1795 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1796 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1797 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1798 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 1799 1756 0 01:22 ? 00:00:00 /usr/local/jdk/bin/java -Djava.endorsed.dirs=/usr/
root 5085 4893 0 09:17 pts/6 00:00:00 grep tomcat
Hi,Econify,
Those are spare threads from Tomcat. Look at server.xml, you will see as:
<Connector port="8080" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
.... />
You lower those attributes for thread and you should see less java processes.
Enjoy :)
Acton
Those are spare threads from Tomcat. Look at server.xml, you will see as:
<Connector port="8080" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
.... />
You lower those attributes for thread and you should see less java processes.
Enjoy :)
Acton
ASKER
hi acton i have 2 installation of tomcat one on ubuntu and another on debian
both have the same values as u have said
<Connector port="8080" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
.... />
but the ubuntu starts only 3 threads and debian starts 50 threads
>>>you lower those attributes for thread and you should see less java processes.
can u be a specific which attribute and to what value
i feel this not the root cause
both have the same values as u have said
<Connector port="8080" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
.... />
but the ubuntu starts only 3 threads and debian starts 50 threads
>>>you lower those attributes for thread and you should see less java processes.
can u be a specific which attribute and to what value
i feel this not the root cause
how about try:
<Connector port="8080" maxHttpHeaderSize="8192"
maxThreads="10" minSpareThreads="2" maxSpareThreads="5"
.... />
for the sake of test.
<Connector port="8080" maxHttpHeaderSize="8192"
maxThreads="10" minSpareThreads="2" maxSpareThreads="5"
.... />
for the sake of test.
ASKER
i acton my googling resulted in a good info about the issue
which finally says
i shud not bother about it
http://marc.theaimsgroup.com/?l=tomcat-user&m=104852893716114&w=2
pls have a look and share your view
actually as they say i am also not bothered for the no of threads tomcat is starting up
i was only bothered for the threads which were not stopping even after i shutdown the server
for which i used killall java
i was only making sure of a clean tomcat startup by using that
and at last but not the least thank you for holding on for so long on
this issue along with me
which finally says
i shud not bother about it
http://marc.theaimsgroup.com/?l=tomcat-user&m=104852893716114&w=2
pls have a look and share your view
actually as they say i am also not bothered for the no of threads tomcat is starting up
i was only bothered for the threads which were not stopping even after i shutdown the server
for which i used killall java
i was only making sure of a clean tomcat startup by using that
and at last but not the least thank you for holding on for so long on
this issue along with me
Econify,
What they said is just what I said.
Did you try the settings I recommended and see if less threads are listed?
If you use startup.sh or shutdown.sh scripts, everything should be fine.
Acton
What they said is just what I said.
Did you try the settings I recommended and see if less threads are listed?
If you use startup.sh or shutdown.sh scripts, everything should be fine.
Acton
ASKER
is there a way to check whether tomcat is running and on which port
on a debian linux machine