[jcifs] Transport1 timedout waiting for response to SmbComSessionSetupAndX

Dave Haworth dhaworth at widen.com
Fri May 11 17:31:51 GMT 2007

The code is running in a Tomcat 5.5.17 container on a server in our DMZ.
It's creating the JShellLink shortcuts locally on that box and copying
them to a separate file server behind our firewall on our private
network. The job first checks if the folder it is copying the shortcut
to exists and if not it creates it and then copies the shortcut over.
About 5% of the shortcuts don't get copied over due to the error below. 

I realize this sounds a little unorthodox, but I can't create the
JShellLink shortcut as an SmbFile so I'm forced to create it as a
regular java.io.File locally and copy it over as an SmbFile. I am using
jcifs 1.2.13.

Thanks for following up.

Dave Haworth

-----Original Message-----
From: Michael B Allen [mailto:mba2000 at ioplex.com] 
Sent: Friday, May 11, 2007 11:01 AM
To: Dave Haworth
Cc: jcifs at lists.samba.org
Subject: Re: [jcifs] Transport1 timedout waiting for response to

On Fri, 4 May 2007 10:04:16 -0500
"Dave Haworth" <dhaworth at widen.com> wrote:

> if the folder I'm moving the shortcut to exists and creating it if it
> doesn't) thousands of times during the course of the job and a couple
> hundred of the shortcuts never make it out to the server and throw the
> following error:
> jcifs.smb.SmbException: 
> jcifs.util.transport.TransportException: Transport1 timedout waiting
> response to
> at jcifs.util.transport.Transport.sendrecv(Transport.java:76)
> at jcifs.smb.SmbTransport.send(SmbTransport.java:606)
> at jcifs.smb.SmbSession.sessionSetup(SmbSession.java:277)
> at jcifs.smb.SmbSession.send(SmbSession.java:233)
> at jcifs.smb.SmbTree.treeConnect(SmbTree.java:154)
> at jcifs.smb.SmbFile.connect(SmbFile.java:798)
> at jcifs.smb.SmbFile.connect0(SmbFile.java:768)
> at jcifs.smb.SmbFile.queryPath(SmbFile.java:1195)
> at jcifs.smb.SmbFile.exists(SmbFile.java:1277)
> It appears that it's running out of ports to connect to and it seems
> error always happens while checking to see if the destination folder
> exists. I've increased both the responseTimeout and soTimeout
> in the configuration to twice their default values using
> Config.setProperty, but the results seems the same. I'm pretty new to
> jcifs, so there's a chance I'm missing something obvious. If anyone
> any thoughts on what I might try it would be appreciated. Thanks!

Are you doing this on different servers? JCIFS should reuse
sessions. Sounds like the overall modus operandi is off somehow.


Michael B Allen
PHP Active Directory Kerberos SSO

More information about the jcifs mailing list