SmbException in jcifs-1.2.7

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

SmbException in jcifs-1.2.7

Rainer Buss
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."

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

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

Any idea ?

thanks

Rainer Buss

Error transferring File : jcifs.smb.SmbException:
jcifs.util.transport.TransportException: Transport1[duss0485/15.1.15.151:445]
timedout waiting for response to Trans2QueryPathInformation
[command=SMB_COM_TRANSACTION2,received=false,errorCode=0,flags=0x0018,flags2=0xC
003,signSeq=0,tid=64,pid=31319,uid=2048,mid=18102,wordCount=15,byteCount=145,tot
alParameterCount=144,totalDataCount=0,maxParameterCount=2,maxDataCount=40,maxSet
upCount=0,flags=0x00,timeout=0,parameterCount=144,parameterOffset=66,parameterDi
splacement=0,dataCount=0,dataOffset=210,dataDisplacement=0,setupCount=1,pad=1,pa
d1=0,informationLevel=0x101,filename=\RMSC_Equities_Transfer\Applications\MPVaR_
ATLAS_Panmure\Input\MPVaR]
        at jcifs.smb.SmbTransport.send(SmbTransport.java:574)
        at jcifs.smb.SmbSession.send(SmbSession.java:229)
        at jcifs.smb.SmbTree.send(SmbTree.java:102)
        at jcifs.smb.SmbFile.send(SmbFile.java:688)
        at jcifs.smb.SmbFile.queryPath(SmbFile.java:1196)
        at jcifs.smb.SmbFile.exists(SmbFile.java:1250)
        at wlb.mpvar.fileimport.transfer.FrontOfficeFileTransfer.run(Unknown
Source)
        at wlb.mpvar.fileimport.demons.BasicDemon.run(Unknown Source)
       
       
Error transferring File : jcifs.smb.SmbException:
jcifs.util.transport.TransportException: Transport1[duss0485/15.1.15.151:445]
timedout waiting for response to Trans2QueryPathInformation
[command=SMB_COM_TRANSACTION2,received=false,errorCode=The operation completed
successfully.,flags=0x0018,flags2=0xC003,signSeq=0,tid=64,pid=50258,uid=2048,mid
=17913,wordCount=15,byteCount=133,totalParameterCount=132,totalDataCount=0,maxPa
rameterCount=2,maxDataCount=40,maxSetupCount=0,flags=0x00,timeout=0,parameterCou
nt=132,parameterOffset=66,parameterDisplacement=0,dataCount=0,dataOffset=198,dat
aDisplacement=0,setupCount=1,pad=1,pad1=0,informationLevel=0x101,filename=\RMSC_
Equities_Transfer\Applications\MPVaR_ATLAS_PANMURE\Input]
        at jcifs.smb.SmbTransport.send(SmbTransport.java:533)
        at jcifs.smb.SmbSession.send(SmbSession.java:228)
        at jcifs.smb.SmbTree.send(SmbTree.java:102)
        at jcifs.smb.SmbFile.send(SmbFile.java:688)
        at jcifs.smb.SmbFile.queryPath(SmbFile.java:1196)
        at jcifs.smb.SmbFile.exists(SmbFile.java:1250)
        at wlb.mpvar.fileimport.transfer.FrontOfficeFileTransfer.run(Unknown
Source)
        at wlb.mpvar.fileimport.demons.BasicDemon.run(Unknown Source)


Reply | Threaded
Open this post in threaded view
|

Re: SmbException in jcifs-1.2.7

Michael B Allen-4
On Wed, 4 Jan 2006 13:47:26 +0000 (UTC)
Rainer Buss <[hidden email]> 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.

Mike

