[
https://issues.apache.org/jira/browse/SOLR-16494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623906#comment-17623906
]
Houston Putman edited comment on SOLR-16494 at 10/25/22 3:44 PM:
-----------------------------------------------------------------
We are currently working on an upgrade to Jetty 10, then I believe the next
step is to upgrade to Jetty 11 afterwards. I have linked the ticket for the
Jetty 11 upgrade, which links the ticket for the Jetty 10 upgrade.
Given our build system, it is unlikely we will be able to build separate solrj
jars for different Jetty versions.
was (Author: houston):
We are currently working on an upgrade to Jetty 10, then I believe the next
step is to upgrade to Jetty 11 afterwards.
> 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: [email protected]
For additional commands, e-mail: [email protected]