[
https://issues.apache.org/jira/browse/SOLR-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher updated SOLR-3591:
-------------------------------
Attachment: screenshot-1.jpg
Actual startup error was due to (experimenting with failure modes of SOLR-1725):
{code}
Jul 2, 2012 6:29:57 PM org.apache.solr.common.SolrException log
SEVERE: null:org.apache.solr.common.SolrException: Unable to initialize
scripts: No ScriptEngine found by file extension: update_processor.rb --
supported extensions: scpt, applescript, app, js
at org.apache.solr.core.SolrCore.<init>(SolrCore.java:664)
at org.apache.solr.core.SolrCore.<init>(SolrCore.java:548)
{code}
by having this in my configuration:
{code}
<updateRequestProcessorChain name="script">
<processor class="solr.StatelessScriptUpdateProcessorFactory">
<str name="script">update_processor.rb</str>
</processor>
<processor class="solr.RunUpdateProcessorFactory" />
</updateRequestProcessorChain>
{code}
Without jruby being present.
> Startup error not reflected in Solr web view
> --------------------------------------------
>
> Key: SOLR-3591
> URL: https://issues.apache.org/jira/browse/SOLR-3591
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.0-ALPHA
> Reporter: Erik Hatcher
> Priority: Blocker
> Fix For: 4.0
>
> Attachments: screenshot-1.jpg
>
>
> When Solr has a fatal startup error, it used to be reflected in general
> responses from Solr. With the new UI, it's relegated to only the logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
