> 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.
You're welcome. And thanks f
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/blo
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-st
On 3/22/2016 6:57 AM, Bram Van Dam wrote:
> Hey folks,
>
> When I start 5.5.0 (on RHEL), the following entry is added to
> server/logs/solr-8983-console.log:
>
> WARNING: System properties and/or JVM args set. Consider using
> --dry-run or --exec
>
> I can't quite figure out what's causing this. A
