[OOZIE-1108] Fix JMS message consumer to maintain single session per topic registration

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk
• Fix Version/s: 4.0.0
• Assignee: Mona Chitnis
• Reporter: Mona Chitnis
• Created: 30/Nov/12 19:03
• Updated: 31/Aug/13 00:02
• Resolved: 14/Dec/12 22:03

Description

When a coordinator spawns multiple actions, there is a different message consumer created per action, even though all actions are registering to single HCat topic. This is undesirable.

Also refactoring some messaging-oriented methods into the JMSAccessorService to be in a single location, is to be done