You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/09/29 22:54:00 UTC
[jira] [Commented] (QPID-8306) [Broker-J] Add ability to update TLS
transport on AMQP port after changing keystore, trustores or other TLS
related attributes
[ https://issues.apache.org/jira/browse/QPID-8306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940559#comment-16940559 ]
ASF subversion and git services commented on QPID-8306:
-------------------------------------------------------
Commit 46c90b50f50adea6d5d037e5cb9e8b16832cf5e6 in qpid-broker-j's branch refs/heads/7.1.x from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=46c90b5 ]
QPID-8306: [Broker-J] Add operation to update port TLS support
This closes #31
(cherry picked from commit ce1cb00c795a70ed33f8717250f0ab61838d23f5)
> [Broker-J] Add ability to update TLS transport on AMQP port after changing keystore, trustores or other TLS related attributes
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-8306
> URL: https://issues.apache.org/jira/browse/QPID-8306
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.5
>
>
> Broker restart is required after changes to AMQP port TLS attributes, keystore and trust stores. It should be possible to update TLS transport without affecting existing AMQP connections.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org