You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <qp...@incubator.apache.org> on 2008/11/13 14:19:44 UTC
[jira] Created: (QPID-1459) port confusion when ssl module is
loaded
port confusion when ssl module is loaded
----------------------------------------
Key: QPID-1459
URL: https://issues.apache.org/jira/browse/QPID-1459
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: M4
Reporter: Gordon Sim
Assignee: Gordon Sim
Fix For: M4
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-1459) port confusion when ssl module is
loaded
Posted by "Gordon Sim (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim resolved QPID-1459.
------------------------------
Resolution: Fixed
Fixed by r713720.
> port confusion when ssl module is loaded
> ----------------------------------------
>
> Key: QPID-1459
> URL: https://issues.apache.org/jira/browse/QPID-1459
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: M4
> Reporter: Gordon Sim
> Assignee: Gordon Sim
> Fix For: M4
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.