Sounds like Wicket and Solr are using the same port(s)...
If you start Wicket first then look at the Solr logs, you might
see some message about "port already in use" or some such.
If this is SolrCloud, there are also the ZooKeeper ports to
wonder about.
Best
Erick
On Mon, Jul 15, 2013 at 6:49 AM, Per Newgro <per.new...@gmx.ch> wrote:
> Hi,
>
> maybe someone here can help me with my solr-4.3.1 issue.
>
> I've successful deployed the solr.war on a tomcat7 instance.
> Starting the tomcat with only the solr.war deployed - works nicely.
> I can see the admin interface and logs are "clean".
>
> If i
> deploy my wicket-spring-data-solr based app (using the HttpSolrServer)
> after the solr app
> without restarting the tomcat
> => all is fine to.
>
> I've implemented a ping to see if server is up.
>
> <code>
> private void waitUntilSolrIsAvailable(int i) {
> if (i == 0) {
> logger.info("Check solr state...");
> }
> if (i > 5) {
> throw new RuntimeException("Solr is not avaliable
> after more than 25 secs. Going down now.");
> }
> if (i > 0) {
> try {
> logger.info("Wait for solr to get alive.");
> Thread.currentThread().wait(5000);
> } catch (InterruptedException e) {
> throw new RuntimeException(e);
> }
> }
> try {
> i++;
> SolrPingResponse r = solrServer.ping();
> if (r.getStatus() > 0) {
> waitUntilSolrIsAvailable(i);
> }
> logger.info("Solr is alive.");
> } catch (SolrServerException | IOException e) {
> throw new RuntimeException(e);
> }
> }
> </code>
>
> Here i can see log
> <log>
> 54295 [localhost-startStop-2] INFO org.apache.wicket.Application –
> [wicket.project] init: Wicket extensions initializer
> INFO - 2013-07-15 12:07:45.261;
> de.company.service.SolrServerInitializationService; Check solr state...
> 54505 [localhost-startStop-2] INFO
> de.company.service.SolrServerInitializationService – Check solr state...
> INFO - 2013-07-15 12:07:45.768; org.apache.solr.core.SolrCore; [collection1]
> webapp=/solr path=/admin/ping params={wt=javabin&version=2} hits=0 status=0
> QTime=20
> 55012 [http-bio-8080-exec-1] INFO org.apache.solr.core.SolrCore –
> [collection1] webapp=/solr path=/admin/ping params={wt=javabin&version=2}
> hits=0 status=0 QTime=20
> INFO - 2013-07-15 12:07:45.770; org.apache.solr.core.SolrCore; [collection1]
> webapp=/solr path=/admin/ping params={wt=javabin&version=2} status=0 QTime=22
> 55014 [http-bio-8080-exec-1] INFO org.apache.solr.core.SolrCore –
> [collection1] webapp=/solr path=/admin/ping params={wt=javabin&version=2}
> status=0 QTime=22
> INFO - 2013-07-15 12:07:45.854;
> de.company.service.SolrServerInitializationService; Solr is alive.
> 55098 [localhost-startStop-2] INFO
> de.company.service.SolrServerInitializationService – Solr is alive.
> </log>
>
> But if i
> restart the tomcat
> with both webapps (solr and wicket)
> the solr is not responding on the ping request.
>
> <log>
> INFO - 2013-07-15 12:02:27.634; org.apache.wicket.Application;
> [wicket.project] init: Wicket extensions initializer
> 11932 [localhost-startStop-1] INFO org.apache.wicket.Application –
> [wicket.project] init: Wicket extensions initializer
> INFO - 2013-07-15 12:02:27.787;
> de.company.service.SolrServerInitializationService; Check solr state...
> 12085 [localhost-startStop-1] INFO
> de.company.service.SolrServerInitializationService – Check solr state...
> </log>
>
> What could that be or how can i get infos where this is stopping?
>
> Thanks for your support
> Per
