[ https://issues.apache.org/jira/browse/ARTEMIS-4709?focusedWorklogId=912807&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-912807 ]
ASF GitHub Bot logged work on ARTEMIS-4709: ------------------------------------------- Author: ASF GitHub Bot Created on: 03/Apr/24 10:32 Start Date: 03/Apr/24 10:32 Worklog Time Spent: 10m Work Description: gtully commented on code in PR #4871: URL: https://github.com/apache/activemq-artemis/pull/4871#discussion_r1549441701 ########## artemis-server/src/main/java/org/apache/activemq/artemis/core/server/plugin/impl/ConnectionPeriodicExpiryPlugin.java: ########## @@ -0,0 +1,130 @@ +/** + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * <p> + * http://www.apache.org/licenses/LICENSE-2.0 + * <p> Review Comment: thanks Issue Time Tracking ------------------- Worklog Id: (was: 912807) Time Spent: 0.5h (was: 20m) > Add a plugin to provide periodic expiry of connections on a per acceptor basis > ------------------------------------------------------------------------------ > > Key: ARTEMIS-4709 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4709 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker > Affects Versions: 2.33.0 > Reporter: Gary Tully > Assignee: Gary Tully > Priority: Major > Fix For: 2.34.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When credential rotation needs to be enforced, active connections need to be > terminated on some timeline to ensure credentials are reevaluated. There are > management apis that can be used but these require some intervention. > In addition to enforce some SLA around duration of connections, having an > easy way to limit connections to a given maximum period can be helpful. > A plugin that will be applied on an per acceptor basis, that can be used to > disconnect connections that have lived for some period can provide a nice > building block for these use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)