You have 10 connections, all of which are blocked waiting in the following way:
>>>>>>
"Worker thread '25'" daemon prio=6 tid=0x000000000758a800 nid=0xe58
runnable [0x000000000a70e000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at
org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at
org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at
org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:260)
at
org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at
org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at
org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at
org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at
org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219)
at
org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at
org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at
org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:633)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:454)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at com.systemware.ci.sdk.CIConnector.sendTxn(CIConnector.java:208)
at com.systemware.ci.sdk.CIConnector.sendTxn(CIConnector.java:310)
at
org.apache.manifoldcf.agents.output.dupfinder.DupFinderConnector.uploadDocumentToCI(DupFinderConnector.java:231)
at
org.apache.manifoldcf.agents.output.dupfinder.DupFinderConnector.addOrReplaceDocument(DupFinderConnector.java:166)
at
org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.addOrReplaceDocument(IncrementalIngester.java:1433)
at
org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.performIngestion(IncrementalIngester.java:418)
at
org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.documentIngest(IncrementalIngester.java:313)
at
org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ingestDocument(WorkerThread.java:1565)
at
org.apache.manifoldcf.crawler.connectors.filesystem.FileConnector.processDocuments(FileConnector.java:275)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:564)
<<<<<<
They're clearly talking to some remote system which is not responding.
Karl
On Tue, Jul 5, 2011 at 3:04 PM, Farzad Valad <[email protected]> wrote:
> This was cool, here is the thread dump. Still trying to make heads and
> tails out of it.
>
> On 7/5/2011 1:45 PM, Karl Wright wrote:
>>
>> Yes, get a thread dump of the agents process. On Windows, this is
>> CTRL-break in the process window, on linux kill -QUIT<pid>. You
>> should be able to find out what everything is waiting on. If you can,
>> send me the dump and I can interpret it for you.
>>
>> Karl
>>
>> On Tue, Jul 5, 2011 at 2:26 PM, Farzad Valad<[email protected]> wrote:
>>>
>>> So I'm crawling with the new code, and the crawl job seems to be frozen.
>>> CPU usage is near 0 for the agent process, nothing abnormal in the logs,
>>> and the status says running in the UI. My crawl set is 47,000 files, in
>>> the
>>> UI Documents=12122, Active=7144, and Processed=4978. According to the
>>> last
>>> log entry, it's been frozen over an hour now. The data resides on the
>>> local
>>> system, so I'm not dependent on the network for anything.
>>>
>>> Any ideas?
>>>
>
>
