Because the current release of our software is based on solr 1.3, and we scheduled the migration to JBoss 5 before the migration to solr 1.4.
It's a concurrency problem! L.M. On 2 February 2010 16:05, Erik Hatcher <erik.hatc...@gmail.com> wrote: > Out of curiosity, why are you deploying Solr 1.3 rather than Solr 1.4? > > Sorry, but I don't know about the JBoss issues first hand myself. > > Erik > > > On Feb 2, 2010, at 9:20 AM, Luca Molteni wrote: > >> Hello list, >> >> I'm having some problem deploying solr to JBoss 5. >> >> The problem is with environment variables: >> >> Following this page of the wiki: http://wiki.apache.org/solr/SolrJBoss >> >> I've added to the web.xml of WEB-INF of solr >> >> <env-entry> >> <env-entry-name>solr/home</env-entry-name> >> <env-entry-type>java.lang.String</env-entry-type> >> <env-entry-value>${solr.home.myhome}</env-entry-value> >> </env-entry> >> >> Since I'm using lots of instances of solr in the same container. >> >> This variable should be expanded by jboss itself in a path using >> properties-services.xml: >> >> <attribute name="Properties"> >> solr.home.myhome=C:/mypath/solr >> </attribute> >> >> Unfortunately, during deployment of the solr application, it gives me >> this error: >> >> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse >> source: The content of element type "env-entry" must match >> "(description?,env-entry-name,env-entry-value?,env-entry-type)". @ >> >> vfsfile:/C:/pathtojboss/server/solrrepo/deploy/Solrrepo/solr-mysolr.war/WEB-INF/web.xml[146,14] >> at >> org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) >> >> ... 33 more >> Caused by: org.xml.sax.SAXException: The content of element type >> "env-entry" must match >> "(description?,env-entry-name,env-entry-value?,env-entry-type)". @ >> >> vfsfile:/C:/pathtojboss/server/solrrepo/deploy/Solrrepo/solr-mysolr.war/WEB-INF/web.xml[146,14] >> at >> org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:426) >> >> >> Notice that the same .war and properties-services.xml works flawlessly >> in JBoss 4.2.3 >> >> Any ideas? >> >> Thank you very much. >> >> L.M. > >
