[jcifs] CLOSE_WAIT-Connections left

[Michael B Allen]

On Mon, 19 Jun 2006 22:02:27 +0200
Martin <martin at heddergott.org> wrote:

> Hello,
> 
> this is a stacktrace when the socket is left in close_wait-state.

Oo, yeah. This isn't supposed to happen. So that's a bug.

> Perhaps this can help to find a solution (call socket.close() when the
> exception is thrown ?).

Actually you might consider putting it right after SmbTransport.java:189
just before it throws that exception.

> jcifs.smb.SmbException: EOF during NetBIOS session request
>         at jcifs.smb.SmbTransport.ssn139(SmbTransport.java:190)
>         at jcifs.smb.SmbTransport.negotiate(SmbTransport.java:236)
>         at jcifs.smb.SmbTransport.doConnect(SmbTransport.java:301)
>         at jcifs.util.transport.Transport.run(Transport.java:223)
>         at java.lang.Thread.run(Unknown Source)
> 
>         at jcifs.util.transport.Transport.run(Transport.java:239)
>         at java.lang.Thread.run(Unknown Source)
> 
>         at jcifs.smb.SmbTransport.connect(SmbTransport.java:288)
>         at jcifs.smb.SmbTree.treeConnect(SmbTree.java:132)
>         at jcifs.smb.SmbFile.connect(SmbFile.java:791)
>         at jcifs.smb.SmbFile.connect0(SmbFile.java:761)
>         at jcifs.smb.SmbFile.send(SmbFile.java:660)
>         at jcifs.smb.SmbFile.doNetEnum(SmbFile.java:1636)
>         at jcifs.smb.SmbFile.listFiles(SmbFile.java:1585)
>         at jcifs.smb.SmbFile.listFiles(SmbFile.java:1551)
>         at CrawlerThread.run(CrawlerThread.java:34)
> 
> If it works as designed i would take the source and insert a close() for
> me - are there any side effects to expect ?

No, I don't think so.

Mike

-- 
Michael B Allen
PHP Extension for SSO w/ Windows Group Authorization
http://www.ioplex.com/