qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Stitcher (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-4810) If ssl/tcp multiplexing is enabled and ssl initialisation fails tcp doesn't start either
Date Thu, 02 May 2013 19:54:16 GMT

     [ https://issues.apache.org/jira/browse/QPID-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Stitcher updated QPID-4810:
----------------------------------

    Summary: If ssl/tcp multiplexing is enabled and ssl initialisation fails tcp doesn't start
either  (was: If ssl/tcp multiplexing is enabled and ssl initialisatino fails tcp doesn't
start either)
    
> If ssl/tcp multiplexing is enabled and ssl initialisation fails tcp doesn't start either
> ----------------------------------------------------------------------------------------
>
>                 Key: QPID-4810
>                 URL: https://issues.apache.org/jira/browse/QPID-4810
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.14
>            Reporter: Andrew Stitcher
>            Assignee: Andrew Stitcher
>
> To reproduce:
> qpidd --ssl-cert-db non-existent_file --ssl-port 5672
> This will try to start ssl, fail and then not start tcp either.
> In versions prior to 0.23 it will also just sit there dumbly waiting, doing nothing,
not exiting (this issue was fixed in trunk r1478398).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message