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

Donato Marro marro at e-spirit.de
Mon May 2 16:26:46 GMT 2005

Michael B Allen <mba2000 <at> ioplex.com> writes:

> The question is - is the first thread legitimately waiting for a response
> that simply will never come or is this some kind of concurrency error like
> the one we fixed in 1.1.8? It's not easy to tell. My understanding is that
> if everything is properly synchronized the negotiation should timeout
> after a short time.

To ensure a timeout of the negotiation wouldn't it be expedient to call the 
wait()-method (SmbTransport.java, line 931) with some timeout parameter?

> Another thing you could try is to reduce the number of threads you're
> running. It's horribly inefficient to run hundreds of threads and the
> stress of so many different threads calling into the library at once could
> be a prerequisite for triggering a concurrency error.

It seems as it is indeed a concurrency error because running the application in 
a single-threaded modus works fine.


More information about the jcifs mailing list