[
https://issues.apache.org/jira/browse/QPID-8795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18145615#comment-18145615
]
ASF GitHub Bot commented on QPID-8795:
--------------------------------------
dakirily opened a new pull request, #476:
URL: https://github.com/apache/qpid-broker-j/pull/476
This PR addresses JIRA
[QPID-8795](https://issues.apache.org/jira/browse/QPID-8795), enforcing
connection limits across provider lifecycle changes
> [Broker-J] Connection limits can become unenforced or stale across provider
> lifecycle changes
> ---------------------------------------------------------------------------------------------
>
> Key: QPID-8795
> URL: https://issues.apache.org/jira/browse/QPID-8795
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-broker-10.1.0, qpid-java-broker-10.1.1
> Reporter: Daniil Kirilyuk
> Assignee: Daniil Kirilyuk
> Priority: Major
> Fix For: qpid-java-broker-10.2.0
>
>
> Connection limits can become unenforced or stale during broker startup,
> virtual host restarts, and provider updates. Virtual hosts may accept
> connections while an applicable provider is initializing, and later provider
> state changes may not refresh cached limiters. Restarting a virtual host can
> retain outdated rules and lose listeners, preventing broker-level changes and
> subsequent provider updates from taking effect. Invalid rule updates or
> failed file reloads can also discard previously valid rules, unintentionally
> disabling enforcement.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]