[QPID-1664] Asynchronous notification capability

• Type: Sub-task
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.5
• Fix Version/s: 0.5
• Labels: qman

Environment

J2SE 1.5 or higher

• Assignee: Andrea Gazzarini
• Reporter: Andrea Gazzarini
• Due: 14/Feb/09
• Created: 14/Feb/09 10:46
• Updated: 14/Mar/17 20:12
• Resolved: 14/Feb/09 10:59

Description

The current implementation of WS-Notification engine is synchronous. That means the publisher (QMan) will remain blocked until the notification has been processed on oberserver (client) side...this is in generarl not acceptable because a server component depends on a client behaviour...
So, notifications should be processed in separate threads. JDK 1.5 introduced a TrheadPoolEXecutor that is something like a WorkManager in a JEE environment.
Qman will use it for asynchronous notification capability.