Applying a new pax-logging profile to a child container breaks the logging of the child container

Solution Verified - Updated -

Issue

I would like to change existing file-based appender's logging pattern. To do this I create a new profile and apply it to the container. I'm trying this on a clean fabric container, as follows:

 fabric:create --clean
 fabric:container-create-child root test-container

 fabric:profile-create logging-config
 fabric:profile-edit --import-pid --pid org.ops4j.pax.logging logging-config
 fabric:profile-edit --pid org.ops4j.pax.logging/log4j.appender.out.layout.ConversionPattern="%d{ABSOLUTE} | %-5.5p | %-16.16t | %-32.32c{1} | %X{bundle.id} - %X{bundle.name} - %X{bundle.version} | ===hello=== %m%n" logging-config

 container-add-profile test-container logging-config

This appears to break the file-based logging for the test-container. The last line I see in karaf.log is:

'Updating configuration org.ops4j.pax.logging'

I've found that this still doesn't work even if I just create a profile with the default logging configuration:

 fabric:create --clean
 fabric:container-create-child root test-container
 fabric:profile-create logging-config
 fabric:profile-edit --import-pid --pid org.ops4j.pax.logging logging-config
 container-add-profile test-container logging-config

Environment

  • JBoss Fuse 6.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.