JBoss ON is losing log events due to event report maximum size being exceeded
Issue
- Some events from log file are missing
-
Log events are dropped and agent contains the following warning:
WARN [EventManager.sender-1] (rhq.core.pc.event.EventManager)- Begin dropped events report WARN [EventManager.sender-1] (rhq.core.pc.event.EventManager)- There were 642 dropped events for source 'EventSource[id=0, eventDefinition.name=logEntry, resource.name=SOA 172.30.96.116:1099 production, location=/opt/jboss/jboss-soa/jboss-as/server/default/log/server.log]' WARN [EventManager.sender-1] (rhq.core.pc.event.EventManager)- Finish dropped events report -
On several occasions we have noticed that JON stops acknowledging events.
-
The agent log file contains the following:
WARN [EventManager.sender-1] (core.domain.event.transfer.EventReport)- Event Report Limit Reached: reached the maximum allowed events [200] for this event source - dropped [36] events: source=[EventSource[id=0, eventDefinition.name=logEntry, resource.name=SRV007 JBossEAP 4.3.0.GA_CP03 j1 (10.20.30.17:1099), location=/usr/local/jboss/server/node1/log/server.log]] -
log4j events not working as expected
- Event logging for a resource stops when too many log entries exist in a single event log source
- Some log entries are lost by the event logger when the event report limit is reached or exceeded
Environment
- Red Hat JBoss Operations Network (ON)
- 2.2, 2.3, 2.4, 3.0, 3.1, 3.2, 3.3
- Log Event Monitoring of one or more resources
- Red Hat JBoss Application Server (AS) log events
- Red Hat JBoss Enterprise Application Platform (EAP) log events
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
