WebLogic Report broken Pipe problem resolution method __web

Symptoms:

Warning:error Sending End Packet
Java.net.SocketException:Broken Pipe

Information:

The cause of broken pipe is usually when the pipe read end is not read, and the end of the pipeline is written, the pipeline is interrupted. (Because the pipe is a one-way communication) SIGSEGV (Segment fault) means that the address to which the pointer corresponds is an invalid address and no physical memory pair should be addressed. The following is the signal interpretation of Unix: 11/sigsegv:unerlaubter Zugriff auf Hauptspeicher (Adressfehler). 12/siguser2:user-defined Signal 2 (POSIX). Change the _java_sr_signum to 12 is the signal to become user-defined, so that it does not report out just, can not solve the problem. Suggested approach:

1. Resources are not fully released and are used to null values (Java GC is not so perfect)

2. The database connection order is closed. (Rs,ps,conn)

3. Optimize the Java Virtual machine to join the appropriate memory parameters.

4. Do not get large pieces of text in the database (that is, a field is not too large)

5. JAVA does not recommend using string to get a large amount of information. (easy to cause memory leak, recommend using StringBuffer)

6. Page Repeat submission

7. As much as possible to move the method to Java, in the JSP all the methods are considered as global variables, the compilation of execution itself has many problems.

8. Try to use a newer, more stable version of the JDK, and the lower version of the JVM itself has many bugs, such as 1. 5 of garbage collection compared to 1. 2, 1. 3 must be very obvious progress.

9. Linux system itself is not so stable, some problems can not be avoided ~ ~:)