Hi Guillaume, Sorry, I was already out of office when you sent the mail... I saw that you did a fix, and I'll check if it works for me. Thanks!
The problem first occurred in one of my own test cases, but then I reproduced it in the SecuredBroker test case by instantiating a Logger there right before the call to the JBIContainer constructor and observing the log level of its parent, which switched from ALL to ERROR. Ciao, Philipp Rossmanith > -----Mensaje original----- > De: Guillaume Nodet (JIRA) [mailto:[EMAIL PROTECTED] > Enviado el: viernes, 16 de febrero de 2007 19:48 > Para: servicemix-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 commented on SM-846: > ------------------------------------ > > Philip, > Is the IdGenerator the only issue ? I still don't understand why / how > 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://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. This e-mail may contain confidential or privileged information. Any unauthorised copying, use or distribution of this information is strictly prohibited.