> Error transferring File : jcifs.smb.SmbException:
> jcifs.util.transport.TransportException: Transport1[duss0485/15.1.15.151:445]
> timedout waiting for response to Trans2QueryPathInformation
> [command=SMB_COM_TRANSACTION2,received=false,errorCode=0,flags=0x0018,flags2=0xC
Reply | Threaded
Open this post in threaded view
|

Re: SmbException in jcifs-1.2.7

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

>
> 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.
>
> Mike
>

Hi Mike,

you are right. A closer look upon the log- messages shows, that
error messages with 'The operation completed successfully' have been
written until we changed from jcifs-1.2.3 to jcifs-1.2.7.
Last night we had only error messages with errorCode=0.

The machine serving the remote directories, we are accessing, is
always up, but sometimes there seem to be network problems
or there may be problems with concurrent accesses ?

Our application is a transfer demon, that copies remote files
to a local directory with some transformation. We have several
file types and for each file type a demon thread is started.
So it may be that two threads try to access the same remote
directory at the same time. These threads are not synchronized via
semaphore, because the application was build for a separate mount demon,
we used before jcifs.

Yesterday we had occasional error messages until in the evening
all threads throw these exceptions for about 20 minutes. Afterwards there
have been no exceptions any more (we think that our application did run),
but new files have not been recognized. (We had to restart the application)


When a thread scans a directory a new directory object is instantiated like:

while(true){
try {
SmbFile directory = new SmbFile(source);
String[] files = directory.list();
... do something
} catch(Exception ex) {
log.error...
}
}

Could you please answer the following questions:

Is each instantiation of SmbFile a new (system-) mount in  jcifs ?
Is this (system-)mount closed after life cycle of SmbFile instance ?
Is the number of parallel mounts on the same remote directory a problem ?
When we create a global SmbFile - instance for a directory, is
directory.list() actual for each access or is there a delay.

cu

Rainer

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




Reply | Threaded
Open this post in threaded view
|

Re: Re: SmbException in jcifs-1.2.7

Michael B Allen-4
On Thu, 5 Jan 2006 10:04:14 +0000 (UTC)
Rainer Buss <[hidden email]> wrote:

> The machine serving the remote directories, we are accessing, is
> always up, but sometimes there seem to be network problems
> or there may be problems with concurrent accesses ?

JCIFS is specifically designed for "concurrent access". But if
your network is flakey, increase your loglevel to 2 (should be ok in
production) and see if you're getting any timeouts. If so you might want
to look into the responseTimeout property.

> Could you please answer the following questions:
>
> Is each instantiation of SmbFile a new (system-) mount in  jcifs ?

No. Mounts that connect to the same share are shared. Sessions that use
the same creds are shared. Transports to the same server are shared. But
the ssnLimit property limits the number of sessions on a transport. For
example if ssnLimit is set to 1 a new transport (and thus session and
thus mount) will be created for each SmbFile.

> Is this (system-)mount closed after life cycle of SmbFile instance ?

A mount is closed when the underlying session is closed. A session is
closed when the underlying transport is closed. A transport is closed
after no activity for soTimeout milliseconds (default 15000) or if a
transport error occurs.

> Is the number of parallel mounts on the same remote directory a problem ?

No. Or at least it should not be. There is a known deadlock caused when
a session tries to logoff at the same time one is trying to setup but
AFAIK only one user has been able to trigger it using a test environment
designed to stress the system.

> When we create a global SmbFile - instance for a directory, is
> directory.list() actual for each access or is there a delay.

I don't know what you mean. There should be no "delay". If the directory
is large (e.g. 15000 items) it could talk a while depending on network
conditions [1].

Mike

[1] One thing that greatly slows performance of JCIFS is attribute
expiration. If for example you list a large directory over a slow network
and it takes longer than attExpirationPeriod milliseconds (default
5000), querying attributes like getLength(), exists(), isDirectory(),
etc will cause the client to re-communicate with the server. Setting
a high attrExpirationPeriod can increase performance several orders of
magnitude in certain conditions.
Reply | Threaded
Open this post in threaded view
|

Re: SmbException in jcifs-1.2.7

Rainer Buss
Michael B Allen <mba2000 <at> ioplex.com> writes:
> ..
> JCIFS is specifically designed for "concurrent access". But if
> your network is flakey, increase your loglevel to 2 (should be ok in
> production) and see if you're getting any timeouts. If so you might want
> to look into the responseTimeout property.
> ..

Hi Mike,

we followed your advice, increased the jcifs- loglevel and traced our
application. Several days there where some exceptions, but jcifs did not hang.
This night jcifs had a severe problem, that caused loosing the connection
to remote share permanently. Could you pls have a look at this.

We traced the following:

INFO   | jvm 1    | 2006/01/16 03:46:57 | 00000: FF 53 4D 42 32 00 00 00 00 98
01 80 00 00 00 00  |ÿSMB2...........|
INFO   | jvm 1    | 2006/01/16 03:46:57 | 00010: 00 00 00 00 00 00 00 00 40 00
15 52 00 08 0C 3A  |........@..R...:|

java.lang.StringIndexOutOfBoundsException: String index out of range: 2097248
INFO   | jvm 1    | 2006/01/16 03:46:57 | at java.lang.String.checkBounds
(String.java:292)
INFO   | jvm 1    | 2006/01/16 03:46:57 | at java.lang.String.<init>
(String.java:326)
INFO   | jvm 1    | 2006/01/16 03:46:57 | at
jcifs.smb.Trans2FindFirst2Response.readString(Trans2FindFirst2Response.java:108)
INFO   | jvm 1    | 2006/01/16 03:46:57 | at
jcifs.smb.Trans2FindFirst2Response.readDataWireFormat
(Trans2FindFirst2Response.java:191)
INFO   | jvm 1    | 2006/01/16 03:46:57 | at
jcifs.smb.SmbComTransactionResponse.readBytesWireFormat
(SmbComTransactionResponse.java:146)
INFO   | jvm 1    | 2006/01/16 03:46:57 | at
jcifs.smb.ServerMessageBlock.decode(ServerMessageBlock.java:327)
INFO   | jvm 1    | 2006/01/16 03:46:57 | at jcifs.smb.SmbTransport.doRecv
(SmbTransport.java:453)
INFO   | jvm 1    | 2006/01/16 03:46:57 | at
jcifs.util.transport.Transport.loop(Transport.java:108)
INFO   | jvm 1    | 2006/01/16 03:46:57 | at
jcifs.util.transport.Transport.run(Transport.java:242)
INFO   | jvm 1    | 2006/01/16 03:46:57 | at java.lang.Thread.run
(Thread.java:536)

Afterwards we traced only exceptions like the following one for about
20 minutes and then no more entries have been written since reboot of
our application.

[SUMMIT_INSTRUMENT-#1] transfer.FrontOfficeFileTransfer (?) - Error
transferring File : jcifs.smb.SmbException:
INFO   | jvm 1    | 2006/01/16 03:47:07 |
jcifs.util.transport.TransportException: Transport1[duss0485/15.1.15.151:445]
timedout waiting for response to Trans2QueryPathInformation
[command=SMB_COM_TRANSACTION2,received=false,errorCode=0,flags=0x0018,flags2=0xC
003,signSeq=0,tid=64,pid=21013,uid=2048,mid=14860,wordCount=15,byteCount=119,tot
alParameterCount=118,totalDataCount=0,maxParameterCount=2,maxDataCount=40,maxSet
upCount=0,flags=0x00,timeout=0,parameterCount=118,parameterOffset=66,parameterDi
splacement=0,dataCount=0,dataOffset=184,dataDisplacement=0,setupCount=1,pad=1,pa
d1=0,informationLevel=0x101,filename=\RMSC_Equities_Transfer\Applications\MPVaR_
SUMMIT\Input]

cu

Rainer Buss



Reply | Threaded
Open this post in threaded view
|

Re: Re: SmbException in jcifs-1.2.7

Michael B Allen-4
On Mon, 16 Jan 2006 10:30:08 +0000 (UTC)
Rainer Buss <[hidden email]> wrote:

> Michael B Allen <mba2000 <at> ioplex.com> writes:
> > ..
> > JCIFS is specifically designed for "concurrent access". But if
> > your network is flakey, increase your loglevel to 2 (should be ok in
> > production) and see if you're getting any timeouts. If so you might want
> > to look into the responseTimeout property.
> > ..
>
> Hi Mike,
>
> we followed your advice, increased the jcifs- loglevel and traced our
> application. Several days there where some exceptions, but jcifs did not hang.
> This night jcifs had a severe problem, that caused loosing the connection
> to remote share permanently. Could you pls have a look at this.
>
> We traced the following:
>
> java.lang.StringIndexOutOfBoundsException: String index out of range: 2097248
        at java.lang.String.checkBounds
    ...
        at jcifs.util.transport.Transport.loop(Transport.java:108)
        at jcifs.util.transport.Transport.run(Transport.java:242)
        at java.lang.Thread.run(Thread.java:536)

The problem appears to be a corrupted response. The cause could be a
problem with the network or more likely the server had a hiccup and
chopped off part of a response.

In jcifs/util/transport/Transport.java line 113 change "IOException" to
"Exception" like the following:

   95   private void loop() {
   96     while( thread == Thread.currentThread() ) {
   97       try {
   98         Request key = peekKey();
   99         if (key == null)
  100           throw new IOException( "end of stream" );
  101         synchronized (response_map) {
  102           Response response = (Response)response_map.get( key );
  103           if (response == null) {
  104             if (log.level > 2)
  105               log.println( "Invalid key, skipping message" );
  106             doSkip();
  107           } else {
  108             doRecv( response );
  109             response.isReceived = true;
  110             response_map.notifyAll();
  111           }
  112         }
  113       } catch( Exception ex ) { <----- changed from IOException
  114         String msg = ex.getMessage();
  115         boolean hard = true;
  116
  117         if (log.level > 2)
  118           ex.printStackTrace( log );

Then rebuilt the jcifs jar file with 'ant jar'. See the end of the
README.txt file for detailed build instructions. Now install that jar and
you should be ok. No need to QA this. It's a fully backward compatible
change and very benign (and you don't have any choice :-).

This will prevent the JCIFS transport loop from exiting when a
RuntimeException like the one you're reporting occurs. It won't prevent
the error from occuring but it should allow the client to disconnect
cleanly thereby letting it reconnect to the server when it's behaving
better.

I will apply this to the next release of JCIFS.

> Afterwards we traced only exceptions like the following one for about
> 20 minutes and then no more entries have been written since reboot of
> our application.
>
> [SUMMIT_INSTRUMENT-#1] transfer.FrontOfficeFileTransfer (?) - Error
> transferring File : jcifs.smb.SmbException:
> INFO   | jvm 1    | 2006/01/16 03:47:07 |
> jcifs.util.transport.TransportException: Transport1[duss0485/15.1.15.151:445]
> timedout waiting for response to Trans2QueryPathInformation

Typical response timeouts. Probably network slowness. Doubling the
response timeout might alieviate these a bit.

Mike
Reply | Threaded
Open this post in threaded view
|

Re: SmbException in jcifs-1.2.7

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

>
> The problem appears to be a corrupted response. The cause could be a
> problem with the network or more likely the server had a hiccup and
> chopped off part of a response.
..
>
> This will prevent the JCIFS transport loop from exiting when a
> RuntimeException like the one you're reporting occurs. It won't prevent
> the error from occuring but it should allow the client to disconnect
> cleanly thereby letting it reconnect to the server when it's behaving
> better.

Hi Mike,

we made your fix and for one and a half day our demons did their work
continously.
This morning there was a crash again.
I will attach a long log- output, so that you are able to see the
history from first exception to freeze of JCIFS.
Meanwhile we opened an action item for out network team to check
network and server machine for errors. Their first answer was that
they could not detect remarkably events.

cu

Rainer

Error Log 7:54 19.01.2006

INFO   | jvm 1    | 2006/01/19 07:54:49 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:54:49 | 00000: FF 53 4D 42 34 00 00 00 00 98
01 80 00 00 00 00  |ÿSMB4...........|
INFO   | jvm 1    | 2006/01/19 07:54:49 | 00010: 00 00 00 00 00 00 00 00 40 00
D3 FC 00 08 68 68  |........@.Óü..hh|
INFO   | jvm 1    | 2006/01/19 07:54:49 |
INFO   | jvm 1    | 2006/01/19 07:55:04 | java.net.SocketTimeoutException: Read
timed out
INFO   | jvm 1    | 2006/01/19 07:55:04 | at
java.net.SocketInputStream.socketRead0(Native Method)
INFO   | jvm 1    | 2006/01/19 07:55:04 | at
java.net.SocketInputStream.read(SocketInputStream.java:129)
INFO   | jvm 1    | 2006/01/19 07:55:04 | at
jcifs.util.transport.Transport.readn(Transport.java:29)
INFO   | jvm 1    | 2006/01/19 07:55:04 | at
jcifs.smb.SmbTransport.peekKey(SmbTransport.java:351)
INFO   | jvm 1    | 2006/01/19 07:55:04 | at
jcifs.util.transport.Transport.loop(Transport.java:98)
INFO   | jvm 1    | 2006/01/19 07:55:04 | at
jcifs.util.transport.Transport.run(Transport.java:242)
INFO   | jvm 1    | 2006/01/19 07:55:04 | at java.lang.Thread.run
(Thread.java:536)
INFO   | jvm 1    | 2006/01/19 07:55:05 | java.net.SocketTimeoutException:
Receive timed out
INFO   | jvm 1    | 2006/01/19 07:55:05 | at
java.net.PlainDatagramSocketImpl.receive(Native Method)
INFO   | jvm 1    | 2006/01/19 07:55:05 | at
java.net.DatagramSocket.receive(DatagramSocket.java:671)
INFO   | jvm 1    | 2006/01/19 07:55:05 | at
jcifs.netbios.NameServiceClient.run(NameServiceClient.java:184)
INFO   | jvm 1    | 2006/01/19 07:55:05 | at java.lang.Thread.run
(Thread.java:536)
INFO   | jvm 1    | 2006/01/19 07:55:06 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:06 | 00000: FF 53 4D 42 72 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBr...........|
INFO   | jvm 1    | 2006/01/19 07:55:06 | 00010: 00 00 00 00 00 00 00 00 00 00
D3 FC 00 00 69 68  |..........Óü..ih|
INFO   | jvm 1    | 2006/01/19 07:55:06 |
INFO   | jvm 1    | 2006/01/19 07:55:06 | byteCount=24 but readBytesWireFormat
returned 22
INFO   | jvm 1    | 2006/01/19 07:55:06 | treeConnect: unc=\\duss0485
\FUNCTION,service=A:
INFO   | jvm 1    | 2006/01/19 07:55:16 |
jcifs.util.transport.TransportException: Transport1 timedout waiting for
response to SmbComSessionSetupAndX
[command=SMB_COM_SESSION_SETUP_ANDX,received=false,errorCode=0,flags=0x0018,flag
s2=0xC003,signSeq=0,tid=0,pid=64723,uid=0,mid=26730,wordCount=13,byteCount=125,a
ndxCommand=0x75,andxOffset=186,snd_buf_size=16644,maxMpxCount=10,VC_NUMBER=1,ses
sionKey=0,passwordLength=24,unicodePasswordLength=24,capabilities=4180,accountNa
me=_mpvarprod,primaryDomain=GSA-WLB,NATIVE_OS=Windows 2000,NATIVE_LANMAN=jCIFS]
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
jcifs.util.transport.Transport.sendrecv(Transport.java:74)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbTransport.send
(SmbTransport.java:595)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
jcifs.smb.SmbSession.sessionSetup(SmbSession.java:264)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbSession.send
(SmbSession.java:223)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbTree.treeConnect
(SmbTree.java:144)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbFile.connect
(SmbFile.java:792)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbFile.connect0
(SmbFile.java:762)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbFile.queryPath
(SmbFile.java:1168)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbFile.exists
(SmbFile.java:1250)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
wlb.mpvar.fileimport.transfer.FrontOfficeFileTransfer.run(Unknown Source)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
wlb.mpvar.fileimport.demons.BasicDemon.run(Unknown Source)
INFO   | jvm 1    | 2006/01/19 07:55:16 | java.net.SocketException: Socket
operation on nonsocket: recv failed
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
java.net.SocketInputStream.socketRead0(Native Method)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
java.net.SocketInputStream.read(SocketInputStream.java:129)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
jcifs.util.transport.Transport.readn(Transport.java:29)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
jcifs.smb.SmbTransport.peekKey(SmbTransport.java:351)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
jcifs.util.transport.Transport.loop(Transport.java:98)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
jcifs.util.transport.Transport.run(Transport.java:242)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at java.lang.Thread.run
(Thread.java:536)
INFO   | jvm 1    | 2006/01/19 07:55:16 | 2006-01-19 07:55:16 FATAL
[CONVERT_CURVE-#1] transfer.FrontOfficeFileTransfer (?) - Error transferring
File : jcifs.smb.SmbException:
INFO   | jvm 1    | 2006/01/19 07:55:16 |
jcifs.util.transport.TransportException: Transport1 timedout waiting for
response to SmbComSessionSetupAndX
[command=SMB_COM_SESSION_SETUP_ANDX,received=false,errorCode=0,flags=0x0018,flag
s2=0xC003,signSeq=0,tid=0,pid=64723,uid=0,mid=26730,wordCount=13,byteCount=125,a
ndxCommand=0x75,andxOffset=186,snd_buf_size=16644,maxMpxCount=10,VC_NUMBER=1,ses
sionKey=0,passwordLength=24,unicodePasswordLength=24,capabilities=4180,accountNa
me=_mpvarprod,primaryDomain=GSA-WLB,NATIVE_OS=Windows 2000,NATIVE_LANMAN=jCIFS]
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
jcifs.util.transport.Transport.sendrecv(Transport.java:74)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbTransport.send
(SmbTransport.java:595)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
jcifs.smb.SmbSession.sessionSetup(SmbSession.java:264)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbSession.send
(SmbSession.java:223)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbTree.treeConnect
(SmbTree.java:144)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbFile.connect
(SmbFile.java:792)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbFile.connect0
(SmbFile.java:762)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbFile.queryPath
(SmbFile.java:1168)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at jcifs.smb.SmbFile.exists
(SmbFile.java:1250)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
wlb.mpvar.fileimport.transfer.FrontOfficeFileTransfer.run(Unknown Source)
INFO   | jvm 1    | 2006/01/19 07:55:16 | at
wlb.mpvar.fileimport.demons.BasicDemon.run(Unknown Source)
INFO   | jvm 1    | 2006/01/19 07:55:16 |
INFO   | jvm 1    | 2006/01/19 07:55:16 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:16 | 00000: FF 53 4D 42 72 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBr...........|
INFO   | jvm 1    | 2006/01/19 07:55:16 | 00010: 00 00 00 00 00 00 00 00 00 00
D3 FC 00 00 6B 68  |..........Óü..kh|
INFO   | jvm 1    | 2006/01/19 07:55:16 |
INFO   | jvm 1    | 2006/01/19 07:55:16 | byteCount=24 but readBytesWireFormat
returned 22
INFO   | jvm 1    | 2006/01/19 07:55:16 | treeConnect: unc=\\duss0485
\FUNCTION,service=A:
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 73 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBs...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 40 00
D3 FC 00 08 6C 68  |........@.Óü..lh|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_SUNGARD\Input
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_ATLAS_Panmure\Input\MPVaR
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_ATLAS_Panmure\Input\MPVaR
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_SUMMIT\Input
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_SUMMIT\Input
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_SUMMIT\Input
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_SUMMIT\Input
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_SUMMIT\Input
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_SUMMIT\Input
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_ATLAS_Panmure\Input\MPVaR
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_Sungard_Ldn\Input
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_ATLAS_Panmure\Input\MPVaR
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_SUMMIT\Input
INFO   | jvm 1    | 2006/01/19 07:55:17 | java.net.SocketException: Socket
operation on nonsocket: recv failed
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
java.net.SocketInputStream.socketRead0(Native Method)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
java.net.SocketInputStream.read(SocketInputStream.java:129)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.readn(Transport.java:29)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.smb.SmbTransport.peekKey(SmbTransport.java:351)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.loop(Transport.java:98)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.run(Transport.java:242)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at java.lang.Thread.run
(Thread.java:536)
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 72 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBr...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 00 00
D3 FC 00 00 6D 68  |..........Óü..mh|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | byteCount=24 but readBytesWireFormat
returned 22
INFO   | jvm 1    | 2006/01/19 07:55:17 | treeConnect: unc=\\duss0485
\FUNCTION,service=A:
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 73 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBs...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 40 00
D3 FC 00 08 6E 68  |........@.Óü..nh|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\Produktion\Applications\ExoticTextFiles\ProductionFiles
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_ATLAS_PANMURE\Input
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_ATLAS_PANMURE\Input
INFO   | jvm 1    | 2006/01/19 07:55:17 | queryPath:
\RMSC_Equities_Transfer\Applications\MPVaR_ATLAS_PANMURE\Input
INFO   | jvm 1    | 2006/01/19 07:55:17 | java.net.SocketException: Socket
operation on nonsocket: recv failed
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
java.net.SocketInputStream.socketRead0(Native Method)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
java.net.SocketInputStream.read(SocketInputStream.java:129)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.readn(Transport.java:29)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.smb.SmbTransport.peekKey(SmbTransport.java:351)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.loop(Transport.java:98)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.run(Transport.java:242)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at java.lang.Thread.run
(Thread.java:536)
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 72 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBr...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 00 00
D3 FC 00 00 6F 68  |..........Óü..oh|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | byteCount=24 but readBytesWireFormat
returned 22
INFO   | jvm 1    | 2006/01/19 07:55:17 | treeConnect: unc=\\duss0485
\FUNCTION,service=A:
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 73 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBs...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 40 00
D3 FC 00 08 70 68  |........@.Óü..ph|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | java.net.SocketException: Socket
operation on nonsocket: recv failed
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
java.net.SocketInputStream.socketRead0(Native Method)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
java.net.SocketInputStream.read(SocketInputStream.java:129)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.readn(Transport.java:29)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.smb.SmbTransport.peekKey(SmbTransport.java:351)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.loop(Transport.java:98)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.run(Transport.java:242)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at java.lang.Thread.run
(Thread.java:536)
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 72 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBr...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 00 00
D3 FC 00 00 71 68  |..........Óü..qh|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | byteCount=24 but readBytesWireFormat
returned 22
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 73 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBs...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 00 00
D3 FC 00 08 72 68  |..........Óü..rh|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | treeConnect: unc=\\duss0485
\FUNCTION,service=A:
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 75 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBu...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 40 00
D3 FC 00 08 73 68  |........@.Óü..sh|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | java.net.SocketException: Socket
operation on nonsocket: recv failed
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
java.net.SocketInputStream.socketRead0(Native Method)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
java.net.SocketInputStream.read(SocketInputStream.java:129)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.readn(Transport.java:29)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.smb.SmbTransport.peekKey(SmbTransport.java:351)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.loop(Transport.java:98)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.run(Transport.java:242)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at java.lang.Thread.run
(Thread.java:536)
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 72 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBr...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 00 00
D3 FC 00 00 74 68  |..........Óü..th|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | byteCount=24 but readBytesWireFormat
returned 22
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 32 02 00 01 00 98
01 80 00 00 00 00  |ÿSMB2...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 00 00
D3 FC 00 00 75 68  |..........Óü..uh|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | 2006-01-19 07:55:17 FATAL
[CASHFLOW_SUNGARD-#1] transfer.FrontOfficeFileTransfer (?) - Error transferring
File : jcifs.smb.SmbException: Incorrect function.
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 73 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBs...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 00 00
D3 FC 00 08 76 68  |..........Óü..vh|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | treeConnect: unc=\\duss0485
\FUNCTION,service=A:
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 32 02 00 05 00 98
01 80 00 00 00 00  |ÿSMB2...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 40 00
D3 FC 00 08 77 68  |........@.Óü..wh|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 75 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBu...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 40 00
D3 FC 00 08 78 68  |........@.Óü..xh|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 32 00 00 00 00 98
01 80 00 00 00 00  |ÿSMB2...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 40 00
D3 FC 00 08 79 68  |........@.Óü..yh|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | java.net.SocketException: socket
closed
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
java.net.SocketInputStream.socketRead0(Native Method)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
java.net.SocketInputStream.read(SocketInputStream.java:129)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.readn(Transport.java:29)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.smb.SmbTransport.peekKey(SmbTransport.java:351)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.loop(Transport.java:98)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.util.transport.Transport.run(Transport.java:242)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at java.lang.Thread.run
(Thread.java:536)
INFO   | jvm 1    | 2006/01/19 07:55:17 | doFindFirstNext:
\RMSC_Equities_Transfer\Applications\MPVaR_SUMMIT\Input\
INFO   | jvm 1    | 2006/01/19 07:55:17 | java.net.SocketException: Socket
closed
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
java.net.SocketOutputStream.write(SocketOutputStream.java:136)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at jcifs.smb.SmbTransport.doSend
(SmbTransport.java:413)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
jcifs.smb.SmbTransport.doSend0(SmbTransport.java:418)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at jcifs.smb.SmbTransport.send
(SmbTransport.java:561)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at jcifs.smb.SmbSession.send
(SmbSession.java:229)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at jcifs.smb.SmbTree.send
(SmbTree.java:102)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at jcifs.smb.SmbFile.send
(SmbFile.java:688)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at jcifs.smb.SmbFile.queryPath
(SmbFile.java:1196)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at jcifs.smb.SmbFile.exists
(SmbFile.java:1250)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
wlb.mpvar.fileimport.transfer.FrontOfficeFileTransfer.run(Unknown Source)
INFO   | jvm 1    | 2006/01/19 07:55:17 | at
wlb.mpvar.fileimport.demons.BasicDemon.run(Unknown Source)
INFO   | jvm 1    | 2006/01/19 07:55:17 | New data read: Transport1
[duss0485/15.1.15.151:445]
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00000: FF 53 4D 42 72 00 00 00 00 98
01 80 00 00 00 00  |ÿSMBr...........|
INFO   | jvm 1    | 2006/01/19 07:55:17 | 00010: 00 00 00 00 00 00 00 00 00 00
D3 FC 00 00 81 68  |..........Óü...h|
INFO   | jvm 1    | 2006/01/19 07:55:17 |
INFO   | jvm 1    | 2006/01/19 07:55:17 | byteCount=24 but readBytesWireFormat
returned 22
INFO   | jvm 1    | 2006/01/19 07:55:17 | 2006-01-19 07:55:17 FATAL
[CONVERT_EVENT-#1] transfer.FrontOfficeFileTransfer (?) - Error transferring
File : jcifs.smb.SmbException: The specified network name is no longer
available.
INFO   | jvm 1    | 2006/01/19 07:55:32 | java.net.SocketTimeoutException: Read
timed out
INFO   | jvm 1    | 2006/01/19 07:55:32 | at
java.net.SocketInputStream.socketRead0(Native Method)
INFO   | jvm 1    | 2006/01/19 07:55:32 | at
java.net.SocketInputStream.read(SocketInputStream.java:129)
INFO   | jvm 1    | 2006/01/19 07:55:32 | at
jcifs.util.transport.Transport.readn(Transport.java:29)
INFO   | jvm 1    | 2006/01/19 07:55:32 | at
jcifs.smb.SmbTransport.peekKey(SmbTransport.java:351)
INFO   | jvm 1    | 2006/01/19 07:55:32 | at
jcifs.util.transport.Transport.loop(Transport.java:98)
INFO   | jvm 1    | 2006/01/19 07:55:32 | at
jcifs.util.transport.Transport.run(Transport.java:242)
INFO   | jvm 1    | 2006/01/19 07:55:32 | at java.lang.Thread.run
(Thread.java:536)
INFO   | jvm 1    | 2006/01/19 07:55:51 | java.net.SocketTimeoutException:
Receive timed out
INFO   | jvm 1    | 2006/01/19 07:55:51 | at
java.net.PlainDatagramSocketImpl.receive(Native Method)
INFO   | jvm 1    | 2006/01/19 07:55:51 | at
java.net.DatagramSocket.receive(DatagramSocket.java:671)
INFO   | jvm 1    | 2006/01/19 07:55:51 | at
jcifs.netbios.NameServiceClient.run(NameServiceClient.java:184)
INFO   | jvm 1    | 2006/01/19 07:55:51 | at java.lang.Thread.run
(Thread.java:536)
INFO   | jvm 1    | 2006/01/19 10:53:52 | 2006-01-19 10:53:52 INFO  [Thread-1]
demons.BasicDemon (?) - SHUTDOWN Thread-1 ...
INFO   | jvm 1    | 2006/01/19 10:53:52 | 2006-01-19 10:53:52 INFO  [Thread-1]
demons.BasicDemon (?) - SHUTDOWN Thread-1 ...








Reply | Threaded
Open this post in threaded view
|

Re: Re: SmbException in jcifs-1.2.7

Michael B Allen-4
On Thu, 19 Jan 2006 13:47:29 +0000 (UTC)
Rainer Buss <[hidden email]> wrote:

> Michael B Allen <mba2000 <at> ioplex.com> writes:
>
> >
> > The problem appears to be a corrupted response. The cause could be a
> > problem with the network or more likely the server had a hiccup and
> > chopped off part of a response.
> ..
> >
> > This will prevent the JCIFS transport loop from exiting when a
> > RuntimeException like the one you're reporting occurs. It won't prevent
> > the error from occuring but it should allow the client to disconnect
> > cleanly thereby letting it reconnect to the server when it's behaving
> > better.
>
> Hi Mike,
>
> we made your fix and for one and a half day our demons did their work
> continously.
> This morning there was a crash again.
> I will attach a long log- output, so that you are able to see the
> history from first exception to freeze of JCIFS.
> Meanwhile we opened an action item for out network team to check
> network and server machine for errors. Their first answer was that
> they could not detect remarkably events.
>
> cu
>
> Rainer
>
> Error Log 7:54 19.01.2006
>
> INFO   | jvm 1    | 2006/01/19 07:55:04 | java.net.SocketTimeoutException: Read
> timed out
> INFO   | jvm 1    | 2006/01/19 07:55:05 | java.net.SocketTimeoutException:
> Receive timed out
> INFO   | jvm 1    | 2006/01/19 07:55:16 | java.net.SocketException: Socket
> operation on nonsocket: recv failed
> INFO   | jvm 1    | 2006/01/19 07:55:17 | java.net.SocketException: Socket
> operation on nonsocket: recv failed
> INFO   | jvm 1    | 2006/01/19 07:55:17 | java.net.SocketException: Socket
> operation on nonsocket: recv failed
> INFO   | jvm 1    | 2006/01/19 07:55:17 | java.net.SocketException: Socket
> operation on nonsocket: recv failed
> INFO   | jvm 1    | 2006/01/19 07:55:17 | java.net.SocketException: Socket
> operation on nonsocket: recv failed
> [CASHFLOW_SUNGARD-#1] transfer.FrontOfficeFileTransfer (?) - Error transferring
> File : jcifs.smb.SmbException: Incorrect function.
> INFO   | jvm 1    | 2006/01/19 07:55:17 | java.net.SocketException: socket
> closed
> INFO   | jvm 1    | 2006/01/19 07:55:17 | java.net.SocketException: Socket
> closed
> [CONVERT_EVENT-#1] transfer.FrontOfficeFileTransfer (?) - Error transferring
> File : jcifs.smb.SmbException: The specified network name is no longer
> available.
> INFO   | jvm 1    | 2006/01/19 07:55:32 | java.net.SocketTimeoutException: Read
> timed out

Hi Rainer,

The above errors are all not directly related to JCIFS. This looks like
some kind of momentary netork or VM failure. After the transport is in
error a cascade of errors follows from all the threads that are using
it. Are there a lot more errors than you're showing here?  Add a network
watchdog that constantly pings a target and logs it. Check your VM memory
usage. Which version of VM are you using? Increase the loglevel to 2,
look at the very first error, and then look closely at the corresponding
JCIFS code to see if you can make sense of what's happening. I can't
debug this kind of failure without help.

Something non-JCIFS related is very likely triggering this in which case
the important question is - does it recover?

Mike
Reply | Threaded
Open this post in threaded view
|

Re: Re: SmbException in jcifs-1.2.7

Michael B Allen-4
In reply to this post by Michael B Allen-4
Did you ever try this Rainer?

On Mon, 16 Jan 2006 13:51:10 -0500
Michael B Allen <[hidden email]> wrote:

> On Mon, 16 Jan 2006 10:30:08 +0000 (UTC)
> Rainer Buss <[hidden email]> wrote:
>
> > Michael B Allen <mba2000 <at> ioplex.com> writes:
> > > ..
> > > JCIFS is specifically designed for "concurrent access". But if
> > > your network is flakey, increase your loglevel to 2 (should be ok in
> > > production) and see if you're getting any timeouts. If so you might want
> > > to look into the responseTimeout property.
> > > ..
> >
> > Hi Mike,
> >
> > we followed your advice, increased the jcifs- loglevel and traced our
> > application. Several days there where some exceptions, but jcifs did not hang.
> > This night jcifs had a severe problem, that caused loosing the connection
> > to remote share permanently. Could you pls have a look at this.
> >
> > We traced the following:
> >
> > java.lang.StringIndexOutOfBoundsException: String index out of range: 2097248
> at java.lang.String.checkBounds
>     ...
> at jcifs.util.transport.Transport.loop(Transport.java:108)
> at jcifs.util.transport.Transport.run(Transport.java:242)
> at java.lang.Thread.run(Thread.java:536)
>
> The problem appears to be a corrupted response. The cause could be a
> problem with the network or more likely the server had a hiccup and
> chopped off part of a response.
>
> In jcifs/util/transport/Transport.java line 113 change "IOException" to
> "Exception" like the following:
>
>    95   private void loop() {
>    96     while( thread == Thread.currentThread() ) {
>    97       try {
>    98         Request key = peekKey();
>    99         if (key == null)
>   100           throw new IOException( "end of stream" );
>   101         synchronized (response_map) {
>   102           Response response = (Response)response_map.get( key );
>   103           if (response == null) {
>   104             if (log.level > 2)
>   105               log.println( "Invalid key, skipping message" );
>   106             doSkip();
>   107           } else {
>   108             doRecv( response );
>   109             response.isReceived = true;
>   110             response_map.notifyAll();
>   111           }
>   112         }
>   113       } catch( Exception ex ) { <----- changed from IOException
>   114         String msg = ex.getMessage();
>   115         boolean hard = true;
>   116
>   117         if (log.level > 2)
>   118           ex.printStackTrace( log );
>
> Then rebuilt the jcifs jar file with 'ant jar'. See the end of the
> README.txt file for detailed build instructions. Now install that jar and
> you should be ok. No need to QA this. It's a fully backward compatible
> change and very benign (and you don't have any choice :-).
>
> This will prevent the JCIFS transport loop from exiting when a
> RuntimeException like the one you're reporting occurs. It won't prevent
> the error from occuring but it should allow the client to disconnect
> cleanly thereby letting it reconnect to the server when it's behaving
> better.
>
> I will apply this to the next release of JCIFS.
>
> > Afterwards we traced only exceptions like the following one for about
> > 20 minutes and then no more entries have been written since reboot of
> > our application.
> >
> > [SUMMIT_INSTRUMENT-#1] transfer.FrontOfficeFileTransfer (?) - Error
> > transferring File : jcifs.smb.SmbException:
> > INFO   | jvm 1    | 2006/01/16 03:47:07 |
> > jcifs.util.transport.TransportException: Transport1[duss0485/15.1.15.151:445]
> > timedout waiting for response to Trans2QueryPathInformation
>
> Typical response timeouts. Probably network slowness. Doubling the
> response timeout might alieviate these a bit.
>
> Mike
>
Reply | Threaded
Open this post in threaded view
|

Re: Re: SmbException in jcifs-1.2.7

Michael B Allen-4
In reply to this post by Michael B Allen-4
Applied in 1.2.8 to be released RSN.

On Mon, 16 Jan 2006 13:51:10 -0500
Michael B Allen <[hidden email]> wrote:

> On Mon, 16 Jan 2006 10:30:08 +0000 (UTC)
> Rainer Buss <[hidden email]> wrote:
>
> > Michael B Allen <mba2000 <at> ioplex.com> writes:
> > > ..
> > > JCIFS is specifically designed for "concurrent access". But if
> > > your network is flakey, increase your loglevel to 2 (should be ok in
> > > production) and see if you're getting any timeouts. If so you might want
> > > to look into the responseTimeout property.
> > > ..
> >
> > Hi Mike,
> >
> > we followed your advice, increased the jcifs- loglevel and traced our
> > application. Several days there where some exceptions, but jcifs did not hang.
> > This night jcifs had a severe problem, that caused loosing the connection
> > to remote share permanently. Could you pls have a look at this.
> >
> > We traced the following:
> >
> > java.lang.StringIndexOutOfBoundsException: String index out of range: 2097248
> at java.lang.String.checkBounds
>     ...
> at jcifs.util.transport.Transport.loop(Transport.java:108)
> at jcifs.util.transport.Transport.run(Transport.java:242)
> at java.lang.Thread.run(Thread.java:536)
>
> The problem appears to be a corrupted response. The cause could be a
> problem with the network or more likely the server had a hiccup and
> chopped off part of a response.
>
> In jcifs/util/transport/Transport.java line 113 change "IOException" to
> "Exception" like the following:
>
>    95   private void loop() {
>    96     while( thread == Thread.currentThread() ) {
>    97       try {
>    98         Request key = peekKey();
>    99         if (key == null)
>   100           throw new IOException( "end of stream" );
>   101         synchronized (response_map) {
>   102           Response response = (Response)response_map.get( key );
>   103           if (response == null) {
>   104             if (log.level > 2)
>   105               log.println( "Invalid key, skipping message" );
>   106             doSkip();
>   107           } else {
>   108             doRecv( response );
>   109             response.isReceived = true;
>   110             response_map.notifyAll();
>   111           }
>   112         }
>   113       } catch( Exception ex ) { <----- changed from IOException
>   114         String msg = ex.getMessage();
>   115         boolean hard = true;
>   116
>   117         if (log.level > 2)
>   118           ex.printStackTrace( log );
>
> Then rebuilt the jcifs jar file with 'ant jar'. See the end of the
> README.txt file for detailed build instructions. Now install that jar and
> you should be ok. No need to QA this. It's a fully backward compatible
> change and very benign (and you don't have any choice :-).
>
> This will prevent the JCIFS transport loop from exiting when a
> RuntimeException like the one you're reporting occurs. It won't prevent
> the error from occuring but it should allow the client to disconnect
> cleanly thereby letting it reconnect to the server when it's behaving
> better.
>
> I will apply this to the next release of JCIFS.
>
> > Afterwards we traced only exceptions like the following one for about
> > 20 minutes and then no more entries have been written since reboot of
> > our application.
> >
> > [SUMMIT_INSTRUMENT-#1] transfer.FrontOfficeFileTransfer (?) - Error
> > transferring File : jcifs.smb.SmbException:
> > INFO   | jvm 1    | 2006/01/16 03:47:07 |
> > jcifs.util.transport.TransportException: Transport1[duss0485/15.1.15.151:445]
> > timedout waiting for response to Trans2QueryPathInformation
>
> Typical response timeouts. Probably network slowness. Doubling the
> response timeout might alieviate these a bit.
>
> Mike
>