falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-174) bind activemq to all interfaces rather than just localhost
Date Thu, 07 Nov 2013 07:28:23 GMT

    [ https://issues.apache.org/jira/browse/FALCON-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815731#comment-13815731
] 

Shwetha G S commented on FALCON-174:
------------------------------------

This active mq endpoint is also used by process/feed jobs to publish the messages. Since these
jobs run on task trackers, and need to connect to activemq thats running with falcon server,
the activemq endpoint need to contain the actual hostname(not localhost/0.0.0.0). So, can
this bind happen with the actual hostname as well?

> bind activemq to all interfaces rather than just localhost
> ----------------------------------------------------------
>
>                 Key: FALCON-174
>                 URL: https://issues.apache.org/jira/browse/FALCON-174
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Arpit Gupta
>            Assignee: Arpit Gupta
>            Priority: Minor
>         Attachments: FALCON-174-v1.patch
>
>
> Currently we bind activemq to localhost. If we bind to 0.0.0.0 then other falcon server
could use the active mq started by another falcon sever.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message