Requests are generating the following for some, but not all, jars in the loadPaths directory in the application log:
that means you don’t get normal writelog() or cflog messages in it, right ?
Did you try going back to older versions on 5.3.x to see where it was introduced ?
If you set the log level for the application log to “Warn”, that will require changing any writeLog()/cflog calls to manually set the “type” argument. By default it’s “info” so it has to be something higher than that - warn, error, fatal.
“Change every log statment in every app” is a hell of a work around :)
Indeed! Thankfully, we had most of our error logging already going through a single function (for a single app) so the change wasn’t that bad for us.
An alternative is to edit the .jar to remove the OSGi meta data from the manifest : https://blog.osgi.org/2013/01/get-help-adding-osgi-metadata-to-your.html
This appears in some testing today to have no impact at all on using Java classes from ex-OSGi .jar either directly, or where there is a Java class dependency.