[JBoss JIRA] Created: (JBMESSAGING-1817) Gigabytes of data getting logged under jboss OrderingGroupMonitor logs
5:13 a.m.
Gigabytes of data getting logged under jboss OrderingGroupMonitor logs
----------------------------------------------------------------------
Key: JBMESSAGING-1817
URL: https://jira.jboss.org/browse/JBMESSAGING-1817
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.3.GA
Environment: Unix
Reporter: Maya Agnihotri
Fix For: 1.4.3.GA
In a jboss messaging 1.4.3.GA instance, I'm getting the following log line, repeated
at full speed, running up a many-gigabyte log file until the disk runs out of space quite
quickly:
2010-08-19 11:51:08,885 DEBUG [org.jboss.messaging.core.impl.OrderingGroupMonitor] message
doesn't have group prop, fine by me
2010-08-19 11:51:08,885 DEBUG [org.jboss.messaging.core.impl.OrderingGroupMonitor] message
doesn't have group prop, fine by me
Due to this issue my deployment is also not happening. Please suggest the cause of the
issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:24 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1817) Gigabytes of data getting logged under jboss OrderingGroupMonitor logs
[
https://jira.jboss.org/browse/JBMESSAGING-1817?page=com.atlassian.jira.pl...
]
Howard Gao commented on JBMESSAGING-1817:
-----------------------------------------
You need to set you log level to a less verbose one. For example INFO.
Gigabytes of data getting logged under jboss OrderingGroupMonitor
logs
----------------------------------------------------------------------
Key: JBMESSAGING-1817
URL: https://jira.jboss.org/browse/JBMESSAGING-1817
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.3.GA
Environment: Unix
Reporter: Maya Agnihotri
Fix For: 1.4.3.GA
In a jboss messaging 1.4.3.GA instance, I'm getting the following log line, repeated
at full speed, running up a many-gigabyte log file until the disk runs out of space quite
quickly:
2010-08-19 11:51:08,885 DEBUG [org.jboss.messaging.core.impl.OrderingGroupMonitor]
message doesn't have group prop, fine by me
2010-08-19 11:51:08,885 DEBUG [org.jboss.messaging.core.impl.OrderingGroupMonitor]
message doesn't have group prop, fine by me
Due to this issue my deployment is also not happening. Please suggest the cause of the
issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:47 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1817) Gigabytes of data getting logged under jboss OrderingGroupMonitor logs
[
https://jira.jboss.org/browse/JBMESSAGING-1817?page=com.atlassian.jira.pl...
]
Maya Agnihotri commented on JBMESSAGING-1817:
---------------------------------------------
Because of this issue my application is also not getting deployed. Even if i reduce the
Verbose level to INFO , the problem will still persist .
The only change will be that it will log less.
Please correct me If i am wrong.
Gigabytes of data getting logged under jboss OrderingGroupMonitor
logs
----------------------------------------------------------------------
Key: JBMESSAGING-1817
URL: https://jira.jboss.org/browse/JBMESSAGING-1817
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.3.GA
Environment: Unix
Reporter: Maya Agnihotri
Fix For: 1.4.3.GA
In a jboss messaging 1.4.3.GA instance, I'm getting the following log line, repeated
at full speed, running up a many-gigabyte log file until the disk runs out of space quite
quickly:
2010-08-19 11:51:08,885 DEBUG [org.jboss.messaging.core.impl.OrderingGroupMonitor]
message doesn't have group prop, fine by me
2010-08-19 11:51:08,885 DEBUG [org.jboss.messaging.core.impl.OrderingGroupMonitor]
message doesn't have group prop, fine by me
Due to this issue my deployment is also not happening. Please suggest the cause of the
issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:44 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1817) Gigabytes of data getting logged under jboss OrderingGroupMonitor logs
[
https://jira.jboss.org/browse/JBMESSAGING-1817?page=com.atlassian.jira.pl...
]
Howard Gao commented on JBMESSAGING-1817:
-----------------------------------------
I guess your log level isn't correctly set. you can see the log is DEBUG. If you set
to INFO, those won't appear in the log file. If you like you can upload your log
config file and I'll have a look.
Gigabytes of data getting logged under jboss OrderingGroupMonitor
logs
----------------------------------------------------------------------
Key: JBMESSAGING-1817
URL: https://jira.jboss.org/browse/JBMESSAGING-1817
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.3.GA
Environment: Unix
Reporter: Maya Agnihotri
Fix For: 1.4.3.GA
In a jboss messaging 1.4.3.GA instance, I'm getting the following log line, repeated
at full speed, running up a many-gigabyte log file until the disk runs out of space quite
quickly:
2010-08-19 11:51:08,885 DEBUG [org.jboss.messaging.core.impl.OrderingGroupMonitor]
message doesn't have group prop, fine by me
2010-08-19 11:51:08,885 DEBUG [org.jboss.messaging.core.impl.OrderingGroupMonitor]
message doesn't have group prop, fine by me
Due to this issue my deployment is also not happening. Please suggest the cause of the
issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:37 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1817) Gigabytes of data getting logged under jboss OrderingGroupMonitor logs
[
https://jira.jboss.org/browse/JBMESSAGING-1817?page=com.atlassian.jira.pl...
]
Maya Agnihotri commented on JBMESSAGING-1817:
---------------------------------------------
Here is the log file . Instead of using the daily Rolling File appender , we are using the
Rolling File Appender.
=============================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<!-- ===================================================================== -->
<!-- -->
<!-- Log4j Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- $Id: jboss-log4j.xml 79553 2008-10-15 20:31:41Z rrajesh $ -->
<!--
| For more configuration infromation and examples see the Jakarta Log4j
| owebsite: http://jakarta.apache.org/log4j
-->
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/"
debug="false">
<!-- ================================= -->
<!-- Preserve messages in a local file -->
<!-- ================================= -->
<!-- A time/date based rolling appender
<appender name="FILE"
class="org.jboss.logging.appender.DailyRollingFileAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="File"
value="${jboss.server.log.dir}/server.log"/>
<param name="Append" value="false"/>
<param name="MaxFileSize" value="500KB"/>
<param name="MaxBackupIndex" value="20"/>
Rollover at midnight each day
<param name="DatePattern" value="'.'yyyy-MM-dd"/>
Rollover at the top of each hour
<param name="DatePattern"
value="'.'yyyy-MM-dd-HH"/>
<layout class="org.apache.log4j.PatternLayout">
The default pattern: Date Priority [Category] Message\n
<param name="ConversionPattern" value="%d %-5p [%c]
%m%n"/>
The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
<param name="ConversionPattern" value="%d %-5r %-5p [%c]
(%t:%x) %m%n"/>
</layout>
</appender>
-->
<!-- A size based file rolling appender -->
<appender name="FILE"
class="org.jboss.logging.appender.RollingFileAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="File"
value="${jboss.server.log.dir}/server.log"/>
<param name="Append" value="true"/>
<param name="MaxFileSize" value="250MB"/>
<param name="MaxBackupIndex" value="10"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p [%c]
%m%n"/>
</layout>
</appender>
<!-- ============================== -->
<!-- Append messages to the console -->
<!-- ============================== -->
<!--
<appender name="CONSOLE"
class="org.apache.log4j.ConsoleAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="Target" value="System.out"/>
<param name="Threshold" value="INFO"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d{ABSOLUTE} %-5p
[%c{1}] %m%n"/>
</layout>
</appender>
-->
<!-- ====================== -->
<!-- More Appender examples -->
<!-- ====================== -->
<!-- Buffer events and log them asynchronously -->
<appender name="ASYNC"
class="org.apache.log4j.AsyncAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<appender-ref ref="FILE"/>
<!--
<appender-ref ref="CONSOLE"/>
<appender-ref ref="SMTP"/>
-->
</appender>
<!-- EMail events to an administrator
<appender name="SMTP"
class="org.apache.log4j.net.SMTPAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="Threshold" value="ERROR"/>
<param name="To" value="admin(a)myhost.domain.com"/>
<param name="From" value="nobody(a)myhost.domain.com"/>
<param name="Subject" value="JBoss Sever Errors"/>
<param name="SMTPHost" value="localhost"/>
<param name="BufferSize" value="10"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="[%d{ABSOLUTE},%c{1}]
%m%n"/>
</layout>
</appender>
-->
<!-- Syslog events
<appender name="SYSLOG"
class="org.apache.log4j.net.SyslogAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="Facility" value="LOCAL7"/>
<param name="FacilityPrinting" value="true"/>
<param name="SyslogHost" value="localhost"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="[%d{ABSOLUTE},%c{1}]
%m%n"/>
</layout>
</appender>
-->
<!-- Log events to JMS (requires a topic to be created)
<appender name="JMS"
class="org.apache.log4j.net.JMSAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="Threshold" value="ERROR"/>
<param name="TopicConnectionFactoryBindingName"
value="java:/ConnectionFactory"/>
<param name="TopicBindingName"
value="topic/MyErrorsTopic"/>
</appender>
-->
<!-- Log events through SNMP
<appender name="TRAP_LOG"
class="org.apache.log4j.ext.SNMPTrapAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="ImplementationClassName"
value="org.apache.log4j.ext.JoeSNMPTrapSender"/>
<param name="ManagementHost" value="127.0.0.1"/>
<param name="ManagementHostTrapListenPort" value="162"/>
<param name="EnterpriseOID" value="1.3.6.1.4.1.24.0"/>
<param name="LocalIPAddress" value="127.0.0.1"/>
<param name="LocalTrapSendPort" value="161"/>
<param name="GenericTrapType" value="6"/>
<param name="SpecificTrapType" value="12345678"/>
<param name="CommunityString" value="public"/>
<param name="ForwardStackTraceWithTrap" value="true"/>
<param name="Threshold" value="DEBUG"/>
<param name="ApplicationTrapOID"
value="1.3.6.1.4.1.24.12.10.22.64"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern"
value="%d,%p,[%t],[%c],%m%n"/>
</layout>
</appender>
-->
<!-- Emit events as JMX notifications
<appender name="JMX"
class="org.jboss.monitor.services.JMXNotificationAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="Threshold" value="WARN"/>
<param name="ObjectName"
value="jboss.system:service=Logging,type=JMXNotificationAppender"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p [%c]
%m"/>
</layout>
</appender>
-->
<!-- Clustering logging -->
<!-- Uncomment the following to redirect the org.jgroups and
org.jboss.ha categories to a cluster.log file. -->
<!--
<appender name="CLUSTER"
class="org.jboss.logging.appender.RollingFileAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="File"
value="${jboss.server.log.dir}/cluster.log"/>
<param name="Append" value="false"/>
<param name="MaxFileSize" value="500KB"/>
<param name="MaxBackupIndex" value="1"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p [%c]
%m%n"/>
</layout>
</appender>
-->
<!-- ================ -->
<!-- Limit categories -->
<!-- ================ -->
<category name="org.jboss.web">
<priority value="INFO" />
</category>
<category name="org.jboss.ha">
<priority value="INFO" />
</category>
<category name="com.arjuna">
<priority value="INFO" />
</category>
<category name="org.hibernate">
<priority value="INFO" />
</category>
<!-- Limit JSF logging to DEBUG. FINER and FINEST will not be logged -->
<category name="javax.enterprise.resource.webcontainer">
<priority value="INFO" />
</category>
<!-- Limit org.ajax4jsf to INFO as DEBUG is too verbose -->
<category name="org.ajax4jsf">
<priority value="INFO" />
</category>
<!-- Enable this to obtain EJB Based Applications Access Log Entries
<category name="org.jboss.ejb.plugins.SecurityInterceptor">
<priority value="TRACE"/>
</category>
-->
<!-- Limit the org.apache category to INFO as its DEBUG is verbose -->
<category name="org.apache">
<priority value="WARN"/>
</category>
<!-- Limit the org.jboss.serial (jboss-serialization) to INFO as its DEBUG is
verbose -->
<category name="org.jboss.serial">
<priority value="WARN"/>
</category>
<!-- Limit the org.jgroups category to WARN as its INFO is verbose -->
<category name="org.jgroups">
<priority value="WARN"/>
</category>
<!-- Limit the jacorb category to WARN as its INFO is verbose -->
<category name="jacorb">
<priority value="WARN"/>
</category>
<!-- Limit JBoss categories
<category name="org.jboss">
<priority value="INFO"/>
</category>
-->
<!-- Limit the JSR77 categories -->
<category name="org.jboss.management">
<priority value="WARN"/>
</category>
<!-- Limit seam logging -->
<category name="org.jboss.seam">
<priority value="WARN"/>
</category>
<!-- Enable JBossWS message tracing
<category name="org.jboss.ws.core.MessageTrace">
<priority value="TRACE"/>
</category>
-->
<!-- Decrease the priority threshold for the org.jboss.varia category
<category name="org.jboss.varia">
<priority value="DEBUG"/>
</category>
-->
<!-- Show the evolution of the DataSource pool in the logs [inUse/Available/Max]
<category
name="org.jboss.resource.connectionmanager.JBossManagedConnectionPool">
<priority value="TRACE"/>
</category>
-->
<!--
| An example of enabling the custom TRACE level priority that is used
| by the JBoss internals to diagnose low level details. This example
| turns on TRACE level msgs for the org.jboss.ejb.plugins package and its
| subpackages. This will produce A LOT of logging output.
|
| Note: since jboss AS 4.2.x, the trace level is supported natively by
| log4j, so although the custom org.jboss.logging.XLevel priority will
| still work, there is no need to use it. The two examples that follow
| will both enable trace logging.
<category name="org.jboss.system">
<priority value="TRACE" class="org.jboss.logging.XLevel"/>
</category>
<category name="org.jboss.ejb.plugins">
<priority value="TRACE"/>
</category>
-->
<!--
| Logs these events to SNMP:
- server starts/stops
- cluster evolution (node death/startup)
- When an EJB archive is deployed (and associated verified messages)
- When an EAR archive is deployed
<category name="org.jboss.system.server.Server">
<priority value="INFO" />
<appender-ref ref="TRAP_LOG"/>
</category>
<category
name="org.jboss.ha.framework.interfaces.HAPartition.lifecycle">
<priority value="INFO" />
<appender-ref ref="TRAP_LOG"/>
</category>
<category name="org.jboss.deployment.MainDeployer">
<priority value="ERROR" />
<appender-ref ref="TRAP_LOG"/>
</category>
<category name="org.jboss.ejb.EJBDeployer">
<priority value="INFO" />
<appender-ref ref="TRAP_LOG"/>
</category>
<category name="org.jboss.deployment.EARDeployer">
<priority value="INFO" />
<appender-ref ref="TRAP_LOG"/>
</category>
-->
<!-- ======================= -->
<!-- Setup the Root category -->
<!-- ======================= -->
<root>
<!-- <appender-ref ref="CONSOLE"/> -->
<appender-ref ref="ASYNC"/>
</root>
</log4j:configuration>
==============================================================
Gigabytes of data getting logged under jboss OrderingGroupMonitor
logs
----------------------------------------------------------------------
Key: JBMESSAGING-1817
URL: https://jira.jboss.org/browse/JBMESSAGING-1817
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.3.GA
Environment: Unix
Reporter: Maya Agnihotri
Fix For: 1.4.3.GA
In a jboss messaging 1.4.3.GA instance, I'm getting the following log line, repeated
at full speed, running up a many-gigabyte log file until the disk runs out of space quite
quickly:
2010-08-19 11:51:08,885 DEBUG [org.jboss.messaging.core.impl.OrderingGroupMonitor]
message doesn't have group prop, fine by me
2010-08-19 11:51:08,885 DEBUG [org.jboss.messaging.core.impl.OrderingGroupMonitor]
message doesn't have group prop, fine by me
Due to this issue my deployment is also not happening. Please suggest the cause of the
issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5834
days inactive
5837
days old
4 comments
2 participants
participants (2)
-
Howard Gao (JIRA) -
Maya Agnihotri (JIRA)