[jcifs] Starvation of threads while accessing files and directories with jcifs

Michael B Allen mba2000 at ioplex.com
Tue Apr 26 17:57:38 GMT 2005

There was a bug that was fixed in 1.1.8 that has this behavior. So either
you're not really running 1.1.8 or you have a bad domain controller. What
happends when you run examples/ListDC.java?

On Tue, 26 Apr 2005 16:55:49 +0200
"Marro, Donato" <marro at e-Spirit.de> wrote:

> Hello,
> i have some problems while accessing files and directories
> with jcifs in a multithreaded environment (running on Resin 2.1.13
> with jcifs 1.1.8).
> I've configured a maximum number of 200 possible threads.
> But after some hours of operating with the application on
> the file-system, more and more threads are blocked until there
> are no more free threads to allocate and so there is no more
> response from our webserver.
> An extract from a threaddump looks like the following:
> 170 threads in the state:
> "tcpConnection-80-xxx" daemon prio=5 tid=0x04f7baa8 nid=0x1420 waiting for
> monitor entry [ae3f000..ae3fd90]
>     at jcifs.smb.SmbTransport.getSmbSession(SmbTransport.java:220)
>     - waiting to lock <0x17596610> (a jcifs.smb.SmbTransport)
>     at jcifs.smb.SmbFile.connect(SmbFile.java:823)
>     at jcifs.smb.SmbFile.connect0(SmbFile.java:797)
>     at jcifs.smb.SmbFile.queryPath(SmbFile.java:1202)
>     at jcifs.smb.SmbFile.exists(SmbFile.java:1285)
>     ...

IRC - where men are men, women are men, and the boys are FBI agents.

More information about the jcifs mailing list