[jcifs] jcifs.smb.SmbException: jcifs.util.transport.TransportException: Transport24 timedout waiting for response to SmbComSessionSetupAndX

[Ghouse, Sherjeel]

Mike,

You were right, these exceptions disappeared after the Domain Controllers were upgraded to Windows 2003 and are stable. I also updated the web.xml to use the default configuration properties provided by jCIFS.

I appreciate your advise.

Thanks,
Sherjeel 


-----Original Message-----
From: Michael B Allen [mailto:mba2000 at ioplex.com] 
Sent: Monday, August 07, 2006 3:25 PM
To: Ghouse, Sherjeel
Cc: jcifs at lists.samba.org
Subject: Re: [jcifs] jcifs.smb.SmbException: jcifs.util.transport.TransportException: Transport24 timedout waiting for response to SmbComSessionSetupAndX

So you mean the machines being upgraded are sometimes not available and
thus the error? That would make sense. You could switch to using the
jcifs.http.domainController property to specify one stable W2K3 machine
for the duration of the upgrade.

Also, some of those properties are strange. An soTimeout of 40000 means
40 seconds. I think the default of 10 minutes is better. In general you
shouldn't change any properties unless explicitly instructed to do so or
if we couldn't provide instructions and the Filter doesn't work properly
without them.

Mike

On Mon, 7 Aug 2006 13:34:23 -0500
"Ghouse, Sherjeel" <Sherjeel.Ghouse at molex.com> wrote:

> Mike,
> 
> Our Infrastructure team is in process of Domain upgrade to Windows 2003. Not all Domain Controllers have been upgraded to Windows 2003 yet. During, this time I have seen the following exceptions in the Server Logs. So far I have seen the exceptions for 3 different user accounts. I don't know if the users experienced a problem yet since this is a global app. I just wanted to be proactive and get your advise. Should I consider this as a problem or can this be igonored ?? . Will increasing the soTimeout resolve this ????
> 
> BEA-101019  <javascript:doPopUp('BEA-101019&ARG0=ServletContext%28id%3D6899410%2Cname%3Dmidas%2Ccontext-path%3D%2Fmidas%29')> Aug 7, 2006 11:07:15 AM CDT Error HTTP [ServletContext(id=6899410,name=*****,context-path=/*******] Servlet failed with IOException 
> jcifs.smb.SmbException: 
> 
> Environment Info
> jCIFS client is running on Windows 2003 server
> App Server : WebLogic 8.1
> Domain : Windows 2000 / 2003 (Some DCs have been upgraded to 2003 and some are still in the process. We are still using the once that have not been upgraded to 2003)
> web.xml looks like this 
> <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>*****</param-value>
>     </init-param>    
>     <init-param>
>       <param-name>jcifs.netbios.wins</param-name>
>       <param-value>WINS</param-value>
>     </init-param>
>     <init-param>
>       <param-name>jcifs.netbios.retryTimeout</param-name>
>       <param-value>10000</param-value>
>     </init-param>
>     <init-param>
>       <param-name>jcifs.netbios.soTimeout</param-name>
>       <param-value>10000</param-value>
>     </init-param>
>     <init-param>
>       <param-name>jcifs.util.loglevel</param-name>
>       <param-value>3</param-value>
>     </init-param>
>     <init-param>
>       <param-name>jcifs.smb.client.soTimeout</param-name>
>       <param-value>40000</param-value>
>     </init-param>
>     <init-param>
>       <param-name>jcifs.smb.client.responseTimeout</param-name>
>       <param-value>30000</param-value>
>     </init-param>
>     <init-param>
>       <param-name>jcifs.smb.client.username</param-name>
>       <param-value>*****</param-value>
>     </init-param>
>     <init-param>
>       <param-name>jcifs.smb.client.password</param-name>
>       <param-value>*****</param-value>
>     </init-param>
>     
> </filter>
> 
> 
> 
> 
> 
> 
> 
> 
> CONFIDENTIALITY NOTICE: This message (including any attachments) may contain Molex confidential information, protected by law. If this message is confidential, forwarding it to individuals, other than those with a need to know, without the permission of the sender, is prohibited.
> 
> This message is also intended for a specific individual. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message or taking of any action based upon it, is strictly prohibited. 
> 
> Chinese  Japanese
> 
> www.molex.com/confidentiality.html
> 
> 


-- 
Michael B Allen
PHP Active Directory SSO
http://www.ioplex.com/


CONFIDENTIALITY NOTICE: This message (including any attachments) may contain Molex confidential information, protected by law. If this message is confidential, forwarding it to individuals, other than those with a need to know, without the permission of the sender, is prohibited.

This message is also intended for a specific individual. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message or taking of any action based upon it, is strictly prohibited. 

Chinese  Japanese

www.molex.com/confidentiality.html