Solve the problem that broken pipe, socket... often occurs in webloigc in Linux .... Connection reset error

 

From: http://www.linuxdiyf.com/viewarticle.php? Id = 86772

There may be JVM errors caused by the Linux thread mechanism, especially during the connection peak hours. Similar situations occur in tomcat in Linux.

The solution is to set _ java_sr_signum = 12 in the environment variable.

Below is a clipping from sun on working around und JVM crashes under high thread counts in the JVM 1.3 for Linux on Linux,
The following is a snippet of JVM crash caused by jvm1.3 on Sun Linux.
Use a larger signal number for hotspot thread suspension/resumption handler.
The hotspot (Hotspot) thread pause/resume processor requires a larger number of signals.
The signal number being used is specified by Environment Variable _ java_sr_signum.
This large number is specified using the Environment Variable _ java_sr_signum.
Setting it to a number larger than SIGSEGV (11) will solve the problem.
Set a number larger than SIGSEGV (11) to solve this problem.
A good number to use is 12, which is sigusr2.
Sigusr2 uses 12 as a good number.
Using Signal 16 to work around the problem might have potential problems.
Using Signal 16 to solve this problem may cause potential problems
So on tcsh, "setenv _ java_sr_signum 12" can solve the problem.
Therefore, "set env _ java_sr_signum 12" can be used to solve this problem.

The last time a comrade asked a Connection reset error occurred while connecting to the database. This may be because the connection was not released normally (not necessarily due to a program problem ), it is best to set the maximum value of invalid connection timeout during connection delay.