Mantis Bugtracker

Viewing Issue Advanced Details Jump to Notes ] View Simple ] 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 Platform
Status closed   OS
Projection none   OS Version
ETA none Fixed in Version 4.0.41 Product Version 4.0.38
  Product Build
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.JniStream.readTimeout(
        at com.caucho.vfs.ReadStream.fillWithTimeout(
        at com.caucho.server.port.TcpConnection.waitForKeepalive(
        at com.caucho.util.ThreadPool$Item.runTasks(
        at com.caucho.util.ThreadPool$

Steps To Reproduce
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

- Relationships

- Notes
03-21-14 13:32

Rep by P Goldberg

- Issue History
Date Modified Username Field Change
03-21-14 13:31 cowan New Issue
03-21-14 13:32 cowan Note Added: 0006419
09-08-14 16:48 ferg Assigned To  => ferg
09-08-14 16:48 ferg Status new => closed
09-08-14 16:48 ferg Resolution open => fixed
09-08-14 16:48 ferg Fixed in Version  => 4.0.41

Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed.
26 unique queries executed.
Powered by Mantis Bugtracker