| Anonymous | Login | Signup for a new account | 10-24-2025 13:56 PDT |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0005697 | [Resin] | minor | always | 03-21-14 13:31 | 09-08-14 16:48 | ||||
| Reporter | cowan | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | 4.0.38 | ||||||
| Summary | 0005697: Thread leak on Windows with OpenSSL | ||||||||
| Description |
Customer reports thread leak on Windows with OpenSSL. Connections not closed by client and timeout on OpenSSL are left in a RUNNABLE state: "http--443-27$15864952" daemon prio=6 tid=0x3b53ac00 nid=0x80c runnable [0x3da0f000..0x3da0fd18] java.lang.Thread.State: RUNNABLE at com.caucho.vfs.JniSocketImpl.readNative(Native Method) at com.caucho.vfs.JniSocketImpl.read(JniSocketImpl.java:279) at com.caucho.vfs.JniStream.readTimeout(JniStream.java:87) at com.caucho.vfs.ReadStream.fillWithTimeout(ReadStream.java:985) at com.caucho.server.port.TcpConnection.waitForKeepalive(TcpConnection.java:208) at com.caucho.server.port.TcpConnection.run(TcpConnection.java:695) at com.caucho.util.ThreadPool$Item.runTasks(ThreadPool.java:743) at com.caucho.util.ThreadPool$Item.run(ThreadPool.java:662) at java.lang.Thread.run(Thread.java:619) |
||||||||
| Additional Information |
On unix systems, the socket itself has a timeout (setsockopt with SO_RCVTIMEO), which OpenSSL can work with. On windows, the SO_RCVTIMEO doesn't work (or at least didn't when our code was written.) So we can't do the same timeouts. |
||||||||
| Attached Files | |||||||||
|
|
|||||||||
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 26 unique queries executed. |