jbonofre commented on issue #1920: URL: https://github.com/apache/activemq/issues/1920#issuecomment-4245249900
@mattrpav for me it's a bug for two reasons: 1. It's a different behavior from the "happy path". Users might be surprised because 99% of the time Jetty won't be started, but sometime the Jetty is there. If the users scan the ports, etc, it can introduce "false positive" or assuming the broker is there. 2. The WebConsole fails if Jetty is running on a slave. I think this "race condition" should be avoided and fixed. A follow up improvement could be done on WebConsole. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
