Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: MB-805
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dejan Bosanac
Reporter: Susan Javurek
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
FUSE Message Broker

Web-console does not function with root logging set to debug

Created: 24/Jan/11 10:20 AM   Updated: 20/Apr/11 12:48 PM
Component/s: broker
Affects Version/s: 5.4.2-fuse-00-00
Fix Version/s: 5.5.0-fuse-00-00

File Attachments: 1. Text File error-active-mq.log (477 kB)


 Description  « Hide
Hi,

When setting the logging to debug:

log4j.rootLogger=DEBUG, logfile, console

The Web Console is unreachable. The log file shows java.lang.ClassCircularityErrors:

INFO   | jvm 1    | 2011/01/21 13:34:15 | Exception in thread "ActiveMQ Journal Checkpoint Worker" java.lang.ClassCircularityError: org/apache/log4j/spi/LoggingEvent
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.fusesource.web.console.server.logging.BrowserAppender.toLogEvent(BrowserAppender.java:106)
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.fusesource.web.console.server.logging.BrowserAppender.append(BrowserAppender.java:68)
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.apache.log4j.Category.callAppenders(Category.java:203)
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.apache.log4j.Category.forcedLog(Category.java:388)
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.apache.log4j.Category.log(Category.java:853)
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.apache.commons.logging.impl.Log4JLogger.debug(Log4JLogger.java:171)
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.apache.activemq.store.kahadb.MessageDatabase.checkpointUpdate(MessageDatabase.java:1131)
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.apache.activemq.store.kahadb.MessageDatabase$10.execute(MessageDatabase.java:698)
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.apache.kahadb.page.Transaction.execute(Transaction.java:728)
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.apache.activemq.store.kahadb.MessageDatabase.checkpointCleanup(MessageDatabase.java:696)
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.apache.activemq.store.kahadb.MessageDatabase$3.run(MessageDatabase.java:293)
...
INFO   | jvm 1    | 2011/01/21 13:34:15 |  WARN | Error for /console/admin/agent
INFO   | jvm 1    | 2011/01/21 13:34:15 | java.lang.ClassCircularityError: org/apache/log4j/spi/LoggingEvent
INFO   | jvm 1    | 2011/01/21 13:34:15 |       at org.fusesource.web.console.server.logging.BrowserAppender.toLogEvent(BrowserAppender.java:106)
....
INFO   | jvm 1    | 2011/01/21 13:56:18 |  WARN | /console/admin/agent: java.lang.ClassCircularityError: org/apache/log4j/spi/LoggingEvent
INFO   | jvm 1    | 2011/01/21 13:56:18 |  WARN | handle failed
INFO   | jvm 1    | 2011/01/21 13:56:18 | java.lang.ClassCircularityError: org/apache/log4j/spi/LoggingEvent
INFO   | jvm 1    | 2011/01/21 13:56:18 |       at org.fusesource.web.console.server.logging.BrowserAppender.toLogEvent(BrowserAppender.java:106)
INFO   | jvm 1    | 2011/01/21 13:56:18 |       at org.fusesource.web.console.server.logging.BrowserAppender.append(BrowserAppender.java:68)
INFO   | jvm 1    | 2011/01/21 13:56:18 |       at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)

Complete log file attached.

Workaround
====================
The customer has been instructed to leave root logger on INFO and set activemq to DEBUG:

log4j.logger.org.apache.activemq=DEBUG

Susan

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Susan Javurek made changes - 24/Jan/11 10:20 AM
Field Original Value New Value
Description Hi,

When setting the logging to debug:

log4j.rootLogger=DEBUG, logfile, console

The Web Console is unreachable. The log file shows java.lang.ClassCircularityErrors:

{code}
....
NFO | jvm 1 | 2011/01/21 13:34:15 | Exception in thread "ActiveMQ Journal Checkpoint Worker" java.lang.ClassCircularityError: org/apache/log4j/spi/LoggingEvent
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.fusesource.web.console.server.logging.BrowserAppender.toLogEvent(BrowserAppender.java:106)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.fusesource.web.console.server.logging.BrowserAppender.append(BrowserAppender.java:68)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.log4j.Category.callAppenders(Category.java:203)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.log4j.Category.forcedLog(Category.java:388)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.log4j.Category.log(Category.java:853)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.commons.logging.impl.Log4JLogger.debug(Log4JLogger.java:171)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.activemq.store.kahadb.MessageDatabase.checkpointUpdate(MessageDatabase.java:1131)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.activemq.store.kahadb.MessageDatabase$10.execute(MessageDatabase.java:698)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.kahadb.page.Transaction.execute(Transaction.java:728)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.activemq.store.kahadb.MessageDatabase.checkpointCleanup(MessageDatabase.java:696)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.activemq.store.kahadb.MessageDatabase$3.run(MessageDatabase.java:293)
...
INFO | jvm 1 | 2011/01/21 13:34:15 | WARN | Error for /console/admin/agent
INFO | jvm 1 | 2011/01/21 13:34:15 | java.lang.ClassCircularityError: org/apache/log4j/spi/LoggingEvent
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.fusesource.web.console.server.logging.BrowserAppender.toLogEvent(BrowserAppender.java:106)
....
INFO | jvm 1 | 2011/01/21 13:56:18 | WARN | /console/admin/agent: java.lang.ClassCircularityError: org/apache/log4j/spi/LoggingEvent
INFO | jvm 1 | 2011/01/21 13:56:18 | WARN | handle failed
INFO | jvm 1 | 2011/01/21 13:56:18 | java.lang.ClassCircularityError: org/apache/log4j/spi/LoggingEvent
INFO | jvm 1 | 2011/01/21 13:56:18 | at org.fusesource.web.console.server.logging.BrowserAppender.toLogEvent(BrowserAppender.java:106)
INFO | jvm 1 | 2011/01/21 13:56:18 | at org.fusesource.web.console.server.logging.BrowserAppender.append(BrowserAppender.java:68)
INFO | jvm 1 | 2011/01/21 13:56:18 | at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)

