[ https://jira.jboss.org/jira/browse/JBAS-6580?page=com.atlassian.jira.plug... ] Stan Silvert commented on JBAS-6580: ------------------------------------ I already know the cause. It's the new logging stuff. The problem will go away if you set the old logging manager -Djava.util.logging.manager=org.jboss.logging.jdk.JDKLogManager This test should pass again when we decide how to solve JBCTS-903. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6580?page=com.atlassian.jira.plug... ] David Lloyd commented on JBAS-6580: ----------------------------------- There's already a fix committed; just need Dimitris to release a new jboss-logging-log4j so I can release a new jboss-logbridge and commit it into JBAS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6580?page=com.atlassian.jira.plug... ] Dimitris Andreadis commented on JBAS-6580: ------------------------------------------ We have applied the latest logging libs that enable the setting of JDK levels in jboss-log4j.xml org.jboss.logging:org.jboss.logging:2.0.6.GA org.jboss.logbridge:jboss-logbridge:1.0.0.CR3 org.jboss.logmanager:jboss-logmanager:1.0.0.CR2 The default level for JSF is INFO: ... <!-- Set the logging level of the JSF implementation that uses | java.util.logging. The jdk logging levels can be controlled | through the org.jboss.logging.log4j.JDKLevel class that | in addition to the standard log4j levels it adds support for | SEVERE, WARNING, CONFIG, FINE, FINER, FINEST --> <category name="javax.enterprise.resource.webcontainer.jsf"> <priority value="INFO" class="org.jboss.logging.log4j.JDKLevel"/> </category> Also I've disabled JBossJSFConfigurationListener's own log bridging: // JBAS-6475, with the update to jboss-log-bridge this is not need // // If the pluginClass is not set, assume Log4J // if (System.getProperty("org.jboss.logging.Logger.pluginClass") == null) // { // setLog4J(); // setLog4JForFacelets(); // } And enabled the dynamic setting of JDK log levels through Log4jService.java. For those levels to be propagated to the JUL side you need to tell the service to reconfigure() itself. Now, with all those changes in place there shouldn't be any need for JSF to bridge logging. However, I cannot get JBCTS-903 to work, and I can verify that the log level for javax.enterprise.resource.webcontainer.jsf is set to INFO. The testsuite JSFIntegrationUnitTestCase needs also to be changed. The Log4jService can now understand the setting of JDK log levels (again you need to reconfigure() it). Assign back to Stan to look at. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6580?page=com.atlassian.jira.plug... ] Jason T. Greene updated JBAS-6580: ---------------------------------- Fix Version/s: JBossAS-5.1.0.CR1 (was: JBossAS-5.1.0.Beta1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6580?page=com.atlassian.jira.plug... ] Stan Silvert updated JBAS-6580: ------------------------------- Fix Version/s: JBossAS-6.0.0.Alpha1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6580?page=com.atlassian.jira.plug... ] Brian Stansberry resolved JBAS-6580. ------------------------------------ Fix Version/s: (was: JBossAS-6.0.0.M3) Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira