You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2010/02/10 15:59:27 UTC
[jira] Created: (FELIX-2065) BootstrapLogManager doesn't load
etc/org.ops4j.pax.logging.cfg file
BootstrapLogManager doesn't load etc/org.ops4j.pax.logging.cfg file
-------------------------------------------------------------------
Key: FELIX-2065
URL: https://issues.apache.org/jira/browse/FELIX-2065
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.2.0
Environment: Linux Debian
JVM Sun 1.5.0
Reporter: Jean-Baptiste Onofré
The BootstrapLogManager doesn't load the org.ops4j.pax.logging.cfg file from the correct location.
By consequence, the log4j.appender.out.file property is set to ${karaf.base}/data/log/karaf.log. If the user setup a different log file name in the appender - for instance as follows:
# File appender
log4j.appender.out=org.apache.log4j.FileAppender
log4j.appender.out.layout=org.apache.log4j.PatternLayout
log4j.appender.out.layout.ConversionPattern=%d{ABSOLUTE} | %-5.5p | %-16.16t | %-32.32c{1} | %-32.32C %4L | %m%n
log4j.appender.out.file=${karaf.base}/data/log/my.log
log4j.appender.out.append=true
he will set:
my.log
karaf.log
in the ${karaf.base}/data/log directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2065) BootstrapLogManager doesn't load
etc/org.ops4j.pax.logging.cfg file
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated FELIX-2065:
----------------------------------------
Attachment: FELIX-2065.patch
> BootstrapLogManager doesn't load etc/org.ops4j.pax.logging.cfg file
> -------------------------------------------------------------------
>
> Key: FELIX-2065
> URL: https://issues.apache.org/jira/browse/FELIX-2065
> Project: Felix
> Issue Type: Bug
> Components: Karaf
> Affects Versions: karaf-1.2.0
> Environment: Linux Debian
> JVM Sun 1.5.0
> Reporter: Jean-Baptiste Onofré
> Attachments: FELIX-2065.patch
>
>
> The BootstrapLogManager doesn't load the org.ops4j.pax.logging.cfg file from the correct location.
> By consequence, the log4j.appender.out.file property is set to ${karaf.base}/data/log/karaf.log. If the user setup a different log file name in the appender - for instance as follows:
> # File appender
> log4j.appender.out=org.apache.log4j.FileAppender
> log4j.appender.out.layout=org.apache.log4j.PatternLayout
> log4j.appender.out.layout.ConversionPattern=%d{ABSOLUTE} | %-5.5p | %-16.16t | %-32.32c{1} | %-32.32C %4L | %m%n
> log4j.appender.out.file=${karaf.base}/data/log/my.log
> log4j.appender.out.append=true
> he will set:
> my.log
> karaf.log
> in the ${karaf.base}/data/log directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-2065) BootstrapLogManager doesn't load
etc/org.ops4j.pax.logging.cfg file
Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Custine reassigned FELIX-2065:
------------------------------------
Assignee: Chris Custine
> BootstrapLogManager doesn't load etc/org.ops4j.pax.logging.cfg file
> -------------------------------------------------------------------
>
> Key: FELIX-2065
> URL: https://issues.apache.org/jira/browse/FELIX-2065
> Project: Felix
> Issue Type: Bug
> Components: Karaf
> Affects Versions: karaf-1.2.0
> Environment: Linux Debian
> JVM Sun 1.5.0
> Reporter: Jean-Baptiste Onofré
> Assignee: Chris Custine
> Attachments: FELIX-2065.patch
>
>
> The BootstrapLogManager doesn't load the org.ops4j.pax.logging.cfg file from the correct location.
> By consequence, the log4j.appender.out.file property is set to ${karaf.base}/data/log/karaf.log. If the user setup a different log file name in the appender - for instance as follows:
> # File appender
> log4j.appender.out=org.apache.log4j.FileAppender
> log4j.appender.out.layout=org.apache.log4j.PatternLayout
> log4j.appender.out.layout.ConversionPattern=%d{ABSOLUTE} | %-5.5p | %-16.16t | %-32.32c{1} | %-32.32C %4L | %m%n
> log4j.appender.out.file=${karaf.base}/data/log/my.log
> log4j.appender.out.append=true
> he will set:
> my.log
> karaf.log
> in the ${karaf.base}/data/log directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2065) BootstrapLogManager doesn't load
etc/org.ops4j.pax.logging.cfg file
Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Custine resolved FELIX-2065.
----------------------------------
Resolution: Fixed
Fix Version/s: karaf-1.4.0
> BootstrapLogManager doesn't load etc/org.ops4j.pax.logging.cfg file
> -------------------------------------------------------------------
>
> Key: FELIX-2065
> URL: https://issues.apache.org/jira/browse/FELIX-2065
> Project: Felix
> Issue Type: Bug
> Components: Karaf
> Affects Versions: karaf-1.2.0
> Environment: Linux Debian
> JVM Sun 1.5.0
> Reporter: Jean-Baptiste Onofré
> Assignee: Chris Custine
> Fix For: karaf-1.4.0
>
> Attachments: FELIX-2065.patch
>
>
> The BootstrapLogManager doesn't load the org.ops4j.pax.logging.cfg file from the correct location.
> By consequence, the log4j.appender.out.file property is set to ${karaf.base}/data/log/karaf.log. If the user setup a different log file name in the appender - for instance as follows:
> # File appender
> log4j.appender.out=org.apache.log4j.FileAppender
> log4j.appender.out.layout=org.apache.log4j.PatternLayout
> log4j.appender.out.layout.ConversionPattern=%d{ABSOLUTE} | %-5.5p | %-16.16t | %-32.32c{1} | %-32.32C %4L | %m%n
> log4j.appender.out.file=${karaf.base}/data/log/my.log
> log4j.appender.out.append=true
> he will set:
> my.log
> karaf.log
> in the ${karaf.base}/data/log directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2065) BootstrapLogManager doesn't load
etc/org.ops4j.pax.logging.cfg file
Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832073#action_12832073 ]
Chris Custine commented on FELIX-2065:
--------------------------------------
Patch applied on behalf of Jean-Baptiste Onofré.
> BootstrapLogManager doesn't load etc/org.ops4j.pax.logging.cfg file
> -------------------------------------------------------------------
>
> Key: FELIX-2065
> URL: https://issues.apache.org/jira/browse/FELIX-2065
> Project: Felix
> Issue Type: Bug
> Components: Karaf
> Affects Versions: karaf-1.2.0
> Environment: Linux Debian
> JVM Sun 1.5.0
> Reporter: Jean-Baptiste Onofré
> Assignee: Chris Custine
> Fix For: karaf-1.4.0
>
> Attachments: FELIX-2065.patch
>
>
> The BootstrapLogManager doesn't load the org.ops4j.pax.logging.cfg file from the correct location.
> By consequence, the log4j.appender.out.file property is set to ${karaf.base}/data/log/karaf.log. If the user setup a different log file name in the appender - for instance as follows:
> # File appender
> log4j.appender.out=org.apache.log4j.FileAppender
> log4j.appender.out.layout=org.apache.log4j.PatternLayout
> log4j.appender.out.layout.ConversionPattern=%d{ABSOLUTE} | %-5.5p | %-16.16t | %-32.32c{1} | %-32.32C %4L | %m%n
> log4j.appender.out.file=${karaf.base}/data/log/my.log
> log4j.appender.out.append=true
> he will set:
> my.log
> karaf.log
> in the ${karaf.base}/data/log directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.