Yes, you heard that correctly on a mainframe. I've had no trouble setting up Solr on Tomcat on a Linux box sitting on my desk, however as it's getting closer to time go to production and I need it on our "real" environment.
We've managed to get Solr installed and running without too much trouble (layout and set-up the solr home directory, create a WebSphere server instance, and deploy the war file.) This runs fine for the most part (I can query, I can update, etc.) However, things aren't working so well doing the initial loads. I keep getting "#500 Internal Server" error messages. We're using post.jar to manage this (about 5 million records in 12 XML files) - I know post.jar is not ideal, but it runs like a champ loading the not particularly powerful Linux box on my desk. We're going through the logs, but any general advice on running in this environment would be appreciated. Thanks -- View this message in context: http://lucene.472066.n3.nabble.com/Anyone-running-Solr-in-WebSphere-on-a-mainframe-tp4015417.html Sent from the Solr - User mailing list archive at Nabble.com.
