[
https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907559#comment-16907559
]
Karl Wright commented on CONNECTORS-1105:
-
Feel free to add the linting fix to the poms that
[
https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907557#comment-16907557
]
Markus Schuch commented on CONNECTORS-1105:
---
The javadoc generation fails due to linting
[
https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907540#comment-16907540
]
Markus Schuch commented on CONNECTORS-1105:
---
Nexus setup is ready. I am able to upload
How many worker threads do you have?
Even if each worker thread is constrained in memory, and they should be,
you can easily cause things to run out of memory by giving too many worker
threads. Another way to keep Tika's usage constrained would be to reduce
the number of Tika Extractor
Yes , I am using Tika Extractor. And the version used for manifold is 2.13.
Also I am using postgres as database.
I have 4 types of jobs
One is accessing/re crawling data from a public site. Other three are
accessing intranet site.
Out of which two are giving me correct output-without any error
I will need to know more. Do you have the tika extractor in your
pipeline? If so, what version of ManifoldCF are you using? Tika has had
bugs related to memory consumption in the past; the out of memory exception
may be coming from it and therefore a stack trace is critical to have.
Hi Karl,
Manifold CF logs hints out me an error like :
agents process ran out of memory - shutting down
java.lang.OutOfMemoryError: Java heap space
Also I have -Xms1024m ,-Xmx1024m memory allocated in
start-options.env.unix, start-options.env.win file.
Also Configuration:-
1) For Crawler server
The error occurs, I believe, as the result of basic connection problems,
e.g. the connection is getting rejected. You can find more information in
the simple history, and in the manifoldcf log.
I would like to know the underlying cause, since the connector should be
resilient against errors of
