Call to default constructor of JBIContainer changes log4j log level
-------------------------------------------------------------------
Key: SM-846
URL: https://issues.apache.org/activemq/browse/SM-846
Project: ServiceMix
Issue Type: Bug
Affects Versions: 3.0
Environment: Windows XP Professional, java version 1.5.0_09, JUnit 4.1
Reporter: Philipp Rossmanith
Priority: Minor
A call to the default constructor of
org.apache.servicemix.jbi.container.JBIContainer sets the log4j log level to
ERROR. See
http://www.nabble.com/Default-constructor-for-JBIContainer-changes-log-level--tf3235243s12049.html
Can be observed in org.apache.servicemix.jbi.security.SecuredBrokerTest, line
63:
jbi = new JBIContainer();
JBIContainer doesn't seem to use org.apache.log4j, but makes calls to
org.apache.commons.logging.Log and org.apache.commons.logging.LogFactory:
>>
private static final Log log = LogFactory.getLog(JBIContainer.class);
<<
... as well as to java.util.logging.Logger:
>>
public Logger getLogger(String suffix, String resourceBundleName) throws
MissingResourceException, JBIException
<<
commons-logging is configured in ServiceMix. Which in turns, starts log4j if
included in the classpath.
It seems that org.apache.servicemix.id.IdGenerator calls the java.util.logging
package. This is the only call afaik and it should be removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
