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
Fix For: 0.6
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-subscr...@qpid.apache.org
