On 8/14/2013 5:16 AM, Roland Everaert wrote: > For the past months I have deplaoyed and used SOLR 4.3.0 on a JBOSS EAP 6.1 > using the standalone configuration. > > Now due to the addition of a new service, I have to start jboss with a > modified version of the standalone-full.xml configuration file, because the > service uses JavaEE 6. The only change concerns connection to a datasource > and interaction with active directory.
It's difficult for this list to support containers other than what actually comes with Solr 4.x, which is a stripped down (but otherwise unmodified) Jetty 8. Most of us have come to the realization that running with the jetty that's included in the example is the least painful way to proceed. Most of the rest are using Tomcat. Tomcat gets somewhat special treatment for two reasons: 1) It's very widespread. 2) It's a fellow Apache project, just as much open source and transparent as Solr itself. None of the error messages in the log you have shown us come from Solr. If that's the only logging info you have, there's nothing for us to go on. You'll need to get help from redhat or another jboss support avenue to narrow down the problem, and if you ultimately do find Solr error messages, then come back here for help resolving them. I can say one general thing that might be helpful: The standard .war file for Solr 4.3.0 and later does not contain logging jars. A proper slf4j logging setup is critically important for Solr operation, and particularly problematic with containers other than the included jetty. It's possible that by adding the other application, there is now a problem with logging jars, likely a version conflict. Problems with logging are, by their very nature, difficult to detect. http://wiki.apache.org/solr/SolrLogging#Solr_4.3_and_above If you want to use a logging mechanism other than log4j, the note about intercept jars is sometimes of particular relevance. Thanks, Shawn