{code}

Complete log file attached.

Workaround
====================
The customer has been instructed to leave root logger on INFO and set activemq to DEBUG:

log4j.logger.org.apache.activemq=DEBUG

Susan 		Hi,

When setting the logging to debug:

log4j.rootLogger=DEBUG, logfile, console

The Web Console is unreachable. The log file shows java.lang.ClassCircularityErrors:

{code}
INFO | jvm 1 | 2011/01/21 13:34:15 | Exception in thread "ActiveMQ Journal Checkpoint Worker" java.lang.ClassCircularityError: org/apache/log4j/spi/LoggingEvent
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.fusesource.web.console.server.logging.BrowserAppender.toLogEvent(BrowserAppender.java:106)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.fusesource.web.console.server.logging.BrowserAppender.append(BrowserAppender.java:68)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.log4j.Category.callAppenders(Category.java:203)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.log4j.Category.forcedLog(Category.java:388)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.log4j.Category.log(Category.java:853)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.commons.logging.impl.Log4JLogger.debug(Log4JLogger.java:171)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.activemq.store.kahadb.MessageDatabase.checkpointUpdate(MessageDatabase.java:1131)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.activemq.store.kahadb.MessageDatabase$10.execute(MessageDatabase.java:698)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.kahadb.page.Transaction.execute(Transaction.java:728)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.activemq.store.kahadb.MessageDatabase.checkpointCleanup(MessageDatabase.java:696)
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.apache.activemq.store.kahadb.MessageDatabase$3.run(MessageDatabase.java:293)
...
INFO | jvm 1 | 2011/01/21 13:34:15 | WARN | Error for /console/admin/agent
INFO | jvm 1 | 2011/01/21 13:34:15 | java.lang.ClassCircularityError: org/apache/log4j/spi/LoggingEvent
INFO | jvm 1 | 2011/01/21 13:34:15 | at org.fusesource.web.console.server.logging.BrowserAppender.toLogEvent(BrowserAppender.java:106)
....
INFO | jvm 1 | 2011/01/21 13:56:18 | WARN | /console/admin/agent: java.lang.ClassCircularityError: org/apache/log4j/spi/LoggingEvent
INFO | jvm 1 | 2011/01/21 13:56:18 | WARN | handle failed
INFO | jvm 1 | 2011/01/21 13:56:18 | java.lang.ClassCircularityError: org/apache/log4j/spi/LoggingEvent
INFO | jvm 1 | 2011/01/21 13:56:18 | at org.fusesource.web.console.server.logging.BrowserAppender.toLogEvent(BrowserAppender.java:106)
INFO | jvm 1 | 2011/01/21 13:56:18 | at org.fusesource.web.console.server.logging.BrowserAppender.append(BrowserAppender.java:68)
INFO | jvm 1 | 2011/01/21 13:56:18 | at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)

{code}

Complete log file attached.

Workaround
====================
The customer has been instructed to leave root logger on INFO and set activemq to DEBUG:

log4j.logger.org.apache.activemq=DEBUG

Susan
Susan Javurek made changes - 24/Jan/11 10:21 AM
Attachment error-active-mq.log [ 18300 ]
Susan Javurek made changes - 24/Jan/11 10:23 AM
Link This issue blocks PROD-540 [ PROD-540 ]
Fintan Bolton made changes - 14/Apr/11 10:06 AM
Assignee Susan Javurek [ sjavurek ]
Susan Javurek made changes - 14/Apr/11 01:02 PM
Assignee Susan Javurek [ sjavurek ]
Dejan Bosanac made changes - 20/Apr/11 12:48 PM
Status Open [ 1 ] Resolved [ 5 ]
Assignee Dejan Bosanac [ dejanb ]
Fix Version/s 5.5.0-fuse-00-00 [ 11211 ]
Resolution Fixed [ 1 ]

Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators