You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org> on 2009/11/12 00:00:40 UTC
[jira] Resolved: (QPID-2184) updated ip whitelisting / firewall
config doesnt take effect after SIGHUP or reloadSecurityConfiguration() JMX
method
[ https://issues.apache.org/jira/browse/QPID-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner resolved QPID-2184.
---------------------------------
Resolution: Fixed
Fixed in r835115
> updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() JMX method
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2184
> URL: https://issues.apache.org/jira/browse/QPID-2184
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.6
> Reporter: Robbie Gemmell
> Assignee: Aidan Skinner
> Fix For: 0.6
>
> Attachments: 0001-QPID-2184-add-test-for-reloading-firewall-config-in.patch, 0002-QPID-2184-add-a-test-case-for-the-firewall-config-u.patch
>
>
> updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() via JMX.
> Changing an existing rule or adding a new rule to reverse the current allow/deny behaviour against a particular client machine does not take effect against new client connections, depsite the SIGHUP / JMX invoked security configuration reload occurring and completing without any Exceptions. Restarting the broker with the updated configuration in place results in the expected behaviour being attained.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org