Bug 107815 - Notification threads fail with NPE
Notification threads fail with NPE
Status: CLOSED RAWHIDE
Product: Red Hat Web Application Framework
Classification: Retired
Component: other (Show other bugs)
nightly
All Linux
medium Severity high
: ---
: ---
Assigned To: ccm-bugs-list
Jon Orris
:
Depends On:
Blocks: 106597
  Show dependency treegraph
 
Reported: 2003-10-23 08:18 EDT by Daniel Berrange
Modified: 2007-04-18 12:58 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-11-13 17:19:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Daniel Berrange 2003-10-23 08:18:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.9 (X11; Linux i686; U;) Gecko/20030314

Description of problem:
The background threads spawned by the notification service are failing with NPEs:

java.lang.NullPointerException
        at
com.arsdigita.notification.RequestManager$1.excurse(RequestManager.java:96)
        at com.arsdigita.kernel.KernelExcursion.run(KernelExcursion.java:57)
        at com.arsdigita.notification.RequestManager.run(RequestManager.java:204)
        at java.util.TimerThread.mainLoop(Timer.java:445)
        at java.util.TimerThread.run(Timer.java:395)
java.lang.NullPointerException
        at
com.arsdigita.notification.SimpleQueueManager.run(SimpleQueueManager.java:59)
        at java.util.TimerThread.mainLoop(Timer.java:445)
        at java.util.TimerThread.run(Timer.java:395)


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


How reproducible:
Always

Steps to Reproduce:
1. Start a server
2. watch the logs
3. wait a while
    

Actual Results:  NPE execeptions from notification threads

Expected Results:  No exceptions


Additional info:
Comment 1 Rafael H. Schloming 2003-11-07 19:14:40 EST
Fixed @37843.

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