[ 
https://issues.apache.org/jira/browse/DISPATCH-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186001#comment-17186001
 ] 

ASF GitHub Bot commented on DISPATCH-1764:
------------------------------------------

ted-ross commented on a change in pull request #837:
URL: https://github.com/apache/qpid-dispatch/pull/837#discussion_r478580017



##########
File path: python/qpid_dispatch_internal/management/config.py
##########
@@ -331,7 +331,7 @@ def configure(attributes):
                     ssl_profile_name = a.get('name')
                     displayname_service.add(ssl_profile_name, 
display_file_name)
 
-    # Configure remaining singleton types; don't configure listeners
+    # Configure remaining singleton types
     for e in config.entities:
         if not e['type'] == 'org.apache.qpid.dispatch.listener':

Review comment:
       Should there be a check for connectors here as well?




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


> At boot time config processing should create connectors later
> -------------------------------------------------------------
>
>                 Key: DISPATCH-1764
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1764
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Management Agent
>    Affects Versions: 1.13.0
>            Reporter: Charles E. Rolke
>            Assignee: Charles E. Rolke
>            Priority: Major
>
> Similar to DISPATCH-1760 opening connectors too soon may expose the router to 
> floods of traffic before the initial configuration has completed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to