Bug 1307104 - "org.hyperic.sigar.win32.Win32Exception: Buffer size (8192) too small (10332 needed)" when reading Windows events
Summary: "org.hyperic.sigar.win32.Win32Exception: Buffer size (8192) too small (10332 ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Monitoring - Events, Agent
Version: JON 3.3.0
Hardware: Unspecified
OS: Windows
high
high
Target Milestone: CR01
: JON 3.3.8
Assignee: Simeon Pinder
QA Contact: Filip Brychta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-12 17:31 UTC by Marc Shirley
Modified: 2019-10-10 11:11 UTC (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-16 18:44:48 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2155731 0 None None None 2016-02-12 17:32:00 UTC
Red Hat Product Errata RHEA-2017:0285 0 normal SHIPPED_LIVE Red Hat JBoss Operations Network 3.3.8 bug fix update 2017-02-16 23:44:22 UTC

Description Marc Shirley 2016-02-12 17:31:16 UTC
Description of problem:
When collecting Windows events, receive an error like the below.  Based on https://jira.hyperic.com/browse/SIGAR-251 this is a hardcoded buffer.

2016-02-08 12:55:05,051 INFO  [EventManager.poller-3] (rhq.plugins.platform.win.Win32EventLogDelegate)- An error occurred while reading the Windows Event Log [Application]
org.hyperic.sigar.win32.Win32Exception: Buffer size (8192) too small (10332 needed)
	at org.hyperic.sigar.win32.EventLog.readlog(Native Method)
	at org.hyperic.sigar.win32.EventLog.read(EventLog.java:98)
	at org.rhq.plugins.platform.win.Win32EventLogDelegate.checkForNewEvents(Win32EventLogDelegate.java:131)
	at org.rhq.plugins.platform.win.Win32EventLogDelegate.poll(Win32EventLogDelegate.java:189)
	at org.rhq.core.pc.event.EventPollerRunner.run(EventPollerRunner.java:56)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

Version-Release number of selected component (if applicable):
JBoss ON 3.3


Additional info:
SIGAR-251 [1] exists for this issue but is in Closed -> Deferred status.

[1] https://jira.hyperic.com/browse/SIGAR-251

Comment 18 Simeon Pinder 2017-02-08 06:03:28 UTC
Moving to ON_QA as available for test with the latest build:

JON 3.3.8 CR01 artifacts are available for test from here:
http://download.eng.bos.redhat.com/brewroot/packages/org.jboss.on-jboss-on-parent/3.3.0.GA/114/maven/org/jboss/on/jon-server-patch/3.3.0.GA/jon-server-patch-3.3.0.GA.zip
 *Note: jon-server-patch-3.3.0.GA.zip maps to CR01 build of
 jon-server-3.3.0.GA-update-08.zip.

https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=537179

Comment 20 errata-xmlrpc 2017-02-16 18:44:48 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2017-0285.html


Note You need to log in before you can comment on or make changes to this bug.