[
https://issues.apache.org/jira/browse/OODT-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490289#comment-16490289
]
ASF GitHub Bot commented on OODT-979:
-------------------------------------
GitHub user IMS94 opened a pull request:
https://github.com/apache/oodt/pull/63
[OODT-979] Stabilized AvroRpc workflow manager client
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/IMS94/oodt master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/oodt/pull/63.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #63
----
commit 836499df6cb95b646fa557048ae3dd73ebde2928
Author: Imesha Sudasingha <imesha.sudasingha@...>
Date: 2018-05-25T05:50:46Z
[OODT-979] Removed XML RPC versions of workflow manager client from all
possible
places and added client.close() wherever necessary. Now the WM client CLI
is working without any hanging.
This commit is the last of many which were to stabilize Avro RPC
implementations.
----
> [AvroRPC] WorkflowManagerClient CLI hangs after starting a dynamic workflow
> ---------------------------------------------------------------------------
>
> Key: OODT-979
> URL: https://issues.apache.org/jira/browse/OODT-979
> Project: OODT
> Issue Type: Bug
> Components: workflow manager
> Affects Versions: 1.9
> Reporter: Imesha Sudasingha
> Assignee: Imesha Sudasingha
> Priority: Major
> Fix For: 1.9
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
