atom feed26 messages in org.freebsd.freebsd-javaclose() of active socket does not wor...
FromSent OnAttachments
Arne H. JuulDec 11, 2006 6:47 am 
Arne H. JuulDec 11, 2006 7:06 am 
Achilleas MantziosDec 11, 2006 7:25 am 
Achilleas MantziosDec 11, 2006 7:48 am 
Kostik BelousovDec 11, 2006 9:11 am 
Arne H. JuulDec 11, 2006 2:40 pm 
David XuDec 11, 2006 4:15 pm 
Arne H. JuulDec 11, 2006 4:25 pm 
Arne H. JuulDec 11, 2006 4:50 pm 
David XuDec 11, 2006 5:04 pm 
Daniel EischenDec 11, 2006 5:08 pm 
Bruce EvansDec 11, 2006 9:54 pm 
Poul-Henning KampDec 11, 2006 10:43 pm 
Daniel EischenDec 12, 2006 5:21 am 
Kostik BelousovDec 12, 2006 5:59 am 
Daniel EischenDec 12, 2006 6:24 am 
Daniel EischenDec 12, 2006 6:35 am 
Kostik BelousovDec 12, 2006 6:38 am 
Greg LewisDec 12, 2006 11:31 am 
Daniel EischenDec 12, 2006 12:49 pm 
David XuDec 12, 2006 3:29 pm 
Arne H. JuulDec 12, 2006 5:59 pm 
Bruce EvansDec 12, 2006 7:28 pm 
Julian ElischerDec 12, 2006 11:12 pm 
Bruce EvansDec 13, 2006 3:28 am 
David XuDec 13, 2006 4:10 am 
Subject:close() of active socket does not work on FreeBSD 6
From:Daniel Eischen (deis@freebsd.org)
Date:Dec 12, 2006 6:24:21 am
List:org.freebsd.freebsd-java

On Tue, 12 Dec 2006, Kostik Belousov wrote:

On Tue, Dec 12, 2006 at 08:18:32AM -0500, Daniel Eischen wrote:

It's also couldn't be entirely solved by fixing it in the threads library. You could still have a non-threaded application that waits on a read operation, but receives a signal and closes the socket in the signal handler.

This is not the problem. The read (as syscall being executed) is aborted when signal is delivered. Original poster considered situation where read() is active (in particular, f_count of struct file is incremented by fget, that caused the reported behaviour).

Even when SA_RESTART is set?