[#MULE-2961] Restoring persisted events does not reattach event to valid UMOSession

Mule

Restoring persisted events does not reattach event to valid UMOSession

Created: 01/Feb/08 09:08 AM Updated: 02/Jun/08 01:15 PM

Component/s:

Core: Queues (SEDA) / Persistence

Affects Version/s:

1.4.3

Fix Version/s:

2.0.2, 1.4.4

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue is duplicated by:

~~MULE-2987~~ SEDA components with persisted queue do not receive asynchronous events.

Related

This issue relates to:

~~MULE-2038~~ Transformers are not persisted when using VM queueing

This issue relates to:

~~MULE-2962~~ Misleading OptionalDataException in MuleEvent.unmarshallTransformers

Labels:
User impact:	High

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Holger Hoffstaette - 01/Feb/08 09:12 AM

Running org.mule.test.integration.persistenceFilePersistenceTestCase shows shadowed (swallowed) NPEs in DefaultMuleProxy etc. After several hours of debugging it turns out that the event passed into the MuleProxy by SedaComponent (dequeued from the componnet's queue) has no session attached, leading to an NPE.

[ Permlink | « Hide ]

Andrew Calafato - 06/Mar/08 08:43 AM

Persisted the endpoint type and session but not component within session.

Updated PersistentVMQueueTestCase to cover the issue.

Trunk revision http://fisheye.codehaus.org/changelog/mule/?cs=11209

[ Permlink | « Hide ]

Daniel Feist - 02/Jun/08 01:15 PM

2.x: http://fisheye.codehaus.org/changelog/mule/?cs=11894