[#JRA-14356] Investigate if log4j file for JBOSS 4.0.3SP1 is valid

JIRA

JRA-13032

Investigate if log4j file for JBOSS 4.0.3SP1 is valid

Created: 28/Jan/08 05:54 PM Updated: 29/Jan/08 09:54 PM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Participants:	Andrew Lui [Atlassian] and Bogdan Dziedzic [Atlassian]
Since last comment:	24 weeks, 5 days ago
Resolution Date:	29/Jan/08 09:54 PM
Labels:

Description

« Hide

'We should let the users know that JBOSS 4.0.3SP1 is shipped with its own log4j and it doesn't like the JIRA's one.'

Bogdan, can you get the JIRA devs to investigate? I can document any impacts to the users once it has been resolved.

Thanks!
Andrew

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Bogdan Dziedzic [Atlassian] - 28/Jan/08 10:25 PM

Hmmm..... I don't think there is anything that should be done with this issue. The only thing that can be improved is to change:

Note: in JBoss 4.0.2-4.0.5 you can expect to see one occurrence of a "Could not create an Appender" error, which is harmless - see JRA-6823. This is fixed in JBoss 4.2+.

to mention this issue too.

Basically, if you follow the docs and apply the workaround from ~~JRA-6823~~ for JBOSS 4.0.x, it will not return log errors related to log4j.

15:04:59,527 INFO  [STDOUT] log4j:ERROR A "org.jboss.logging.util.OnlyOnceErrorHandler" object is not assignable to a "org.apache.log4j.spi.ErrorHandler" variable.
15:04:59,528 INFO  [STDOUT] log4j:ERROR The class "org.apache.log4j.spi.ErrorHandler" was loaded by 
15:04:59,528 INFO  [STDOUT] log4j:ERROR [WebappClassLoader
  delegate: false
  repositories:
    /WEB-INF/classes/
----------> Parent Classloader:
java.net.FactoryURLClassLoader@16c14c0
] whereas object of type 
15:04:59,528 INFO  [STDOUT] log4j:ERROR "org.jboss.logging.util.OnlyOnceErrorHandler" was loaded by [org.jboss.system.server.NoAnnotationURLClassLoader@127734f].
15:04:59,603 INFO  [STDOUT] log4j:ERROR Could not create an Appender. Reported error follows.
15:04:59,604 INFO  [STDOUT] java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender cannot be cast to org.apache.log4j.Appender
15:04:59,604 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:165)
15:04:59,604 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:140)
15:04:59,605 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:153)
15:04:59,605 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:415)
15:04:59,605 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:384)
15:04:59,605 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:790)
15:04:59,605 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:673)

Peter's workaround from the above mentioned issue seems to be the solution to this issue.

Funny enough, the workaround in my case didn't its original purpose - fixing the following:

15:16:51,905 INFO  [STDOUT] 15:16:51,905 INFO  [NoModule] [FlexibleProperties.load]: Couldn't find the URL: file:/home/bdziedzic/apps/jboss-4.0.3SP1/server/default/tmp/deploy/tmp7329jira.war/debug
15:16:51,924 INFO  [STDOUT] 15:16:51,907 INFO  [NoModule] 
java.io.FileNotFoundException: /home/bdziedzic/apps/jboss-4.0.3SP1/server/default/tmp/deploy/tmp7329jira.war/debug (Is a directory)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(FileInputStream.java:106)
        at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:93)
        at java.net.URL.openStream(URL.java:1009)
        at org.ofbiz.core.util.FlexibleProperties.load(FlexibleProperties.java:141)
        at org.ofbiz.core.util.FlexibleProperties.init(FlexibleProperties.java:97)

Cheers,
Bogi

[ Show » ]

Bogdan Dziedzic [Atlassian] - 28/Jan/08 10:25 PM Hmmm..... I don't think there is anything that should be done with this issue. The only thing that can be improved is to change:

Note: in JBoss 4.0.2-4.0.5 you can expect to see one occurrence of a "Could not create an Appender" error, which is harmless - see JRA-6823. This is fixed in JBoss 4.2+.

to mention this issue too. Basically, if you follow the docs and apply the workaround from ~~JRA-6823~~ for JBOSS 4.0.x, it will not return log errors related to log4j.

15:04:59,527 INFO  [STDOUT] log4j:ERROR A "org.jboss.logging.util.OnlyOnceErrorHandler" object is not assignable to a "org.apache.log4j.spi.ErrorHandler" variable.
15:04:59,528 INFO  [STDOUT] log4j:ERROR The class "org.apache.log4j.spi.ErrorHandler" was loaded by 
15:04:59,528 INFO  [STDOUT] log4j:ERROR [WebappClassLoader
  delegate: false
  repositories:
    /WEB-INF/classes/
----------> Parent Classloader:
java.net.FactoryURLClassLoader@16c14c0
] whereas object of type 
15:04:59,528 INFO  [STDOUT] log4j:ERROR "org.jboss.logging.util.OnlyOnceErrorHandler" was loaded by [org.jboss.system.server.NoAnnotationURLClassLoader@127734f].
15:04:59,603 INFO  [STDOUT] log4j:ERROR Could not create an Appender. Reported error follows.
15:04:59,604 INFO  [STDOUT] java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender cannot be cast to org.apache.log4j.Appender
15:04:59,604 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:165)
15:04:59,604 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:140)
15:04:59,605 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:153)
15:04:59,605 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:415)
15:04:59,605 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:384)
15:04:59,605 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:790)
15:04:59,605 INFO  [STDOUT]     at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:673)

Peter's workaround from the above mentioned issue seems to be the solution to this issue. Funny enough, the workaround in my case didn't its original purpose

- fixing the following:

15:16:51,905 INFO  [STDOUT] 15:16:51,905 INFO  [NoModule] [FlexibleProperties.load]: Couldn't find the URL: file:/home/bdziedzic/apps/jboss-4.0.3SP1/server/default/tmp/deploy/tmp7329jira.war/debug
15:16:51,924 INFO  [STDOUT] 15:16:51,907 INFO  [NoModule] 
java.io.FileNotFoundException: /home/bdziedzic/apps/jboss-4.0.3SP1/server/default/tmp/deploy/tmp7329jira.war/debug (Is a directory)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(FileInputStream.java:106)
        at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:93)
        at java.net.URL.openStream(URL.java:1009)
        at org.ofbiz.core.util.FlexibleProperties.load(FlexibleProperties.java:141)
        at org.ofbiz.core.util.FlexibleProperties.init(FlexibleProperties.java:97)

Cheers, Bogi