Re: Random problems connecting to DFS server

Absolutely.

Is this just for Mike's information, or is there a bugzilla somewhere
that I can increase its priority?

Simon

On 4/17/2012 11:49 AM, Gabor Herr wrote:
>
> Great, good to hear that the fix worked for you. I assume we get a +1
> from you to include the patch into the main branch.
>
> Gabor
>
> Am 16.04.2012 23:58 schrieb "Simon Weatherill"
> <[email protected] <mailto:[email protected]>>:
>
>     Thank you, thank you, thank you!
>
>     That fixed the problem. Thanks for the quick response.
>
>     Simon
>
>     On 4/16/2012 5:40 PM, Gabor Herr wrote:
>>
>>     Hi Simon,
>>
>>     This sounds very similar to our jcifs problem reported in
>>     https://lists.samba.org/archive/jcifs/2012-March/009874.html
>>
>>     Maybe you could give a try with the patch suggested in my post.
>>     It should also work with version 1.3.17.
>>
>>     Good luck...
>>
>>     Gabor
>>
>>     Am 16.04.2012 21:59 schrieb "Simon Weatherill"
>>     <[email protected] <mailto:[email protected]>>:
>>     >
>>     > I've been seeing many errors that have a final stack trace of
>>     > jcifs.smb.Dfs.resolve(Dfs.java:169) (jCIFS 1.3.17):
>>     >
>>     > java.lang.NullPointerException
>>     >        at jcifs.smb.Dfs.resolve(Dfs.java:169)
>>     >        at jcifs.smb.SmbFile.resolveDfs(SmbFile.java:671)
>>     >        at jcifs.smb.SmbFile.getDfsPath(SmbFile.java:1536)
>>     >        at ListFiles.main(ListFiles.java:45)
>>     >
>>     > I'm using a slightly modified ListFiles.java to test this. I
>>     have a list
>>     > of 12608 directories, which all exist. If I invoke ListFiles
>>     for each
>>     > directory separately, it completes fine. If I invoke it once
>>     for all
>>     > directories, it will fail after reading about 3000 directories.
>>     If I add
>>     > a test to see if the path exists before calling listFiles(),
>>     the problem
>>     > goes away. I don't know if it is an issue of timing or whether the
>>     > exists() call does something that avoids the problem. Once the
>>     problem
>>     > starts all remaining  directories have the same problem.
>>     >
>>     > I added a getDfsPath() call (and printed the result) thinking
>>     that might
>>     > point in a particular direction. When I add this, it fails on the
>>     > getDfsPath() before it gets to getFiles().
>>     >
>>     > We're using jCIFS in an RMI server that is always running. We
>>     can clear
>>     > up the problem by restarting the server, but it comes back.
>>     >
>>     > Any ideas?
>>     >
>>     > Thanks,
>>     > Simon
>>