On 11/21/2018 1:40 AM, Jan Høydahl wrote:
It is super easy to change the log level of one particular class or
package
selectively, that's why we have log4j2.xml and also the Admin's
Logging levels menu.
The occational need to see all of the 150 jar files loaded on startup
should not be
solved by spewing out that for first-time users of Solr who really
just care for whether
the server started OK or not.
If somebody's got a config that loads 150 jars, I really do think that
having that info in the log would be useful information. That's a LOT
of jars, and it could be vital for troubleshooting a classloader problem
with one jar -- need to be able to tell whether it has been loaded or not.
It definitely shouldn't be default to have Jetty log its jar loading. I
just want to know how to make it do so, for situations that require very
in-depth study.
A user who's got 20 cores and each of them is loading the same 10 jars
with <lib> config ... IMHO that would ALSO be useful information to be
able to see in the default log. Without it, the user will probably have
absolutely no idea that they have 200 jar loads. (when that happens,
does Java realize that the classloader is loading the same jars and
eliminate duplicates in memory?)
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
