[jcifs] SmbException in jcifs-1.2.7

Michael B Allen mba2000 at ioplex.com
Wed Jan 4 18:24:40 GMT 2006

On Wed, 4 Jan 2006 13:47:26 +0000 (UTC)
Rainer Buss <rainer.buss at rbconsult.de> wrote:

> Hi,
> I am a new user of jcifs.
> We are using jcifs-1.2.7 in an application that scans an remote directory
> in 20 sec interval for new files. We often get exceptions like these shown
> below and are not shure, if these messages indicate severe errors corrupting
> further connections or errors as described in release text for jcifs-1.2.4:
> "It was discovered that the new transport (as of 1.2.x) could not cleanly 
> recover from temporary server failure (e.g. a restart). This has been fixed. 
> Methods will still throw Exceptions but the moment the server comes back online 
> the client should gracefully recover."

So is the machine offline when this happends? And jCIFS never recovers?

> The errorCode is always 0 or 'The operation completed successfully' ?!

It is VERY strange that the debug output would print 0 or 'The operation
completed successfully'. 1.2.7 prints 0 for errorCode ALWAYS. Could it be
that you have some old jar files hidding in your classpath somewhere? Try
moving the 1.2.7 jar file out of the CLASSPATH temporarily and see if
the app still runs.

> Is it possible to avoid these errors by setting properties as
> jcifs.netbios.retryCount ?

No, that property if for name service lookups. See the overview page of
the API documentation for meaningful properties.


> Error transferring File : jcifs.smb.SmbException: 
> jcifs.util.transport.TransportException: Transport1[duss0485/] 
> timedout waiting for response to Trans2QueryPathInformation
> [command=SMB_COM_TRANSACTION2,received=false,errorCode=0,flags=0x0018,flags2=0xC

More information about the jcifs mailing list