[OODT-979] [AvroRPC] WorkflowManagerClient CLI hangs after starting a dynamic workflow

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.9
• Fix Version/s: 1.9
• Component/s: workflow manager
• Skill Level: Don't Know (Unsure) - The default level
• Assignee: Imesha Sudasingha
• Reporter: Imesha Sudasingha
• Created: 25/May/18 05:46
• Updated: 25/May/18 16:05
• Resolved: 25/May/18 16:05

Description

When WM client is upgraded to use AvroRPCWorkflowManagerClient, the CLI hangs after starting the workflow instance. This happens because the underlying Netty Transceiver used has a running threadpool even after the communication is complete. Closing the NettyTranceiver fixes this issue which was implemented in OODT-978.

So, updating workflow manager components to close the WMClient once done is the solution.

Issue Links

• links to: GitHub Pull Request #63