As long as the fetch is retried, and is eventually successful, I think this is OK. Can you confirm this?
Karl On Tue, Jan 29, 2013 at 9:01 AM, Shinichiro Abe <[email protected]> wrote: > Hi, > > I'm using Web connector in RC7, I saw the symptom which I didn't see in MCF > 1.0.1. > Simple History is showing sometimes: > Result Code -1, "The target server failed to respond" at fetch activity. > > Now I'm using Web connector in MCF 1.0.1, but I can not see this results at > all. > > Simple History is showing: > Start Time Activity Identifier Result Code Bytes Time > Result Description > 01-29-2013 22:29:26.999 fetch > http://www.rondhuit.com/technologies/apache-lucene-apache-solr.html > -1 0 1 The target server failed to respond > 01-29-2013 22:29:06.999 fetch http://www.rondhuit.com/?p=836 > -1 0 2 The target server failed to respond > > manifoldcf.log is showing: > WARN 2013-01-29 22:29:07,003 (Worker thread '27') - Pre-ingest service > interruption reported for job 1359465187706 connection '1': Timed out waiting > for response for 'http://www.rondhuit.com/?p=836': The target server failed > to respond > WARN 2013-01-29 22:29:27,004 (Worker thread '41') - Pre-ingest service > interruption reported for job 1359465187706 connection '1': Timed out waiting > for response for > 'http://www.rondhuit.com/technologies/apache-lucene-apache-solr.html': The > target server failed to respond > > I'm +1 if this problem is not critical. > I've already checked Filesystem, JCIFS, JDBC and SharePoint connector. > > Regards, > Shinichiro Abe > > > > On 2013/01/29, at 9:07, Karl Wright wrote: > >> - Ran all tests >> - Ran multiprocess example, and created a solr output connection >> >> +1 from me. >> >> Karl >> >> On Mon, Jan 28, 2013 at 5:09 PM, Karl Wright <[email protected]> wrote: >>> Please vote on whether or not to release ManifoldCF 1.1, RC7. >>> >>> The release artifact can be found at: >>> >>> http://people.apache.org/~kwright/apache-manifoldcf-1.1 >>> >>> There is a tag at: >>> >>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1-RC7 >>> >>> This release candidate fixes a packaging problem for wars similar to >>> CONNECTORS-619. It also fixes a problem with the CMIS connector >>> and another SolrJ-related issue (CONNECTORS-622 and CONNECTORS-623). >>> >>> This release candidate provides a better workaround for >>> CONNECTORS-616 than RC5. It also fixes CONNECTORS-617. >>> >>> This release candidate fixes one problem since RC4, which is >>> the inconfigurability of the commit action path for Solr commits in >>> the Solr connector. This needed to be fixed to maintain backwards >>> compatibility. CONNECTORS-621. >>> >>> This release candidate fixes two problems since RC3. The problems >>> were in the included jars for the multiprocess example (CONNECTORS-619) >>> and in connection leakage for JDBC handles (CONNECTORS-620). >>> >>> This release candidate fixes one problem since RC2. The problem is >>> CONNECTORS-618, which relates to MySQL performance. >>> >>> This release candidate fixes one additional problem since RC1. The >>> problem is CONNECTORS-616, and relates to Solr dropping connections >>> during >>> indexing. >>> >>> This release candidate fixes two other problems since RC0, both >>> related to Solr 4.0.0 support. >>> - CONNECTORS-613: The version of Tika used in Solr 4.0.0 cannot >>> extract text unless told an accurate mime type. While this is >>> probably a Tika bug, in this ticket we at least make sure a good guess >>> as to the mime type is sent to Solr. >>> - CONNECTORS-614: Fix logic having to do with releasing idle Solr >>> connections. This shows up as socket timeout exceptions, because it >>> becomes very easy to exhaust the Solr application server's thread pool >>> when idle connections are not released in a timely way. >>> >>> This release includes a significant amount of long-planned upgrading >>> and refactoring since Apache ManifoldCF 1.0.1, including: >>> - Port to HttpComponents from commons-httpclient >>> - Port to SolrJ from homegrown for the Solr connector, so that >>> SolrCloud is supported >>> - Improved NTLM support >>> - Partial Kerberos support >>> - Many other improvements, which are summarized in CHANGES.txt >
