[
https://issues.apache.org/jira/browse/SOLR-16638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Deparvu updated SOLR-16638:
--------------------------------
Description:
Http2SolrClient can throw a number of RemoteSolrException using the
serverBaseUrl variable in the message. trouble is, this can be null, and is
null for the inter node requests).
One example I recently saw had `Error from server at null` [0]
There are places in the Http2SolrClient that look at the
'solrRequest.getBasePath()' and use that instead of the serverBaseUrl, I think
we could do the same for the exception message.
[0]
{noformat}
.... o.a.s.h.RequestHandlerBase
org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException: Error
from server at null: parsing error =>
org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException: Error
from server at null: parsing error
at
org.apache.solr.client.solrj.impl.Http2SolrClient.processErrorsAndResponse(Http2SolrClient.java:713)
org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException: Error
from server at null: parsing error
at
org.apache.solr.client.solrj.impl.Http2SolrClient.processErrorsAndResponse(Http2SolrClient.java:713)
{noformat}
was:
Http2SolrClient can throw a number of RemoteSolrException using the
serverBaseUrl variable in the message. trouble is, this can be null, and is
null for the inter node requests).
One example I recently saw had `Error from server at null` [0]
There are places in the Http2SolrClient that look at the
'solrRequest.getBasePath()' and use that instead of the serverBaseUrl, I think
we could do the same for the exception message.
[0]
{noformat}
org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException: Error
from server at null: parsing error =>
org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException: Error
from server at null: parsing error
at
org.apache.solr.client.solrj.impl.Http2SolrClient.processErrorsAndResponse(Http2SolrClient.java:713)
org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException: Error
from server at null: parsing error
at
org.apache.solr.client.solrj.impl.Http2SolrClient.processErrorsAndResponse(Http2SolrClient.java:713)
{noformat}
> Fix Http2SolrClient's exception message when serverBaseUrl is null
> ------------------------------------------------------------------
>
> Key: SOLR-16638
> URL: https://issues.apache.org/jira/browse/SOLR-16638
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.11.2
> Reporter: Alex Deparvu
> Priority: Minor
>
> Http2SolrClient can throw a number of RemoteSolrException using the
> serverBaseUrl variable in the message. trouble is, this can be null, and is
> null for the inter node requests).
> One example I recently saw had `Error from server at null` [0]
> There are places in the Http2SolrClient that look at the
> 'solrRequest.getBasePath()' and use that instead of the serverBaseUrl, I
> think we could do the same for the exception message.
> [0]
> {noformat}
> .... o.a.s.h.RequestHandlerBase
> org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException:
> Error from server at null: parsing error =>
> org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException:
> Error from server at null: parsing error
> at
> org.apache.solr.client.solrj.impl.Http2SolrClient.processErrorsAndResponse(Http2SolrClient.java:713)
> org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException:
> Error from server at null: parsing error
> at
> org.apache.solr.client.solrj.impl.Http2SolrClient.processErrorsAndResponse(Http2SolrClient.java:713)
> {noformat}
--
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
