jcifs classes are not initialized when connector is run on Linux 64-bit environment

[GoogleCodeExporter]

HttpClient-Modified library makes use of Jcifs for supporting NTLM V2. On
Suse Linux 64-bit environment it has been observed that Jcifs classes like
Type1Message are not initialized properly and hence connector configuration
does not gets saved.

It was also observed that hostname resolution was not getting succeeded on
the machine and hence connector was throwing "UnknownHostException" when
the Crawl URL contained the host name. This was expected to be resolved
after using host's IP address instead of hostname. But, because of the
Jcifs issue mentioned in the first para, this was also not working and
there were exception related initialization of Jcifs classes.

The class initialization issue with Jcifs gets resolved with the latest
version (1.3.X) of Jcifs library. There are important differences in the
way Type1Message.java like classes are written in these two versions of
Jcifs. Though, i was not able track the exact fix, yet.

Since, some function signatures have been changed in the latest version of
Jcifs, upgrading to this library will require changing/upgrading HttpClient
library as well.

Original issue reported on code.google.com by th.nitendra on 29 Jan 2010 at 10:20

[GoogleCodeExporter]

Also check Issue 139

Original comment by rakeshs101981@gmail.com on 29 Jan 2010 at 11:58

[GoogleCodeExporter]

Original comment by shashank...@gmail.com on 18 Mar 2011 at 12:05

[GoogleCodeExporter]

This issue is filed as Google issue #6514004

Original comment by tdnguyen@google.com on 18 May 2012 at 12:13

• Changed state: Duplicate