DO NOT REPLY [Bug 47670] Unlock accept issue

2010-01-11 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=47670 Mark Thomas changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|

DO NOT REPLY [Bug 47670] Unlock accept issue

2009-12-13 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=47670 Mark Thomas changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #1 from Mark Th

DO NOT REPLY [Bug 47670] New: Unlock accept issue

2009-08-10 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=47670 Summary: Unlock accept issue Product: Tomcat 6 Version: 6.0.14 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component

Re: Unlock accept issue

2009-08-10 Thread Filip Hanik - Dev Lists
in either case, the "unlocker" thread should have set connect timeout and read timeout in NIO, we do s.connect(saddr,getSocketProperties().getUnlockTimeout()); Marcin, the best way for us to track this is for you to open a bugzilla issue. http://issues.apache.org/bugzilla On 08/10/2009 07:

Unlock accept issue

2009-08-10 Thread BALCER, Marcin (Marcin)
Hi I am having problem when shutting down tomcat. Tomcat: 6.0.14. OS: Linux 2.6.16.21-0.8-smp #1 SMP Mon Jul 3 18:25:39 UTC 2006 x86_64 Java: "1.5.0_14" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_14-b03, mixed mode) The s