The simple sequence of qpidd -d; qpidd -q no longer works because there is ambiguity as to which port (tcp or ssl) defines the process: $ src/qpidd --daemon $ src/qpidd --quit Cannot open /home/user/.qpidd/qpidd.5672.pid: No such file or directory $ src/qpidd --quit --port 5671 $ It appears that the port used in the pid file is chosen by the --transport option. This option appears to default to "ssl" for creation of the daemon and "tcp" for deletion of the daemon. This is also true of the stdout emission of an ephemeral port: $ src/qpidd --daemon --port 0 5671 In this case, we have no idea what port qpidd is listening on for tcp.
Fixed by r713720.
To verify, configure SSL correctly[1] and ensure module is loaded on broker. Then check that: $ src/qpidd --daemon $ src/qpidd --quit works and that: $ src/qpidd --daemon --port 0 prints a port other than 5671. [1] http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.1/html/Messaging_User_Guide/sect-Messaging_User_Guide-Authentication-Encryption_using_SSL.html Or e.g. use the test_cert_db created by make check under qpid svn.
Validated on RHEL 5.2 / 4.7 i386 / x86_64 that the issue has been fixed. On packages: qpidd-0.3.719671-1.el5 rhm-0.3.2804-4.el5 ->VERIFIED
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-0035.html