刷新jsp文件时的线程锁定

Question

在负载过重的情况下，我看到许多线程在GZipping和解压缩JSP文件时被锁定。线程转储如下所示。似乎来自"header.jsp“，它的大小是14 be。

http-0.0.0.0-8080-304" daemon prio=3 tid=0x0000000008bcc000 nid=0x302 runnable [0xfffffd7de7bc2000]
   java.lang.Thread.State: RUNNABLE
    at java.util.zip.Deflater.deflateBytes(Native Method)
    at java.util.zip.Deflater.deflate(Deflater.java:306)
    - locked <0xfffffd7e589078e8> (a java.util.zip.ZStreamRef)
    at java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:159)
    at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:118)
    at java.util.zip.GZIPOutputStream.write(GZIPOutputStream.java:72)
    - locked <0xfffffd7e58524d28> (a java.util.zip.GZIPOutputStream)
    at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:91)
    at com.pinksheets.common.web.cache.ServletOutputStreamWrapper.write(ServletOutputStreamWrapper.java:24)
    at java.io.OutputStream.write(OutputStream.java:99)
    at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202)
    at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:263)
    at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:106)
    - locked <0xfffffd7e58524d48> (a java.io.OutputStreamWriter)
    at java.io.OutputStreamWriter.write(OutputStreamWriter.java:190)
    at java.io.BufferedWriter.write(BufferedWriter.java:170)
    - locked <0xfffffd7e58524d48> (a java.io.OutputStreamWriter)
    at java.io.PrintWriter.write(PrintWriter.java:382)
    - locked <0xfffffd7e5824bd80> (a java.io.BufferedWriter)
    at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:119)
    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:326)
    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:342)
    at org.apache.jsp.include.header_jsp._jspService(header_jsp.java:2032)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

Answer 1

一些必然的联系：

• http://www.java.net/forum/topic/glassfish/glassfish/glassfish-301-gzip-problem-threads-apparently-spinning-100-cpu-use
• java.util.zip - ZipInputStream v.s. ZipFile

我们正在经历类似的问题--我们目前最好的理论是，Java代码(或者它使用底层zlib支持库的方式)会导致线程以这种方式进入空间。到目前为止，我们能够阻止这种情况的唯一方法是不使用GZip响应--但是我们宁愿支付100%的CPU成本(因为其他线程仍然响应能力很强)，而不是GZIP响应。你已经几个月没发邮件了，你还有其他信息要分享吗？