[jira] Created: (QPID-2184) updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() JMX method

[Qpid Developers mailing list]

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-subscribe@...

[Qpid Developers mailing list]

     [ https://issues.apache.org/jira/browse/QPID-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aidan Skinner reassigned QPID-2184:
-----------------------------------

    Assignee: Aidan Skinner

> 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
>
>
> 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 Developers mailing list]

     [ https://issues.apache.org/jira/browse/QPID-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aidan Skinner updated QPID-2184:
--------------------------------

    Attachment: 0002-QPID-2184-add-a-test-case-for-the-firewall-config-u.patch
                0001-QPID-2184-add-test-for-reloading-firewall-config-in.patch

Patches with test case for this problem. Still working on a solution.

> 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 Developers mailing list]

    [ https://issues.apache.org/jira/browse/QPID-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776178#action_12776178 ]

Aidan Skinner commented on QPID-2184:
-------------------------------------

This works for per-virtualhost firewall sections, but not for server-wide ones. Although the existing unit tests do exercise this, they check in an ever so slightly different manner.

> 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 Developers mailing list]

     [ 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@...