lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "SolrJBoss" by HossMan
Date Tue, 07 Jul 2009 18:32:21 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The following page has been changed by HossMan:
http://wiki.apache.org/solr/SolrJBoss

The comment on the change is:
TOC, header cleanup, new sub-sec with snmp link

------------------------------------------------------------------------------
- == Solr with JBoss ==
+ = Solr with JBoss =
   * Solr runs fine with [http://www.jboss.org/ JBoss], see the instructions in the generic
[wiki:SolrInstall Solr installation] page
   * The latest version of JBoss is recommended
  
+ [[TableOfContents()]]
+ 
- === Optional Configuration ===
+ = Optional Configuration =
- ==== URI Charset Config ====
+ == URI Charset Config ==
  If you are going to '''query''' Solr using international characters (>127) using HTTP-GET,
you must configure JBoss to conform to the URI standard by accepting percent-encoded UTF-8.
  
  Edit JBoss's ''server/default/deploy/jbossweb-tomcat55.sar/server.xml'' and add the following
attribute to the correct Connector element: URIEncoding="UTF-8". If you're using JBoss v4.0
or above, then the file is located at: server/default/deploy/jboss-web-deployer/server.xml
@@ -21, +23 @@

  
  This is only an issue when sending non-ascii characters in a query request... no configuration
is needed for Solr/Tomcat to return non-ascii chars in a response, or accept non-ascii chars
in an HTTP-POST body.
  
+ == SNMP Monitoring ==
+ 
+ For more information on Using SNMP with Solr in JBoss please see SolrSnmp
+ 
- === Configuring Solr Home ===
+ = Configuring Solr Home =
  You can configure the Solr home directory globally via ''-Dsolr.solr.home'' in the file
''bin/run.bat''. But that is often not desired because you potentially want more than one
Solr installation deployed.
  
- ==== Solr Home via web.xml ====
+ == Solr Home via web.xml ==
  You can configure the Solr home directory to use per webapp in Solr's ''web.xml'' file.
Add following snippet to the web.xml:
  {{{
    <env-entry>
@@ -34, +40 @@

    </env-entry>
  }}}
  
- ==== Solr Home via properties-service.xml ====
+ == Solr Home via properties-service.xml ==
  You can also configure it (and other Solr variables, such as the Solr-data-dir) in properties-service.xml
like so:
  {{{
  <mbean code="org.jboss.varia.property.SystemPropertiesService" name="jboss:type=Service,name=SystemProperties">
@@ -45, +51 @@

  </mbean>
  }}}
  
- === JBoss Logging ===
+ = JBoss Logging =
  By default JBoss uses Log4J for its logging, while the default Solr installation uses the
[http://www.slf4j.org/manual.html#binding SLF4J binding] to log via the JDK1.4 logging system.
In order to get Solr to log via Log4J, you must replace the slf4j-jdk*.jar binding with the
slf4j-log4j*.jar binding. From that point on, logging can be configured via the log4j.xml
configuration file.
  
  For example, this can be used to silence all the INFO messages from Solr:
@@ -55, +61 @@

  </category>
  }}}
  
- === Troubleshooting ===
+ = Troubleshooting =
  If you encounter the error "statements are only available if source level is 5.0" then you
have to edit the file ''server/default/deploy/jbossweb-tomcat55.sar/conf/web.xml''.
  
  Comment in the block

Mime
View raw message