[
https://issues.apache.org/jira/browse/UIMA-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519378#comment-14519378
]
Lou DeGenaro commented on UIMA-4335:
------------------------------------
Code change added to now produce:
bash-4.1$ ./viaducc /bin/echo hello
...
Managed Reservation 7 submitted.
id:7 location:5728@myhost
id:7 state:WaitingForResources
[1] hello
id:7 remote:5875@myhost-4
id:7 state:Running
id:7 state:Completed
id:7 rationale:code=0
id:7 rc:0
That is, remote location is displayed prior to state Running. However, since a
different channel (socket) is used for user's output, it my arrive prior to
DUCC status message that reports Running. It is a race!
> DUCC CLI Monitor (CLI) has out-of-order messages
> ------------------------------------------------
>
> Key: UIMA-4335
> URL: https://issues.apache.org/jira/browse/UIMA-4335
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Priority: Minor
> Fix For: 2.0.0-Ducc
>
>
> 1. discard "remote"
> 2. replace with "Assigned"
> degenaro@uima-ducc-vm:~/hello$ java-viaducc Hello
> /home/degenaro/ducc/versions/apache-uima-ducc-2.0.0-SNAPSHOT/bin/ducc_process_submit
> --attach_console --process_memory_size 15 --scheduling_class fixed
> --description java-viaducc --wait_for_completion --cancel_on_interrupt
> --working_directory /home/degenaro/hello --process_executable
> /home/degenaro/local/sun/jdk1.7.0_45/bin/java --process_executable_args
> "'Hello'"
> Managed Reservation 23 submitted.
> id:23 location:31712@uima-ducc-vm
> id:23 state:WaitingForResources
> [1] Hello
> id:23 state:Running
> id:23 remote:31980@uima-ducc-demo-4
> id:23 state:Completed
> id:23 rationale:code=0
> id:23 rc:0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
