Heavy file sync results in too many concurrent connections to the Search Appliance

When a full sync kicks in with 4 threads on a net folder with thousands of files (for example 10,000 files), the system pushes the number of connections to the index server up to nearly a thousands even though only 4 threads are making connection requests. This is due to the fact that RMI manager on the client side is creating new connections for every request while the connections previously opened and used have not been closed yet.

A fix for this issue is available in the Filr 1.0.1 Hot Patch 1, available via the Novell Patch Finder.

The following error was seen in the Filr ssf.log file:

2013-09-27 12:57:25,249 WARN  [http-apr-8443-exec-3] [org.kablink.teaming.spring.web.portlet.DispatcherPortlet] - Handler execution resulted in exception - forwarding to resolved error view
org.kablink.teaming.lucene.LuceneException: java.rmi.ConnectIOException: Exception creating connection to: filesearch.performance.com; nested exception is:
    java.net.SocketException: Connection reset / java.rmi.ConnectIOException: Exception creating connection to: filesearch.performance.com; nested exception is:
    java.net.SocketException: Connection reset