Guys, Thanks everyone who helped or tried to help me out with this issue. After talking with a buddy of mine who uses solr, he said that XPath exception seemed familiar. It turns out that right at the bottom of the Solr Wiki install page is a troubleshooting section with one entry... and it was regarding XPath. tomcat did not have xalan in its class path and the easiest way to fix that was to create a symlink to the file in /usr/share/tomcat/shared/lib directory.
my version of xalan was located under /usr/share/java. for future reference, have anyone complaining about this same issue (XPath etc) go to this page: http://wiki.apache.org/solr/SolrTomcat#head-7fe06bf7aac41f6307f0290a2150b365227e1074 and at the bottom they will get the same instructions. Guys, again... thanks so much! --Aaron On Wed, Aug 26, 2009 at 8:47 PM, Fuad Efendi<f...@efendi.ca> wrote: > Looks like you totally ignored my previous post... > > > > >> Who is vendor of this "openjdk-1.6.0.0"? Who is vendor of JVM which this > JDK >> runs on? >>... such installs for Java are totally mess, you > may have incompatible Servlet API loaded by bootstrap classloader before > Tomcat classes > > > > > First of all, please, try to install standard Java from SUN on your > development box, and run some samples... > > > > > > !>This is due to your tomcat instance not having the xalan jar file in > !>the classpath > > > P.S. > Don't rely on CentOS 'approved' Java libraries. > > > >
