Am 05.07.2013 um 16:36 schrieb Shalin Shekhar Mangar: > Okay so just for the rest of the people who dig up this thread. You > had to put all the extra jar files required by typo3 into WEB-INF/lib > to make this work. Is that right?
Maybe this works aswell but I'd put it in a directory called "lib" within the core's folder. That way it is loaded automatically, too, says the example solrconfig.xml: https://svn.apache.org/repos/asf/lucene/dev/trunk/solr/example/solr/collection1/conf/solrconfig.xml Cheers, Michael Am 05.07.2013 um 16:36 schrieb Shalin Shekhar Mangar: > Okay so just for the rest of the people who dig up this thread. You > had to put all the extra jar files required by typo3 into WEB-INF/lib > to make this work. Is that right? > > On Fri, Jul 5, 2013 at 8:03 PM, Michael Bakonyi > <kont...@mb-neuemedien.de> wrote: >> Hi Shalin, >> >> Am 05.07.2013 um 16:23 schrieb Shalin Shekhar Mangar: >>> There are plenty of use-cases for having multiple cores. You may have >>> two different schemas for two different kind of documents. Perhaps you >>> are indexing content in multiple languages and you may want a core per >>> language. In SolrCloud, a node can have multiple cores to support more >>> than one shard on the same box. >> >> alright, so it depends on the use case. I guess for me the different use >> cases will be combinations of domain.tld and language. But for me this is >> far future I think. >> >>> The Solr war file has all the classes it needs to startup and run >>> (well except for some optional components like DataImportHandler etc) >>> and the SolrInfoMBean is most definitely present in the war file. >>> Enabling or disabling jmx has nothing to do with loading that class. >> >> This is what I guessed, too. But I'm neither know Java or Tomcat nor Solr so >> I tried everything I could. >> >>> It is very difficult to guess what's wrong with your setup this way. >>> Why don't you try using the example jetty? It works and is well >>> supported and optimized for Solr. >> >> Giovanni's guess was right, so this error disappeared luckily. >> >> Cheers, >> Michael >> >> >> >> >> >> >> Am 05.07.2013 um 16:23 schrieb Shalin Shekhar Mangar: >> >>> On Thu, Jul 4, 2013 at 4:32 PM, Michael Bakonyi >>> <kont...@mb-neuemedien.de> wrote: >>>> Hi everyone, >>>> >>>> I'm trying to get the CMS "TYPO3" connected with Solr 3.6.2. >>>> >>>> By now I followed the installation at >>>> http://wiki.apache.org/solr/SolrTomcat except that I didn't copy the >>>> .war-file into the $SOLR_HOME but referencing to it at a different >>>> location via Tomcat Context fragment file. >>>> >>>> Until then the Solr-Server works – I can reach the GUI via URL. >>>> >>>> To get Solr connected with the CMS I then created a new core-folder (btw. >>>> can anybody give me kind of a live example, when to use different cores? >>>> Until now I still don't really understand the concept of cores ..) by >>>> duplicating the example-folder in which I overwrote some files (especially >>>> solrconfig.xml) with files offered by the TYPO3-community. I also moved >>>> the file "solr.xml" one level up and edited it (added core-fragment and >>>> especially adjusted "instanceDir") to get a correct multicore-setup like >>>> in the example multicore-setup within the downloaded solr-tgz-package. >>> >>> There are plenty of use-cases for having multiple cores. You may have >>> two different schemas for two different kind of documents. Perhaps you >>> are indexing content in multiple languages and you may want a core per >>> language. In SolrCloud, a node can have multiple cores to support more >>> than one shard on the same box. >>> >>>> >>>> But now I get the Java-exception >>>> >>>> "java.lang.NoClassDefFoundError: org/apache/solr/core/SolrInfoMBean at >>>> java.lang.ClassLoader.defineClass1(Native Method)" >>>> >>>> In the Tomcat-log file it is said additionally: "Caused by: >>>> java.lang.ClassNotFoundException: org.apache.solr.core.SolrInfoMBean". >>>> >>>> My guess is, that within the new solrconfig.xml there are calls to classes >>>> which aren't included correctly. There are some libs, which are included >>>> at the top of this file but the paths of the references should be ok as I >>>> checked them via Bash: At http://wiki.apache.org/solr/SolrConfigXml it is >>>> said that the <lib dir= directory is relative to the instanceDir, so this >>>> is what I've checked. I also inserted absolute paths but this wasn't >>>> successful either. >>>> >>>> Can anybody give me a hint how to solve this problem? Would be great :) >>> >>> The Solr war file has all the classes it needs to startup and run >>> (well except for some optional components like DataImportHandler etc) >>> and the SolrInfoMBean is most definitely present in the war file. >>> Enabling or disabling jmx has nothing to do with loading that class. >>> It is very difficult to guess what's wrong with your setup this way. >>> Why don't you try using the example jetty? It works and is well >>> supported and optimized for Solr. >>> >>> >>> -- >>> Regards, >>> Shalin Shekhar Mangar. >> > > > > -- > Regards, > Shalin Shekhar Mangar.
