Hello all wise guys,
i have a question about the tomcat environment,
when i start the Jarkarta-Tomcat3.2.2b2 and look with ps aux on the
system,
(with Tomcat3.2.1final it will be 33 Threads ;-)) )
it show :
......
.....
root 7287 0.0 18.2 214124 17876 tty1 S 14:26 0:03
/usr/local/jdk1.3/bin/i386/native_threads/java
-Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol
-Dtomcat.home=/usr/local/jakarta-tomcat-3.2.2b2/bin/..
org.apache.tomcat.startup.Tomcat
root 7327 0.0 18.2 214124 17876 tty1 S 14:26 0:06
/usr/local/jdk1.3/bin/i386/native_threads/java
-Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol
-Dtomcat.home=/usr/local/jakarta-tomcat-3.2.2b2/bin/..
org.apache.tomcat.startup.Tomcat
..........
CUT
.........
root 7328 0.0 18.2 214124 17876 tty1 S 14:26 0:00
/usr/local/jdk1.3/bin/i386/native_threads/java
-Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol
-Dtomcat.home=/usr/local/jakarta-tomcat-3.2.2b2/bin/..
org.apache.tomcat.startup.Tomcat
there are 34 Threads !!! is that normal ? (the -Djava....... is only a
parameter)
And the 18.2 is the %MEN variable. The sum of all cpu use is about 8
percent , that's ok.
The %MEN will grow Up when I work with the servlets.
After 4 Day's the server was very slow, and finnaly it hangs Up !!
The System is SuseLinux 7.1 (and no Microsoft, then a had understand why
it hangs up ; >)
Have anyone the same experience ?
Or some work around ??
Please help,
thank you for inconvenience,
Michael
