activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <christian.po...@gmail.com>
Subject Re: Fix for AMQ-3915 undone by fix for AMQ-4033
Date Fri, 10 May 2013 13:56:56 GMT
Yah, could be unintentional. Can you make this comment on the
https://issues.apache.org/jira/browse/AMQ-4033 JIRA?


On Wed, May 8, 2013 at 4:33 PM, Benjamin Jansen
<bjansen-activemq@w007.org>wrote:

> Hello,
>
> I have been researching how to restrict JMX to bind to a loopback address,
> so that it is not accessible off the box, but is easily accessible to a
> different user account (our software, which embeds ActiveMQ, is running as
> Local System). Based on my research, such a thing is not directly supported
> by JVM configuration. So, I was pleased to discover AMQ-3915 [1] and that
> it was marked fixed for the 5.7 release of ActiveMQ.
>
> Unfortunately, when I tried setting connectorHost, it appeared to have no
> effect. I dug in and discovered that a subsequent bug fix, for AMQ-4033
> [2], actually undid the fix for AMQ-3915 [3]. Was this intentional?
>
> Thanks,
> Ben Jansen
>
> 1: https://issues.apache.org/jira/browse/AMQ-3915
> 2: https://issues.apache.org/jira/browse/AMQ-4033
> 3: starting with line 500 at
> https://fisheye6.atlassian.com/changelog/activemq?cs=1382852




-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message