Bug 779615 (SOA-1985)

Summary: NPE when collecting alerts and accessing the admin console
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jaroslaw Kijanowski <kijanowski>
Component: Monitoring and Management, JONAssignee: tcunning
Status: CLOSED WORKSFORME QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 GA, 5.1.0.ER9   
Target Milestone: ---   
Target Release: 5.2.0 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1985
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-15 17:09:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jaroslaw Kijanowski 2010-03-09 16:29:12 UTC
project_key: SOA

1. download SOA-P 5 from

http://jawa05.englab.brq.redhat.com/released/soa-5.0.0.GA/soa-5.0.0.GA.zip

2. unzip, add user admin=admin in jboss-soa-p.5.0.0/jboss-as/server/production/conf/props/soa-users.properties, start the production config

3. create jboss-soa-p.5.0.0/jboss-as/samples/quickstarts/quickstarts.properties
org.jboss.esb.server.config=production
jbpm.console.username=admin
jbpm.console.password=admin

4. go to jboss-soa-p.5.0.0/jboss-as/samples/quickstarts/messagealerts
$ ant deploy
verify esb has been deployed successfully
$ ant runtest

5. verify 4 WARN messages showed up in the server console

so far so good...

6. open the admin console and login as admin/admin
http://x.x.x.x:8080/admin-console/

7. wait for the NPE, it shows up every 60 seconds:
04:38:59,490 WARN [EventManager] Failure to report Events to Server.
java.lang.NullPointerException
at org.rhq.core.pc.event.EventManager.sendEventReport(EventManager.java:133)
at org.rhq.core.pc.event.EventSenderRunner.call(EventSenderRunner.java:48)
at org.rhq.core.pc.event.EventSenderRunner.run(EventSenderRunner.java:54)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)


If there wouldn't be any alerts, this NPE wouldn't show up.

Comment 2 mvanek 2011-02-04 14:02:44 UTC
Also present in 5.1 ER9.

Comment 3 tcunning 2011-07-29 20:34:48 UTC
I can't reproduce this in 5.2.0 ER1.   May be fixed thanks to changes in the alerting mechanism previously.

Comment 4 David Le Sage 2011-08-18 00:17:54 UTC
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage