[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-2072) Remove references to jboss logging appenders (and levels) from log4j.xml files of testsuite

[jaikiran pai (JIRA)]

     [ https://jira.jboss.org/jira/browse/EJBTHREE-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai resolved EJBTHREE-2072.
------------------------------------

    Resolution: Done


Done in r103625.

> Remove references to jboss logging appenders (and levels) from log4j.xml files of testsuite
> -------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-2072
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2072
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: testsuite
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>
> With the upgrade to 3.0.0.Beta2 of jboss-logging in AS trunk, we have started seeing:
> [junit] log4j:ERROR Could not create level [TRACE]. Reported error follows.
>     [junit] java.lang.ClassNotFoundException: org.jboss.logging.XLevel
>     [junit] 	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
>     [junit] 	at java.security.AccessController.doPrivileged(Native Method)
>     [junit] 	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>     [junit] 	at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
>     [junit] 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>     [junit] 	at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
>     [junit] 	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
>     [junit] 	at java.lang.Class.forName0(Native Method)
>     [junit] 	at java.lang.Class.forName(Class.java:169)
>     [junit] 	at org.apache.log4j.helpers.Loader.loadClass(Loader.java:178)
>     [junit] 	at org.apache.log4j.xml.DOMConfigurator.parseLevel(DOMConfigurator.java:519)
>     [junit] 	at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:438)
>     [junit] 	at org.apache.log4j.xml.DOMConfigurator.parseCategory(DOMConfigurator.java:345)
>     [junit] 	at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:827)
>     [junit] 	at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:712)
>     [junit] 	at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618)
>     [junit] 	at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:470)
>     [junit] 	at org.apache.log4j.LogManager.<clinit>(LogManager.java:122)
>     [junit] 	at java.lang.Class.forName0(Native Method)
>     [junit] 	at java.lang.Class.forName(Class.java:247)
>     [junit] 	at org.jboss.logging.LoggerProviders.findProvider(LoggerProviders.java:37)
>     [junit] 	at org.jboss.logging.LoggerProviders.<clinit>(LoggerProviders.java:28)
>     [junit] 	at org.jboss.logging.Logger.getI18nLogger(Logger.java:2124)
>     [junit] 	at org.jboss.logging.Logger.getLogger(Logger.java:2162)
>     [junit] 	at org.jboss.logging.Logger.getLogger(Logger.java:2187)
>     [junit] 	at org.jboss.test.AbstractTestCase.<clinit>(AbstractTestCase.java:50)
>     [junit] 	at java.lang.Class.forName0(Native Method)
>     [junit] 	at java.lang.Class.forName(Class.java:169)
>     [junit] 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:335)
>     [junit] 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911)
>     [junit] 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:768)
>     [junit] log4j:ERROR Could not create an Appender. Reported error follows.
>     [junit] java.lang.ClassNotFoundException: org.jboss.logging.appender.DailyRollingFileAppender
> These classes no longer exist in this version of jboss-logging. Effectively, there's no logging going on, on the client side.
> In any case, we don't need any JBoss specific appenders in that log4j.xml. Just falling back on log4j specific appenders and log4j specific appenders should be enough. Update the log4j.xml file accordingly.

-- 
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