CF 9.0.1 Solr does not respect Java VM Path

Brentil, I would assert that if Solr is "trying" to use the runtime/jre to find classes then perhaps your last point is not correct:  maybe instead it IS honoring the classpath, but it's other than what you're seeing. Rather than rely on what you see as the textarea field of the Java and JVM page (for the classpath), look instead in the settings summary page to see what it shows to be the classpath.

As for your removing the CF JRE when you would add a new JDK, that's interesting. I'd not heard of people doing it. Of course, the fact you used ProcMon to prove that Solr looked there if its own JRE was removed may be how you proved that when you added a new JDK for CF, it too still looked in the old jre location. Did you prove that? I would be surprised, and it could suggest that people who added a new JDK may not have always been leveraging it alone. That would be a surprise. Let us know if you did prove that. Perhaps others would want to start removing it--though this Solr problem is certainly another challenge in considering that.

Will look forward to seeing how all this turns out.

/charlie

Thanks for the clarification on why you would remove it in the past.

As for the problem you're having with Solr, I'm just explaining that Java has a notion of a classpath, which is a list of directories through which the JVM will look when trying to load a class. If you look at what CF shows to be the classpath, then THAT is why it's looking where it is.

Does that help?

/charlie

Well, to be clear, I'm not an Adobe representative, so I can't do anything if you feel there is a bug. You'd want to report that in the CF bug tracking area instead: http://www.adobe.com/go/cf_bugs

As for why the JVM searches for classes in other than the jre.home, I can't explain that. Maybe someone else can. I would just say that as far as normal class loading goes, it works as we've observed: searching through the directories in the classpath to find a class when loaded, and it's done in the order that directories are listed, so that if a class is not found in one then it looks in the next.

I'd not be surprised that it would work the same for "application" classes as well as classes within the JRE itself.

/charlie

I'd like to add a followup to this thread from 3 years ago, in case anyone may find it in the future as I just did doing a search for something. Keith's last note had discussed how to modify the solr jvm configuration file (solr.lax in CF9) to point to a new JVM.

He had said the line to modify was that for lax.nl.currentvm but instead it's than lax.nl.current.vm. I clarify this as much for those who may be searching for references to it, so they may find this discussion.

Also, FWIW for future readers, in CF10+ the file is now instead called jetty.lax and is also located in a different directory: \[cf10]\cfusion\jetty, or [cf10]\[instancename]\jetty if you have created a new CF10 Enterprise instance.

Hope that's helpful.

Hi Leith,

You have surely found a solution that is bound to help someone else in future. Please mark your last post as the 'correct' answer.