-
Recently, broken pipe errors often occur in email servers written in Java. After inspection
It is possible that the threading mechanism of Linux will cause JVM errors, especially during peak connection periods. Similar problems occur with tomcat under Linux.
The solution is to set it in the environment variable: _JAVA_SR_SIGNUM = 12, which basically solves the problem.
Set in the WIN environment variable: _JAVA_SR_SIGNUM =12. If you use export _JAVA_SR_SIGNUM =12 under Linux, it can basically be solved.
explanation of sun:
--posted by: cooper
Below is a clipping from Sun on working around JVM crashes under high
thread counts in the JVM 1.3 for Linux
On Linux, use a larger signal number for hotspot thread
suspension/resumption handler. The signal number being used is
specified by environment variable _JAVA_SR_SIGNUM. Setting it to a
number larger than SIGSEGV (11) will solve the problem. A good number
to use is 12, which is SIGUSR2. Using signal 16 to work around the
problem might have potential problems. So on tcsh, "setenv
_JAVA_SR_SIGNUM 12" can solve the problem.
-