[jcifs] SmbTransport thread accumulation issues

Michael B Allen ioplex at gmail.com
Tue Oct 18 13:45:19 MDT 2011


On Tue, Oct 18, 2011 at 2:46 PM, Michael B Allen <ioplex at gmail.com> wrote:
> But to Colin directly, note that in 1.3.16, the
> jcifs.smb.client.soTimeout value is passed to the Socket constructor
> to control the connect timeout.

Note: This just changed in the 1.3.17 release. There is a new property
now called jcifs.smb.client.connTimeout which controls the timeout
passed to Socket.connect(). The jcifs.smb.client.soTimeout goes back
to just controlling how long the client will wait for a read() just as
it always did.

Text below edited to compensate.

> So by just using a relatively small
> [jcifs.smb.client.connTimeout] value you could speed things up considerably. And you could
> make one pass over the list of hosts with a low [connTimeout] and if they
> respond, process and remove them from the list and then double the
> [connTimeout] and go over the list again and remove and repeat so that you
> try successively longer [connTimeouts].

Mike

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


More information about the jCIFS mailing list