[jcifs] looping on disconnect

[Michael B Allen]

Hi Simon,

It's not clear from your description that doDisconnect is being called
incorrectly in a loop by JCIFS or if your code is simply calling
something 129 million times that is triggering JCIFS to try to connect
to servers that aren't listening. You stack trace shows the exception
is thrown out out of run() so that would actually suggest the later is
the case. I'm not ruling out a bug but I would need to see more
evidence to take further action.

Old JCIFS releases are in the "old" directory like:

  http://jcifs.samba.org/old/jcifs-<version>.zip

Mike

-- 
Michael B Allen
Java Active Directory Integration
http://www.ioplex.com/

On Wed, Apr 20, 2011 at 12:11 PM, Simon <simon-samba at weatherill.org> wrote:
> We're using jCIFS 1.3.13 and just encountered an endless loop that
> effectively took down our application servers. The following appeared in our
> logs more than 129 million times!
>
> 2011-04-14 18:24:07,766 ERROR [STDERR] (Transport3)
> java.net.SocketException: Socket is closed
> 2011-04-14 18:24:07,766 ERROR [STDERR] (Transport3)     at
> java.net.Socket.shutdownOutput(Socket.java:1407)
> 2011-04-14 18:24:07,766 ERROR [STDERR] (Transport3)     at
> jcifs.smb.SmbTransport.doDisconnect(SmbTransport.java:358)
> 2011-04-14 18:24:07,766 ERROR [STDERR] (Transport3)     at
> jcifs.util.transport.Transport.disconnect(Transport.java:210)
> 2011-04-14 18:24:07,766 ERROR [STDERR] (Transport3)     at
> jcifs.util.transport.Transport.loop(Transport.java:122)
> 2011-04-14 18:24:07,766 ERROR [STDERR] (Transport3)     at
> jcifs.util.transport.Transport.run(Transport.java:257)
> 2011-04-14 18:24:07,766 ERROR [STDERR] (Transport3)     at
> java.lang.Thread.run(Thread.java:662)
>
> Can I get the source for 1.3.13 somewhere? I have 1.3.8 and the latest
> (1.3.15), but can't find 1.3.13.
>
> My guess is that the exception is causing the connection to be left in an
> open state only to attempt another disconnect (which fails). Seeing the
> actual source may help finding out what is going on.
>
> Thanks,
> Simon
>