-dev@geronimo.apache.org
Asunto: [jira] Commented: (SM-846) Call to default constructor
ofJBIContainer changes log4j log level
[ https://issues.apache.org/activemq/browse/SM-
846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel#action_38541 ]
Guillaume Nodet
servicemix
could change the log4j level ...
What's the way to reproduce the problem ?
Call to default constructor of JBIContainer changes log4j log level
---
Key: SM-846
URL: https
Nodet
URL: http://svn.apache.org/viewvc?view=revrev=508541
URL: http://svn.apache.org/viewvc?view=revrev=508544
Call to default constructor of JBIContainer changes log4j log level
---
Key: SM-846
stop / start
the
service from jmx.
On 1/11/07, Thomas TERMIN [EMAIL PROTECTED] wrote:
What I want to do is to implement a MBean which configure the log4j
system periodicaly with a scheduler. But before I will look if there is
a log4j.xml or log4j.properties in the conf directory
, Thomas TERMIN [EMAIL PROTECTED] wrote:
What I want to do is to implement a MBean which configure the log4j
system periodicaly with a scheduler. But before I will look if
there is
a log4j.xml or log4j.properties in the conf directory if there is
nothing in it then I assume
log4j service for changing log levels at runtime
-
Key: SM-817
URL: https://issues.apache.org/activemq/browse/SM-817
Project: ServiceMix
Issue Type: New Feature
Components
the
service from jmx.
On 1/11/07, Thomas TERMIN [EMAIL PROTECTED] wrote:
What I want to do is to implement a MBean which configure the log4j
system periodicaly with a scheduler. But before I will look if there is
a log4j.xml or log4j.properties in the conf directory if there is
nothing in it then I
: Upgrade commons-logging to 1.1 and log4j to 1.2.13
Modified:
incubator/servicemix/trunk/pom.xml
Upgrade commons-logging to 1.1 and log4j to 1.2.13 to support the log4j TRACE
level
---
Key: SM-741
