Issue Details (XML | Word | Printable)

Key: MULE-2962
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Dirk Olmes
Reporter: Holger Hoffstaette
Votes: 0
Watchers: 0
Operations

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

Misleading OptionalDataException in MuleEvent.unmarshallTransformers

Created: 01/Feb/08 09:18 AM   Updated: 05/Jun/08 04:04 PM
Component/s: Core: Queues (SEDA) / Persistence, Core: Transformers
Affects Version/s: 1.4.3
Fix Version/s: 1.4.4, 2.0.2

Time Tracking:
Not Specified

Issue Links:
Related
 

Labels:
User impact: Medium


 Description  « Hide
MuleEvent.unmarshallTransformers is called from readObject(). Since the number of written transformer names is unknown, it simply reads until no more data can be read. This creates very confusing debugging output because it indicates errors even though nothing wrong happened. Writing the number of transformer names to be read (or an array) would solve this problem.

 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Holger Hoffstaette added a comment - 04/Feb/08 11:08 AM
fixed in r10688, pending further review & decision re. persistence strategies

Holger Hoffstaette added a comment - 05/Feb/08 06:24 AM
This is also valid in 2.x; Dirk will port forward.

Dirk Olmes added a comment - 08/Feb/08 06:05 AM

Daniel Feist added a comment - 02/Jun/08 01:33 PM
This is not apply in 2.x anymore because transformer names are not serialized. Blocked in http://fisheye.codehaus.org/changelog/mule/?cs=11896