You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Kevin Risden (Jira)" <ji...@apache.org> on 2022/10/25 18:22:00 UTC

[jira] [Commented] (SOLR-16494) jetty 11 http client

    [ https://issues.apache.org/jira/browse/SOLR-16494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623972#comment-17623972 ] 

Kevin Risden commented on SOLR-16494:
-------------------------------------

The other thing I'll add here about a separate Jetty 11.x client - the way the Solr build system works today is to standardize dependencies across the project. This means its hard today to have different dependency versions in a single module separate - so not easy to just build a Jetty 11.x Solr client.

> jetty 11 http client
> --------------------
>
>                 Key: SOLR-16494
>                 URL: https://issues.apache.org/jira/browse/SOLR-16494
>             Project: Solr
>          Issue Type: Wish
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrJ
>    Affects Versions: 9.0
>            Reporter: Bernd Wahlen
>            Priority: Minor
>
> i tried to migrate one of our smaller projects to spring boot3 rc1 and the only issue was with solr. Solr uses jetty9 and spring boot3 provides jetty11, the method used in the solr Http2SolrClient was (re)moved in jetty11. Since solr9 already requires java11, it should be possible to update or build a seperate solrj or httpclient using jetty11 or factor out to pluggable http client with different implementations.
> btw: jetty9 is eol
> https://github.com/eclipse/jetty.project/releases/tag/jetty-9.4.48.v20220622
> {code:java}
> An attempt was made to call a method that does not exist. The attempt was made from the following location:
>     org.apache.solr.client.solrj.impl.Http2SolrClient.createHttpClient(Http2SolrClient.java:227)
> The following method did not exist:
>     'void org.eclipse.jetty.client.HttpClient.<init>(org.eclipse.jetty.client.HttpClientTransport, org.eclipse.jetty.util.ssl.SslContextFactory)'
> The calling method's class, org.apache.solr.client.solrj.impl.Http2SolrClient, was loaded from the following location:
>     jar:file:/projects/local/photoai/photomoderation-1.0.0.jar!/BOOT-INF/lib/solr-solrj-9.0.0.jar!/org/apache/solr/client/solrj/impl/Http2SolrClient.class
> The called method's class, org.eclipse.jetty.client.HttpClient, is available from the following locations:
>     jar:file:/projects/local/photoai/photomoderation-1.0.0.jar!/BOOT-INF/lib/jetty-client-11.0.12.jar!/org/eclipse/jetty/client/HttpClient.class
> The called method's class hierarchy was loaded from the following locations:
>     org.eclipse.jetty.client.HttpClient: jar:file:/projects/local/photoai/photomoderation-1.0.0.jar!/BOOT-INF/lib/jetty-client-11.0.12.jar!/
>     org.eclipse.jetty.util.component.ContainerLifeCycle: jar:file:/projects/local/photoai/photomoderation-1.0.0.jar!/BOOT-INF/lib/jetty-util-11.0.12.jar!/
>     org.eclipse.jetty.util.component.AbstractLifeCycle: jar:file:/projects/local/photoai/photomoderation-1.0.0.jar!/BOOT-INF/lib/jetty-util-11.0.12.jar!/
> Action:
> Correct the classpath of your application so that it contains compatible versions of the classes org.apache.solr.client.solrj.impl.Http2SolrClient and org.eclipse.jetty.client.HttpClient
>  (main)
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org