Created and resolved CONNECTORS-1613.
Karl
On Mon, Jun 24, 2019 at 8:28 AM Karl Wright wrote:
> Hi Cihad,
>
> The unexpected job status error I cannot help you with; somehow your
> database has gotten corrupted. But I'm looking into the AIOOBE issue now.
>
> Karl
>
>
> On Mon, Jun 24, 2019
Hi Cihad,
The unexpected job status error I cannot help you with; somehow your
database has gotten corrupted. But I'm looking into the AIOOBE issue now.
Karl
On Mon, Jun 24, 2019 at 6:01 AM Cihad Guzel wrote:
> Hi Karl,
>
> I have 2 types error as follow:
>
> FATAL 2019-06-24T09:37:27,226
Hi Karl,
I have 2 types error as follow:
FATAL 2019-06-24T09:37:27,226 (Worker thread '3') - Error tossed: 7
java.lang.ArrayIndexOutOfBoundsException: 7
at
org.apache.manifoldcf.crawler.connectors.jdbc.JDBCConnector.applyMultiAttributeValues(JDBCConnector.java:2188)
~[?:?]
at
Hi Cihad,
Do you have a stack trace of the ArrayIndexOutOfBounds exception? It would
have to be taken from early when it started happening.
What the "Error: Unexpected job status encountered: 1" error means is that
the character that is stored in the job status field is not one that
ManifoldCF
Please do create a ticket with a patch. I'm extremely curious.
Depending on what you're proposing, I think a valid approach might need to
be to propose appropriate changes to the HttpComponents/HttpClient library.
Karl
On Thu, Jan 3, 2019 at 7:52 AM Erlend Garåsen
wrote:
>
> It works now
Thanks for looking harder into this!
The credential encoding in httpcomponents/httpclient has been problem free
as far as I have seen, so if you determine that that's the issue I am sure
it will be news to a lot of people. But by using the wire logging you
should be able to see the headers,
It wasn't necessary to deal with tools like tcpdump etc. Adding the
following to the logging.xml did the trick:
So now I know what's going on. Bad credentials:
DEBUG 2018-12-27T11:18:41,593 (Thread-1508) - http-outgoing-2 <<
"HTTP/1.1 401 Unauthorized[\r][\n]"
Strange, because connection
This is SSL. Did you add the server's cert to the web connector's
keystore? Or, if not, add a "trust all" rule?
Karl
On Thu, Dec 13, 2018 at 8:08 AM Erlend Garåsen
wrote:
>
> I'm able to run the jobs now, but I think the problem was related to
> Tomcat. The Solr and Web connectors were
I'm able to run the jobs now, but I think the problem was related to
Tomcat. The Solr and Web connectors were still available/showing up in
the web interface (MCF) *EVEN THOUGH* I deleted all tables in pgAdmin.
They disappeared after I restarted Tomcat.
Now I'm getting an error I reported back
On 12/12/2018 18:12, Karl Wright wrote:
> Did you import any data directly into new tables?
I used the ImportConfiguration command class and noticed some errors,
but it seems that the Solr and Web connectors have been successfully
imported.
> The schema has changed significantly from 1.7 until
Did you import any data directly into new tables?
The schema has changed significantly from 1.7 until now. I doubt very much
you could get away with an import of the old table data, and that could
well cause the effect you're seeing.
Karl
On Wed, Dec 12, 2018 at 11:12 AM Erlend Garåsen
wrote:
11 matches
Mail list logo
