Issue Details (XML | Word | Printable)

Key: MULE-3680
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Daniel Feist
Reporter: Daniel Feist
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Mule

Deserialized instances of DefaultMuleEvent are missing endpoint instance.

Created: 19/Sep/08 01:18 AM   Updated: 28/Sep/08 10:37 PM
Component/s: Core: Queues (SEDA) / Persistence
Affects Version/s: 2.1-M2
Fix Version/s: 2.0 ITR7, 2.1.0

Time Tracking:
Original Estimate: 6 hours
Original Estimate - 6 hours
Remaining Estimate: 0 minutes
Time Spent - 5 hours
Time Spent: 5 hours
Time Spent - 5 hours Time Not Required

Issue Links:
Related
 

Labels:
User impact: High


 Description  « Hide
This happens if events are deserialized after the registry is disposed and recreating or if jvm is restarted etc.

 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Daniel Feist added a comment - 28/Sep/08 05:44 PM
Removed blocking link for MULE-3720 (Implement equals methods for service, component etc.), see comments on this issue

I will implement a much more rudimentary test case for endpoint deserialization with a new muleContext instance.