How to enable DEBUG logging for ModeShape running in Wildfly

[dalbani]

Hello,

I'm trying to track some kind of bug / issue in the Infinispan binary store implementation in ModeShape.

But I couldn't find a way to enable logging at DEBUG level, so I can see what is the activity of the InfinispanBinaryStore class.

In the standalone XML configuration file, I've added everything I could think of:

<logger category="org.modeshape">
    <level name="DEBUG"/>
</logger>
<logger category="org.modeshape.jcr">
    <level name="DEBUG"/>
</logger>
<logger category="org.modeshape.jcr.value">
    <level name="DEBUG"/>
</logger>
<logger category="org.modeshape.jcr.value.binary">
    <level name="DEBUG"/>
</logger>
<logger category="org.modeshape.jcr.value.binary.AbstractBinaryStore">
    <level name="DEBUG"/>
</logger>
<logger category="org.modeshape.jcr.value.binary.infinispan">
    <level name="DEBUG"/>
</logger>
<logger category="org.modeshape.jcr.value.binary.infinispan.InfinispanBinaryStore">
    <level name="DEBUG"/>
</logger>

I now indeed have a more verbose logging in log/server.log but there isn't the InfinispanBinaryStore calls I'm interested in.

I'm running Wildfly 8.1 by the way.

Thanks.

[hchiorean]

You need to also change the default logging level of the appropriate handler (the defaults are "INFO"). So, for example, if you wanted to log to console you'd change the following:

<console-handler name="CONSOLE">

   <level name="DEBUG"/>

If you're using 4.0.0.Beta2 with DEBUG logging enabled and using binary values, you'll also probably run into: [MODE-2302] The FileSystemBinaryStore incorrectly handles the binary unused / used cycle - JBoss Issue Tracker

This is something that will be fixed in the next release.

[dalbani]

Strangely enough, I had set this CONSOLE parameter to DEBUG.

I restarted Wildfly this morning without having touched the configuration file... and I got DEBUG messages indeed.

And of course the original issue I had didn't materialize anymore.

Was it some kind of LevelDB-related "stray process"?

Anyway, I'll see if that pops up again.