| Re: [jetty-dev] jetty-dev Digest, Vol 69, Issue 1 |
Hi Pushkar, Your asking to discuss a bug in a version of Jetty that is two and a half years old, Since Jetty 8.1.3 was released, many many bugs have been fixed. The last version of Jetty 8.1.x is actually Jetty 8.1.16. It might be worth considering if you might be encountering a bug that was fixed several years ago, consider upgrading to at least 8.1.16. Best regards, Jacob > Date: Mon, 10 Nov 2014 14:32:13 +0530 > From: Pushkar N Kulkarni <pushkar.nk@xxxxxxxxxx> > To: jetty-dev@xxxxxxxxxxx > Subject: [jetty-dev] Jetty unresponsive when HTTPS enabled > Message-ID: > <OF36541319.B845D59D-ON65257D8C.0030281B-65257D8C.0031EC6C@xxxxxxxxxx> > Content-Type: text/plain; charset="utf-8" > > A customer of ours sees Jetty going unresponsive when they enable > HTTPS-based connections, on Linux. The jetty version is 8.1.3.v20120416. > > We took thread dumps during this period and found that there are 271 > QueuedThreadPool threads. Out of those, around 230 are stuck running this > call stack: >
Attachment:
smime.p7s
Description: S/MIME cryptographic signature