[
https://issues.apache.org/jira/browse/SOLR-16728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17708471#comment-17708471
]
Houston Putman commented on SOLR-16728:
---------------------------------------
Ok from what I can ascertain (with very little info), I believe the error is
coming from either:
https://github.com/eclipse/jetty.project/blob/jetty-10.0.13/jetty-client/src/main/java/org/eclipse/jetty/client/dynamic/HttpClientTransportDynamic.java#L227
However solr does not use the HttpClientTransportDynamic class, so this is
unlikely.
The other option this stack-chain:
*
https://github.com/eclipse/jetty.project/blob/jetty-10.0.13/jetty-alpn/jetty-alpn-java-client/src/main/java/org/eclipse/jetty/alpn/java/client/JDK9ClientALPNProcessor.java#L50
*
https://github.com/eclipse/jetty.project/blob/jetty-10.0.13/jetty-alpn/jetty-alpn-client/src/main/java/org/eclipse/jetty/alpn/client/ALPNClientConnectionFactory.java#L100
*
https://github.com/eclipse/jetty.project/blob/jetty-10.0.13/jetty-http2/http2-http-client-transport/src/main/java/org/eclipse/jetty/http2/client/http/HttpClientTransportOverHTTP2.java#L165
*
Either way, this isn't giving me the information I need on why there is a
classpath issue. These starting classes now live in Jars (jetty-client and
jetty-http2) that live in /server/lib/ext now. So that makes sense that these
will get shared between the Jetty start classLoader and the Jetty webapp
classLoader. So maybe that's the issue, though I have no idea why the webapp is
using the jetty start classLoader at all.
> ClassCastException while creating new collection using JDK17
> ------------------------------------------------------------
>
> Key: SOLR-16728
> URL: https://issues.apache.org/jira/browse/SOLR-16728
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Server, SolrCloud
> Affects Versions: 9.2
> Reporter: Thomas Wöckinger
> Priority: Critical
>
> Creating a new collection using CollectionAPI results in following error:
> 2023-03-31T08:22:34.574888544Z 2023-03-31 08:22:34.573 WARN
> (httpShardExecutor-5-thread-3) [] o.e.j.i.ManagedSelector Could not accept
> java.nio.channels.SocketChannel[closed]: java.lang.ClassCastException: class
> org.eclipse.jetty.alpn.client.ALPNClientConnection cannot be cast to class
> org.eclipse.jetty.alpn.client.ALPNClientConnection
> (org.eclipse.jetty.alpn.client.ALPNClientConnection is in unnamed module of
> loader org.eclipse.jetty.start.Classpath$Loader @1f89ab83;
> org.eclipse.jetty.alpn.client.ALPNClientConnection is in unnamed module of
> loader org.eclipse.jetty.webapp.WebAppClassLoader @757f675c)
>
> Tested with:
> Red Hat, Inc. OpenJDK 64-Bit Server VM 17.0.6 17.0.6+10-LTS
> Solr started in cloude mode with one node and embedded zookeeper
> /opt/solr/bin/solr start -c -Dsolr.ssl.checkPeerName=false
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
