[SM-233] JCA Work - Long running Work methods are going to cause problems....

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.0.2
• Assignee: Unassigned
• Reporter: Peter Samuelson
• Created: 12/Dec/05 01:14
• Updated: 26/Mar/13 13:36
• Resolved: 26/Mar/13 13:36

Description

See also IRC (12/12). There appear to be a general assumption that the scheduled Work instances are going to complete very quickly. If they do then all may seem OK.

But slow Work could cause lots of problems. For example, FTPPoller looks buggy - if a 2nd poll occurs before a 1st poll completes then it is going to go bananas and reprocess and attempt the same file again in parallel.

There seems a general problem with ALL the servicemix usage of the WorkManager Work - ie in general there seem no way to interrupt long runnng Work processing. This is releated to writing proper Work.release() methods as well as potential shutdown issues.

Sub-Tasks

• JCA Work instances not correctly synchronized with ServiceMix shutdown: Closed
• JCA Work - release() method not implemented or not implemented correctly: Closed