activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (AMQ-2319) Specifying an IP in a transport URI doesn't make the resulting listen socket use that IP only
Date Wed, 08 Jul 2009 09:10:07 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52727#action_52727
] 

Gary Tully edited comment on AMQ-2319 at 7/8/09 2:08 AM:
---------------------------------------------------------

check out the comments on https://issues.apache.org/activemq/browse/AMQ-2094, the current
behavior on trunk (5.3-SNAP) is as you request.

      was (Author: gtully):
    check out the comments on this issue, the current behavior on trunk (5.3-SNAP) is as you
request.
  
> Specifying an IP in a transport URI doesn't make the resulting listen socket use that
IP only
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2319
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2319
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.2.0
>         Environment: Linux jdk6
>            Reporter: Marshall Pierce
>            Priority: Minor
>
> The following configuration
> <transportConnector name="openwire" uri="tcp://127.0.0.1:61616" />
> yields the following output from netstat:
> tcp6       0      0 :::61616                :::*                    LISTEN     6528/java
> Instead of listening on :: (the ipv6 equivalent of 0.0.0.0), it should only listen on
127.0.0.1

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message