[ 
https://issues.apache.org/jira/browse/DISPATCH-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887836#comment-15887836
 ] 

ASF GitHub Bot commented on DISPATCH-644:
-----------------------------------------

GitHub user adel-boutros opened a pull request:

    https://github.com/apache/qpid-dispatch/pull/145

    DISPATCH-644 - Fix daemon mode incorrectly exiting while dispatch rou…

    
    
    Signed-off-by: aboutros <[email protected]>

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/adel-boutros/qpid-dispatch-1 master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/qpid-dispatch/pull/145.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 #145
    
----
commit 67bf5013fbcd16c5f5f335dfc16f442745890356
Author: aboutros <[email protected]>
Date:   2017-02-27T16:59:20Z

    DISPATCH-644 - Fix daemon mode incorrectly exiting while dispatch router 
has started
    
    Signed-off-by: aboutros <[email protected]>

----


> Fix qdrouterd generating exit code 1 because of a pipe issue in Daemon mode
> ---------------------------------------------------------------------------
>
>                 Key: DISPATCH-644
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-644
>             Project: Qpid Dispatch
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>            Reporter: Adel Boutros
>         Attachments: 0001-Fix-writing-to-pipe.patch
>
>
> When starting the qdrouterd in Daemon mode, the pipe is not receiving "OK". 
> So the parent process considers the child process failed to start the 
> dispatch router and exits with exit_code 1 while the router has actually 
> started correctly. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to