[jira] [Resolved] (CONNECTORS-283) Upgrade to jcifs.jar 1.3.17

2011-10-27 Thread Shinichiro Abe (Resolved) (JIRA)

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shinichiro Abe resolved CONNECTORS-283.
---

Resolution: Fixed

r1189564

 Upgrade to jcifs.jar 1.3.17
 ---

 Key: CONNECTORS-283
 URL: https://issues.apache.org/jira/browse/CONNECTORS-283
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Build, JCIFS connector
Affects Versions: ManifoldCF 0.4
Reporter: Shinichiro Abe
Assignee: Shinichiro Abe
Priority: Minor
 Fix For: ManifoldCF 0.4

 Attachments: CONNECTORS-283.patch


 I upgrade new jcifs version because of missing link of previous version 
 1.3.16.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (CONNECTORS-281) RSS connector takes nearly a second to fetch a document even with no throttling

2011-10-27 Thread Karl Wright (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/CONNECTORS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13137765#comment-13137765
 ] 

Karl Wright commented on CONNECTORS-281:


With the fixes as checked in so far, there's no appreciable difference between 
early parts of the crawl and later parts.  So I'm going to resolve this issue.


 RSS connector takes nearly a second to fetch a document even with no 
 throttling
 ---

 Key: CONNECTORS-281
 URL: https://issues.apache.org/jira/browse/CONNECTORS-281
 Project: ManifoldCF
  Issue Type: Bug
  Components: RSS connector
Affects Versions: ManifoldCF 0.4
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.4


 The RSS connector load test shows that the RSS connector is overthrottling, 
 for some reason.
 10-24-2011 05:30:50.423   fetch   
 http://localhost:8189/rss/gen.php?doc=4feed=782type=doc
   200 46  843
 ... Where 843 ms is taken to fetch a document of size 46 bytes.  This is with 
 connection parameters as follows:
 Parameters:   Robots usage=none
 Max fetches per minute=100
 Email address=someb...@somewhere.com
 KB per second=100
 Max server connections=100

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Resolved] (CONNECTORS-281) RSS connector takes nearly a second to fetch a document even with no throttling

2011-10-27 Thread Karl Wright (Resolved) (JIRA)

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright resolved CONNECTORS-281.


Resolution: Fixed

 RSS connector takes nearly a second to fetch a document even with no 
 throttling
 ---

 Key: CONNECTORS-281
 URL: https://issues.apache.org/jira/browse/CONNECTORS-281
 Project: ManifoldCF
  Issue Type: Bug
  Components: RSS connector
Affects Versions: ManifoldCF 0.4
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.4


 The RSS connector load test shows that the RSS connector is overthrottling, 
 for some reason.
 10-24-2011 05:30:50.423   fetch   
 http://localhost:8189/rss/gen.php?doc=4feed=782type=doc
   200 46  843
 ... Where 843 ms is taken to fetch a document of size 46 bytes.  This is with 
 connection parameters as follows:
 Parameters:   Robots usage=none
 Max fetches per minute=100
 Email address=someb...@somewhere.com
 KB per second=100
 Max server connections=100

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (CONNECTORS-279) Postgresql load test job delete document cleanup fails sometimes and leaves orphaned documents

2011-10-27 Thread Karl Wright (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/CONNECTORS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13137766#comment-13137766
 ] 

Karl Wright commented on CONNECTORS-279:


Posted to both stackoverflow and postgresql-general lists. Other people on the 
postgresql lists seem to have encountered this but no resolution as yet appears 
to be available.  It doesn't seem like the postgresql team is taking it 
seriously.


 Postgresql load test job delete document cleanup fails sometimes and leaves 
 orphaned documents
 --

 Key: CONNECTORS-279
 URL: https://issues.apache.org/jira/browse/CONNECTORS-279
 Project: ManifoldCF
  Issue Type: Bug
  Components: Framework crawler agent
Affects Versions: ManifoldCF 0.4
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.4


 Running the postgresql load test on my laptop, I was surprised when the test 
 did not finish.  The UI indicated that the job was being deleted, but there 
 were 49,000 documents and that number was not moving.  Further inspection 
 yielded the following:
 - Job was in the DELETING state
 - Documents were in the BEINGDELETED state
 - No activity of any kind ongoing
 The log had no errors.
 It was impossible to get a thread dump, but a cursory inspection of the code 
 indicated that either the documents were being marked as BEINGDELETED but 
 were not actually being placed on the in-memory queue, or the delete threads 
 were picking up the documents and somehow avoiding marking them as being 
 processed.
 Also, probably unrelated, the Document Status report listed these documents 
 as having a status of Being removed and a state of Unknown.  The 
 Unknown should have been a Deleting.  Since the extended WHEN... ELSE 
 clause has a reasonable condition for the Deleting answer, it's hard to see 
 how this could have occurred either.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira