[jcifs] Re: SmbException in jcifs-1.2.7

[Michael B Allen]

On Thu, 19 Jan 2006 13:47:29 +0000 (UTC)
Rainer Buss <rainer.buss at rbconsult.de> 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