[jcifs] About the long crawling time again...

[torjo845 at student.liu.se]

Now, after about 20-30 minutes I got an exception:

torgny at p13:~/java$ java -Djcifs.properties=LinGet.prp 
ThreadedSmbCrawler smb://750 1 1
Aug 3 08:50:11.280 - SmbFile exception
java.net.NoRouteToHostException: Connection timed out
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
        at java.net.PlainSocketImpl.connectToAddress
(PlainSocketImpl.java:132)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:119)
        at java.net.Socket.<init>(Socket.java:269)
        at java.net.Socket.<init>(Socket.java:173)
        at jcifs.netbios.NbtSocket.<init>(NbtSocket.java:54)
        at jcifs.netbios.NbtSocket.<init>(NbtSocket.java:50)
        at jcifs.smb.SmbTransport.ensureOpen(SmbTransport.java:215)
        at jcifs.smb.SmbTransport.send(SmbTransport.java:400)
        at jcifs.smb.SmbTransport.negotiate(SmbTransport.java:525)
        at jcifs.smb.SmbTransport.send(SmbTransport.java:362)
        at jcifs.smb.SmbSession.sessionSetup(SmbSession.java:154)
        at jcifs.smb.SmbSession.send(SmbSession.java:128)
        at jcifs.smb.SmbTree.treeConnect(SmbTree.java:84)
        at jcifs.smb.SmbTree.sendTransaction(SmbTree.java:49)
        at jcifs.smb.SmbTree.netShareEnum(SmbTree.java:296)
        at jcifs.smb.SmbFile.list(SmbFile.java:702)
        at ThreadedSmbCrawler$SmbCrawlerThread.run
(ThreadedSmbCrawler.java:48)

Sorry for sending 2 messages like this.


----- Original Message -----
From: "Allen, Michael B (RSCH)" <Michael_B_Allen at ml.com>
Date: Thursday, August 2, 2001 10:46 pm
Subject: RE: [jcifs] About the long crawling time again...

> This depends on a lot of things Torgny. It's very hard for me to 
> tell whats going on
> without looking at your code. If you call exists() then, yes, 
> obviously it should
> return an accurate value for that particular moment in time. 
> However, if you make
> this test and then put the URL into a list that might not be 
> traversed again for some
> time then it might produce some funky results because the 
> Transport object will
> disconnect but still exist and I don't think it goes through all 
> the hula-hoops to
> reconnect. There are alot of other factors to consider too. For 
> example, are you
> using IP addresses as opposed to host names? Are you messing with 
> any properties
> like retryTimeouts, soTimeouts, retryCounts, etc? Are you still 
> using your WINS ip
> for baddr? Does the ThreadedSmbCrawler produce these exceptions?
> 
> Mike
> 
> > -----Original Message-----
> > From:	Torgny Johansson 
[SMTP:torgny.johansson at kommun.ljungby.se]
> > Sent:	Thursday, August 02, 2001 10:26 AM
> > To:	jcifs at samba.org
> > Subject:	[jcifs] About the long crawling time again...
> > 
> > Ok, let's say that it's taking so long to do the crawl because 
> some of the
> > pcs in the list are shut down when my crawler comes around to 
> them. I've put
> > a "if SmbFile.exists()" that should check whether or not the 
> specified share
> > exists or not right? If the pc isn't turned on, shouldn't this 
> say that the
> > pc isn't available, and my crawler should go on to the next one? 
> A pc that
> > seems to be turned off obviously get a true value from the 
> exist() method
> > otherwise the crawler would skip it.
> > 
> > 
> > 
> 
> 
>