[
https://issues.apache.org/jira/browse/OODT-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490915#comment-16490915
]
ASF GitHub Bot commented on OODT-979:
-------------------------------------
Github user chrismattmann commented on the issue:
https://github.com/apache/oodt/pull/63
works fine!
```
[INFO]
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @
oodt ---
[INFO]
[INFO] >>> maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) >
generate-sources @ oodt >>>
[INFO]
[INFO] <<< maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) <
generate-sources @ oodt <<<
[INFO]
[INFO]
[INFO] --- maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) @ oodt ---
[INFO]
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ oodt ---
[INFO] Installing /Users/mattmann/git/oodt/pom.xml to
/Users/mattmann/.m2/repository/org/apache/oodt/oodt/1.9-SNAPSHOT/oodt-1.9-SNAPSHOT.pom
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] OODT Core .......................................... SUCCESS [
2.966 s]
[INFO] Common Utilities ................................... SUCCESS [
25.553 s]
[INFO] CAS Command Line Interface ......................... SUCCESS [
9.238 s]
[INFO] OODT - Configuration Management .................... SUCCESS [
26.115 s]
[INFO] Process Control System Input Data Package .......... SUCCESS [
2.539 s]
[INFO] Catalog and Archive Service Generic Multi-valued Metadata Container
SUCCESS [ 3.944 s]
[INFO] Catalog and Archive File Management Component ...... SUCCESS [04:00
min]
[INFO] Catalog and Archive Resource Management Component .. SUCCESS [
34.679 s]
[INFO] Catalog and Archive Workflow Management Component .. SUCCESS [
44.468 s]
[INFO] Catalog and Archive Crawling Framework ............. SUCCESS [
25.364 s]
[INFO] OODT CAS Curator Single Sign On Security Package ... SUCCESS [
1.768 s]
[INFO] CAS Curation Web Services .......................... SUCCESS [
10.596 s]
[INFO] Process Control System Core Package ................ SUCCESS [
22.956 s]
[INFO] OODT Wicket Web Components ......................... SUCCESS [
6.353 s]
[INFO] CAS Curation Interface ............................. SUCCESS [
17.284 s]
[INFO] CAS PGE Adaptor Framework .......................... SUCCESS [
31.880 s]
[INFO] CAS Installer Maven Mojo ........................... SUCCESS [
5.200 s]
[INFO] OODT :: Archetypes :: OpsUI ........................ SUCCESS [
1.831 s]
[INFO] OODT :: Archetypes :: RADiX ........................ SUCCESS [
1.496 s]
[INFO] OODT :: Archetypes ................................. SUCCESS [
0.067 s]
[INFO] CAS File Manager Browser Web App ................... SUCCESS [
14.612 s]
[INFO] CAS Workflow Manager Monitor Web App ............... SUCCESS [
5.818 s]
[INFO] CAS Product Server Web Application ................. SUCCESS [
13.191 s]
[INFO] CAS Workflow REST Services ......................... SUCCESS [
4.052 s]
[INFO] Process Control System Operator Interface Webapp ... SUCCESS [
24.666 s]
[INFO] OODT Process Control System JAX-RS service layer ... SUCCESS [
9.585 s]
[INFO] Apache OODT ........................................ SUCCESS [
0.020 s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 09:47 min
[INFO] Finished at: 2018-05-25T09:02:12-07:00
[INFO] Final Memory: 137M/1556M
[INFO]
------------------------------------------------------------------------
nonas:oodt mattmann$
```
commiting now!
> [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)
