[jcifs] jCifs stops working.

[Marko.Krejic at corp.vodafone.se]

I am using NTLM filter and using the following config:

<filter>
        <filter-name>NtlmHttpFilter</filter-name>
        <filter-class>jcifs.http.NtlmHttpFilter</filter-class>

        <init-param>
                    <param-name>jcifs.smb.client.domain</param-name>
                    <param-value>europolitan</param-value>
                </init-param>
                <init-param>
                    <param-name>jcifs.http.domainController</param-name>
                    <param-value>172.16.20.160</param-value>
                </init-param>
                <init-param>
                    <param-name>jcifs.netbios.wins</param-name>
                    <param-value>172.16.21.160,172.16.21.82</param-value>
                </init-param>
                <init-param>
                    <param-name>jcifs.util.loglevel</param-name>
                    <param-value>10</param-value>
                </init-param>
    </filter>


Thanks
Marko

-----Original Message-----
From: Michael B Allen [mailto:mba2000 at ioplex.com] 
Sent: den 26 januari 2006 07:48
To: Marko.Krejic at corp.vodafone.se
Cc: jcifs at lists.samba.org
Subject: Re: [jcifs] jCifs stops working.


On Thu, 26 Jan 2006 07:21:40 +0100 Marko.Krejic at corp.vodafone.se wrote:

> Hi!
> 
> I have problems with that jCifs stops responding sometimes. I have not 
> really been able to connect to a specific case, just that it has been 
> a peek of users.
> 
> I am using jCIFS 1.2.7 and here is a part of the log:
> 
> java.io.InterruptedIOException: Read timed out
>         at java.net.SocketInputStream.socketRead(Native Method) 
> SmbComLogoffAndX[command=SMB_COM_LOGOFF_ANDX,received=false,errorCode=
> 0,flag
>
SmbComTreeDisconnect[command=SMB_COM_TREE_DISCONNECT,received=false,errorCod
>
SmbComNegotiate[command=SMB_COM_NEGOTIATE,received=false,errorCode=0,flags=0
>
SmbComNegotiateResponse[command=SMB_COM_NEGOTIATE,received=false,errorCode=0
> 
> After this it doesn't work anymore.
> 
> Can anybody help me?

Mmm, I don't know. This looks like a relatively harmless read timeout,
disconnect, and renegotiation. I suppose it could be that the resource open
is in a bad state after the reconnect. But I can't tell what it is from
this. What type of resource is being used? Are you just reading a file or
are you using the NTLM HTTP filter or what?

Mike

______________________________________ 
This message and any files or documents attached are confidential and may
also be legally privileged or protected by other legal rules. It is intended
only for the individual or entity named. If you are not the named addressee
or you have received this email in error, please inform the sender
immediately, delete it from your system and do not copy or disclose it or
its contents or use it for any purpose.
 Thank you. 

Please also note that transmission cannot be guaranteed to be secure or
error-free.