rocks.xmpp.extensions.caps.EntityCapabilitiesManager logging

[Geoffrey Knauth]

rocks.xmpp.extensions.caps.EntityCapabilitiesManager is dumping WARNING messages to my console, like:

Jun 08, 2015 9:10:11 PM rocks.xmpp.extensions.caps.EntityCapabilitiesManager$7 run
WARNING: Failed to discover information for entity '[e-mail]/User' for node 'http://...'

I would really like to redirect these messages to a DailyRollingFileAppender I already have for my own log4j logging, but I haven't figured out the correct log4j.xml incantation to make that happen. Does anyone have any suggestions other than "read the log4j docs?" I've been doing that and tinkering with settings, but nothing has helped so far.

[Christian Schudt]

This has already been fixed: 8909101ff2288cfb9eec94f152b5d5a3ac0af7e4

As for the logging: I never did that, but there are many resources online: https://www.google.de/#q=jul+to+log4j

I am sure you find a way.

[Geoffrey Knauth]

Thanks for the response. I'm not looking for java.util.logging to log4j, I'm already using log4j and am trying to move your log4j messages from console to a logger I control.

[Christian Schudt]

I don't use log4j, but JUL. So I think what you need to do is "forward" the JUL logging to your log4j logging. To do this there are log4j Bridges and Adapters, like: http://www.slf4j.org/legacy.html#jul-to-slf4j http://stackoverflow.com/questions/869945/how-to-send-java-util-logging-to-log4j https://logging.apache.org/log4j/2.0/log4j-jul/index.html

Hope it helps.

[Geoffrey Knauth]

Sorry I didn't see your most recent message until today, but it was right on target. This is what I wrote on SO this morning:

It turns out Babbler was using java.util.logging. I upgraded my own logging from Log4J 1.2.17 to Log4J2 2.3, and then used the JUL bridge to capture and redirect the logging output from Babbler to Log4J2 RollingFile appender.

[Christian Schudt]

ok, nice, closing this then.