Bug 103418

Summary: ThreadedMessage.replyTo() throws NPE if there is no associated MessageThread
Product: [Retired] Red Hat Web Application Framework Reporter: Scott Seago <sseago>
Component: otherAssignee: ccm-bugs-list
Status: CLOSED WONTFIX QA Contact: Jon Orris <jorris>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-09 15:31:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Scott Seago 2003-08-29 22:09:24 UTC 
Description of problem:
ThreadedMessage.replyTo() throws NPE if there is no associated MessageThread. In
theory, this should not happen, as the afterSave() event of ThreadedMessage
should create the MessageThread. However, I ran into at least one case where
there were ThreadedMessage objects without a created thread. London change 35504
creates a MessageThread in ThreadedMessage.getThread() if none is found.