[
https://issues.apache.org/jira/browse/SOLR-14553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136816#comment-17136816
]
Jason Gerlowski commented on SOLR-14553:
----------------------------------------
Hey Jim, sorry you're having troubles. Unfortunately, we don't use our JIRA
here as a support portal - it's only for reproducible (or strongly suspected)
bugs in Solr itself.
The mailing list is the best place for you to get help. It's the right format,
and it's also got a much wider readership than the smaller set of people who
read the jira list. I looked for the mail thread you mentioned in your
description, but couldn't find it, though I found others you created for other
issues in your recent project. Please ping that thread again or start a new
one, and when you do, please include the full stack trace you get on the client
side. The stack you've posted above is missing the top few lines that mention
the name of the actual exception and its message. Also include all of the
"Caused By" sections, if there are any.
Best of luck!
> I get a stack trace when running Solrj when calling the query method of
> HttpSolrClient
> --------------------------------------------------------------------------------------
>
> Key: SOLR-14553
> URL: https://issues.apache.org/jira/browse/SOLR-14553
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: clients - java
> Affects Versions: 7.3.1
> Reporter: Jim Anderson
> Priority: Major
> Labels: HttpSolrClient, solrj
> Attachments: SolrRead.java, bugSteps.ods
>
>
> I started a thread last week about running solrj using Solr 8.5.1. My program
> was crashing. I was using it with Nutch 1.16. In the documentation, it was
> recommended that Nutch 1.17 be used with Solr 8.5.1. Nutch 1.17 is still a
> developer version and not released, so I have downloaded Solar 7.3.1 to use
> with Nutch 1.16.
> I have been able to build up a small index in Solr using Nutch and I can see
> the Solr core containing the index in the solr admin window.
> Next, I tried to query Solr using solrj, using an example I found at:
> https://lucene.apache.org/solr/guide/8_1/using-solrj.html#common-configuration-options
> I wrote my own version of the example and tried running it and I get the
> following
> stacktrace:
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:607)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:255
> )
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:244
> )
> at org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:194)
> at org.apache.solr.client.solrj.SolrClient.query(SolrClient.java:942)
> at bfs.solrRead.SolrRead.main(SolrRead.java:40)
>
> This problem occurs on a linux platform, and the output from 'uname -a' is:
> Linux roe 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64
> GNU/Linux
> I have logged my steps and can probably reproduce the problem, but it does
> take some time. Along the way I had some warnings and potential error
> messages (I too new to Solr to know if the messages were errors or not) so
> the crash could be due to bad data in the index.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
