You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2016/01/08 00:56:39 UTC

[jira] [Updated] (PROTON-398) pn_messenger_subscribe() fails to create a listener

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

Justin Ross updated PROTON-398:
-------------------------------
    Labels: messenger  (was: )

> pn_messenger_subscribe() fails to create a listener
> ---------------------------------------------------
>
>                 Key: PROTON-398
>                 URL: https://issues.apache.org/jira/browse/PROTON-398
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c, proton-j
>    Affects Versions: 0.5
>         Environment: linux (fedora 14 64bit)
>            Reporter: Marc Berkowitz
>              Labels: messenger
>
> Running a local ActiveMQ server, release 5.8.0, default configuration.
> The documented "listen all' feature of the python example fails with the error
> 'bind: Address already in use.'
> cd  proton/examples/messenger/py;
>   ./recv.py  amqp://localhost/test   --  subscribes to a specified address, and works
>   ./recv.py   OR  ./recv.py amqp://~localhost   -- listens to all addresses, and fails.
>  py/recv.py amqp://~localhost
> Traceback (most recent call last):
>   File "py/recv.py", line 41, in <module> mng.subscribe(a)
>   File "/usr/lib64/python2.7/site-packages/proton.py", line 371, in subscribe self._check(PN_ERR)
>   File "/usr/lib64/python2.7/site-packages/proton.py", line 228, in _check raise exc("[%s]: %s" % (err, pn_messenger_error(self._mng)))
> proton.MessengerException: [-2]: unable to subscribe to source: amqp://~localhost 
> (bind: Address already in use)
> Same error from a similar java program, which calls proton-j.
> Both fail trying to bind to localhost:5672, which is held by the local activemq server.
> Must either fix the ~ADDRESS feature or remove it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)