Hi, it worked! The issue was originally on WAS 7, but has somehow regressed to WebSphere 8.5. Thanks.
On Thu, Feb 19, 2015 at 10:13 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > : Hi! Solr is starting up "dormant" for me, until a client wake it up with > a > : REST request, or I open admin UI, only then the remaining initializing > : happens. > : Is it something known? > > based on my recollection of the servlet spec, that sounds like a > bug/glitch/config option in your Servlet container... > > Googling "WebSphere init Filters on startup" turns up this IBM bug report > with noted fix versions... > http://www-01.ibm.com/support/docview.wss?uid=swg1PK86553 > > > : I can't see any load-on-startup in the web.xml, in Solr.war. > > The bulk of Solr exists as a "Filter". Filters are not permitted > by the servlet spec to specify "load-on-startup" value (only > Servlets can specify that, and the only Servlets in Solr are for > supporting legacy paths -- the load order doesn't matter for them) > > > : Running Solr 4.7.2 over WebSphere 8.5 > : > : App loading message as the server starts up: > : [2/*16*/15 12:17:19:956 GMT] 00000056 ApplicationMg A WSVR0221I: > : Application started: solr-4.7.2 > : [2/*16*/15 12:17:20:319 GMT] 00000001 WsServerImpl A WSVR0001I: > : Server serverSolr open for e-business > : The the next start up message in the log is on the next day once I enter > : Solr admin UI: > : [2/*17*/15 10:20:13:827 GMT] 00000098 SolrDispatchF I > : org.apache.solr.servlet.SolrDispatchFilter init SolrDispatchFilter.init() > : ... > : > > -Hoss > http://www.lucidworks.com/ >
