We have some java code in a jar in custom that uses an SLF4J log to write some statements at info level.
These show up in the Mirth 2.2.3.6825 log and console as "error" level:
ERROR 2014-11-02 05:14:18,191 [5f54fc5e-a7e7-4c60-a4c9-c10d9145a668_source_connector.5f54fc5e-a7e7-4c60-a4c9-c10d9145a668.receiver.1] Server: 197594048 [5f54fc5e-a7e7-4c60-a4c9-c10d9145a668_source_connector.5f54fc5e-a7e7-4c60-a4c9-c10d9145a668.receiver.1] INFO org.ext.xml.parser.ParserWrapper - Begin getCanonicalXML
Is this normal for all logging generated within Java classes? I'd like the level to be info or debug so they can be squelched from the Mirth Administrator.
These show up in the Mirth 2.2.3.6825 log and console as "error" level:
ERROR 2014-11-02 05:14:18,191 [5f54fc5e-a7e7-4c60-a4c9-c10d9145a668_source_connector.5f54fc5e-a7e7-4c60-a4c9-c10d9145a668.receiver.1] Server: 197594048 [5f54fc5e-a7e7-4c60-a4c9-c10d9145a668_source_connector.5f54fc5e-a7e7-4c60-a4c9-c10d9145a668.receiver.1] INFO org.ext.xml.parser.ParserWrapper - Begin getCanonicalXML
Is this normal for all logging generated within Java classes? I'd like the level to be info or debug so they can be squelched from the Mirth Administrator.
log.info statements from Java class show up as errors in Mirth log?
0 commentaires:
Enregistrer un commentaire