monitor failed error

Post any question you may have in regards to GoAnywhere Director and let our talented support staff and other users assist you.
2 posts Page 1 of 1

joeyam67

Posts: 1
Joined: Wed Sep 10, 2014 9:40 am

Post by joeyam67 » Wed Sep 10, 2014 12:38 pm
anyone ever seen this error?

09/09/2014 18:50:35 ERROR [2100 - MonitorRuntime] Monitor 'ICLRET' failed to run. Transport3 timedout waiting for response to SmbComSessionSetupAndX[command=SMB_COM_SESSION_SETUP_ANDX,received=false,errorCode=0,flags=0x0018,flags2=0xC803,signSeq=0,tid=0,pid=5618,uid=0,mid=16076,wordCount=12,byteCount=115,andxCommand=0xFF,andxOffset=0,snd_buf_size=16644,maxMpxCount=10,VC_NUMBER=1,sessionKey=0,lmHash.length=0,ntHash.length=0,capabilities=-2147479468,accountName=null,primaryDomain=null,NATIVE_OS=Windows Server 2008 R2,NATIVE_LANMAN=jCIFS]
com.linoma.commons.file.FileSystemException: Transport3 timedout waiting for response to SmbComSessionSetupAndX[command=SMB_COM_SESSION_SETUP_ANDX,received=false,errorCode=0,flags=0x0018,flags2=0xC803,signSeq=0,tid=0,pid=5618,uid=0,mid=16076,wordCount=12,byteCount=115,andxCommand=0xFF,andxOffset=0,snd_buf_size=16644,maxMpxCount=10,VC_NUMBER=1,sessionKey=0,lmHash.length=0,ntHash.length=0,capabilities=-2147479468,accountName=null,primaryDomain=null,NATIVE_OS=Windows Server 2008 R2,NATIVE_LANMAN=jCIFS]
at com.linoma.dpa.util.SMBNetworkFile.exists(Unknown Source)
at com.linoma.dpa.monitors.runtime.FileMonitorUtilities.getCurrentImage(Unknown Source)
at com.linoma.dpa.monitors.runtime.FileMonitorWorker.processFileMonitor(Unknown Source)
at com.linoma.dpa.monitors.runtime.FileMonitorWorker.run(Unknown Source)
at com.linoma.dpa.util.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at com.linoma.dpa.util.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: jcifs.smb.SmbException: Transport3 timedout waiting for response to SmbComSessionSetupAndX[command=SMB_COM_SESSION_SETUP_ANDX,received=false,errorCode=0,flags=0x0018,flags2=0xC803,signSeq=0,tid=0,pid=5618,uid=0,mid=16076,wordCount=12,byteCount=115,andxCommand=0xFF,andxOffset=0,snd_buf_size=16644,maxMpxCount=10,VC_NUMBER=1,sessionKey=0,lmHash.length=0,ntHash.length=0,capabilities=-2147479468,accountName=null,primaryDomain=null,NATIVE_OS=Windows Server 2008 R2,NATIVE_LANMAN=jCIFS]
jcifs.util.transport.TransportException: Transport3 timedout waiting for response to SmbComSessionSetupAndX[command=SMB_COM_SESSION_SETUP_ANDX,received=false,errorCode=0,flags=0x0018,flags2=0xC803,signSeq=0,tid=0,pid=5618,uid=0,mid=16076,wordCount=12,byteCount=115,andxCommand=0xFF,andxOffset=0,snd_buf_size=16644,maxMpxCount=10,VC_NUMBER=1,sessionKey=0,lmHash.length=0,ntHash.length=0,capabilities=-2147479468,accountName=null,primaryDomain=null,NATIVE_OS=Windows Server 2008 R2,NATIVE_LANMAN=jCIFS]
at jcifs.util.transport.Transport.sendrecv(Transport.java:73)
at jcifs.smb.SmbTransport.send(SmbTransport.java:633)
at jcifs.smb.SmbSession.sessionSetup(SmbSession.java:395)
at jcifs.smb.SmbSession.send(SmbSession.java:224)
at jcifs.smb.SmbTree.treeConnect(SmbTree.java:176)
at jcifs.smb.SmbFile.doConnect(SmbFile.java:906)
at jcifs.smb.SmbFile.connect(SmbFile.java:949)
at jcifs.smb.SmbFile.connect0(SmbFile.java:875)
at jcifs.smb.SmbFile.queryPath(SmbFile.java:1328)
at jcifs.smb.SmbFile.exists(SmbFile.java:1410)
at com.linoma.dpa.util.SMBNetworkFile.exists(Unknown Source)
at com.linoma.dpa.monitors.runtime.FileMonitorUtilities.getCurrentImage(Unknown Source)
at com.linoma.dpa.monitors.runtime.FileMonitorWorker.processFileMonitor(Unknown Source)
at com.linoma.dpa.monitors.runtime.FileMonitorWorker.run(Unknown Source)
at com.linoma.dpa.util.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at com.linoma.dpa.util.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

at jcifs.smb.SmbTransport.send(SmbTransport.java:638)
at jcifs.smb.SmbSession.sessionSetup(SmbSession.java:395)
at jcifs.smb.SmbSession.send(SmbSession.java:224)
at jcifs.smb.SmbTree.treeConnect(SmbTree.java:176)
at jcifs.smb.SmbFile.doConnect(SmbFile.java:906)
at jcifs.smb.SmbFile.connect(SmbFile.java:949)
at jcifs.smb.SmbFile.connect0(SmbFile.java:875)
at jcifs.smb.SmbFile.queryPath(SmbFile.java:1328)
at jcifs.smb.SmbFile.exists(SmbFile.java:1410)

Support_Rick

Support Specialist
Posts: 592
Joined: Tue Jul 17, 2012 2:12 pm
Location: Phoenix, AZ

Post by Support_Rick » Wed Sep 10, 2014 5:17 pm
Joey ...

There are a couple suggestions and options available to you with SMB.

From the post you made, it looks like there was probably some network traffic that pushed the Monitor response past it's timeout value. Default for SMB is 30 seconds.

If multiple Monitors had the same issue during a particular period, then there was more than likely a splurge of activity that pushed the Monitors past their Timeout Response Time.

Take a look at the jcifs.properties file (located in the "<install dir>\config" folder) and look for the following properties.

jcifs.smb.client.responseTimeout = 120
jcifs.smb.client.soTimeout = 140

Set them to values like the example shown, and/or, tweak them to values that would benefit your business needs.

*Note* You will need to remove the '#' from the beginning to activate the properties as well as restart GoAnywhere Service.

The best solution would be to utilize a Domain Service account. That way you could utilize UNC Addressing in Windows (or a Mount in Linux) to access the remote server just as if it was a local drive/folder. It's cleaner and easier to administer.

Please let us know if this helps correct your issue.
Rick Elliott
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696
2 posts Page 1 of 1