On 3/22/2016 10:25 AM, Bram Van Dam wrote: > On 22/03/16 15:16, Shawn Heisey wrote: >> This message is not coming from Solr. It's coming from Jetty. Solr >> uses Jetty, but uses it completely unchanged. > Ah you're right. Here's the offending code: > > https://github.com/eclipse/jetty.project/blob/ac24196b0d341534793308d585161381d5bca4ac/jetty-start/src/main/java/org/eclipse/jetty/start/Main.java#L446 > > Doesn't look like there's an immediate workaround. Darn.
After a discussion on the jetty-user list, I have learned that although the warning comes from Jetty, the reason it gets logged is actually a bug in Solr -- one we've already fixed for 6.0: https://issues.apache.org/jira/browse/SOLR-8145 The -XX:OnOutOfMemoryError option is being handed to Jetty (start.jar) instead of the JVM. Jetty doesn't know what to do with this option unless it's started with the --exec option, so it logs the warning and ignores the option. Apparently if Jetty is started with the --exec option, the process this creates will give this -XX option to the nested JVM. I asked about the --exec option, but from what I could learn, I don't think it makes sense for Solr. When I made the change outlined in the patch on SOLR-8145 to my bin/solr script, the warning disappeared. That was not the intended effect of the patch, but I'm glad to have the mystery solved. Thank you for mentioning the problem so we could track it down. Thanks, Shawn
