Problem with jboss 6 native logging in Domain / Host cluster

[duneorbit]

Hi in my local host standalone.xml I have the following,

<size-rotating-file-handler name="perfMetricsAppender" autoflush="true">

                <formatter>

                    <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) correlationID[%X{correlationID}] userID[%X{userID}] threadID[%X{threadID}] serviceCall[%X{serviceCall}] %s%E%n"/>

                </formatter>

                <file relative-to="jboss.server.log.dir" path="performance.log"/>

                <rotate-size value="100000m"/>

                <max-backup-index value="30"/>

                <append value="true"/>

            </size-rotating-file-handler>

<logger category="PERF_METRICS_LOGGER" use-parent-handlers="false">

                <level name="INFO"/>

                <handlers>

                    <handler name="perfMetricsAppender"/>

                </handlers>

            </logger>

Which works as expected, jboss creates the looging.properties with the correct structure and logging behaves as expected.

When we take this to the Domain JBOSS box and update the domain.xml with the above to the correct profile, the Host server has the correct logging.properties created on startup, the log file performance.log gets created also, but nothing gets appended to the log file, its empty.

Is there something I have missed here in the cluster setup for logging.

[jamezp]

Double check the profile you're adding the configuration to and the profile you're launching.

--

James R. Perkins

[duneorbit]

Thanks for your reply James.

Yes this was one of the fiorst things I had verified by DEV OPS.

My bad, it turned to be an issue where I had a config locally that was different from the war in the upper envs.

JBOS-DEPLOYMENT-STRUCTURE.xml had an exclusion filter blocking log4j libraries from the classloader.

Problem solved,

Thanks,

John.