Yes, you need to use a different port for Solr.
As for the contextpath, I have no idea.
Best
Erick
On Tue, Jul 16, 2013 at 2:02 PM, Per Newgro wrote:
> Thanks Eric,
>
> i've configured both to use 8080 (For wicket this is standard :-)).
>
> Do i have to assign a different port to solr if i use b
Thanks Eric,
i've configured both to use 8080 (For wicket this is standard :-)).
Do i have to assign a different port to solr if i use both webapps in
the same container?
Btw. the contextpath for my wicket app is /*
Could that be a problem to?
Per
Am 15.07.2013 17:12, schrieb Erick Erickson:
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
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 (usin
