You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Sebastian Nagel (Jira)" <ji...@apache.org> on 2019/11/22 15:46:00 UTC

[jira] [Resolved] (NUTCH-2024) httpcore classpath jar conflict when invoking protocol-selenium

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

Sebastian Nagel resolved NUTCH-2024.
------------------------------------
    Resolution: Cannot Reproduce

Hi [~lewismc], closing this old issue for now. The selenium plugins have been upgraded in NUTCH-2676. Please test with the recent Nutch 1.16 and reopen if the problem persists. Thanks!

> httpcore classpath jar conflict when invoking protocol-selenium
> ---------------------------------------------------------------
>
>                 Key: NUTCH-2024
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2024
>             Project: Nutch
>          Issue Type: Bug
>          Components: plugin
>    Affects Versions: 1.10
>            Reporter: Lewis John McGibbney
>            Priority: Major
>
> I fear that there is a classpath issue right now with httpcore when protocol-selenium is invoked and used.
> The error I get is something similar to the following
> {code}
> Caused by: java.lang.NoSuchFieldError: INSTANCE
>     at org.apache.http.impl.io.DefaultHttpRequestWriterFactory.<init>(DefaultHttpRequestWriterFactory.java:52)
>     at org.apache.http.impl.io.DefaultHttpRequestWriterFactory.<init>(DefaultHttpRequestWriterFactory.java:56)
>     at org.apache.http.impl.io.DefaultHttpRequestWriterFactory.<clinit>(DefaultHttpRequestWriterFactory.java:46)
>     at org.apache.http.impl.conn.ManagedHttpClientConnectionFactory.<init>(ManagedHttpClientConnectionFactory.java:72)
>     at org.apache.http.impl.conn.ManagedHttpClientConnectionFactory.<init>(ManagedHttpClientConnectionFactory.java:84)
>     at org.apache.http.impl.conn.ManagedHttpClientConnectionFactory.<clinit>(ManagedHttpClientConnectionFactory.java:59)
>     at org.apache.http.impl.conn.PoolingHttpClientConnectionManager$InternalConnectionFactory.<init>(PoolingHttpClientConnectionManager.java:487)
>     at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:147)
>     at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:136)
>     at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:112)
>     at org.apache.http.impl.client.HttpClientBuilder.build(HttpClientBuilder.java:726)
> {code}
> I managed to workaround this by removing all httpcore dependencies which are older than httpcore-4.3.2.jar which is required by protocol-selenium.
> I need to look into a more appropriate fix... possibly an upgrade of the httpcore libraries which are peppered around everywhere.
> We will see.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)