[jira] [Work logged] (ARTEMIS-3699) EmbeddedActiveMQ port configuration

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-3699?focusedWorklogId=734143&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-734143 ]

ASF GitHub Bot logged work on ARTEMIS-3699:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 28/Feb/22 19:53
            Start Date: 28/Feb/22 19:53
    Worklog Time Spent: 10m 
      Work Description: jbertram opened a new pull request #3969:
URL: https://github.com/apache/activemq-artemis/pull/3969


   It sometimes makes sense to set an acceptor's port to 0 to allow the JVM
   to select an ephemeral port (e.g. in embedded integration tests). This
   commit adds a new getter on NettyAcceptor so tests can programmtically
   determine the ephemeral port used by the acceptor.
   
   This commit also changes the ACCEPTOR_STARTED notification and the
   related logging to clarify the actual port value where clients can
   connect.


-- 
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: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 734143)
    Remaining Estimate: 0h
            Time Spent: 10m

> EmbeddedActiveMQ port configuration
> -----------------------------------
>
>                 Key: ARTEMIS-3699
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3699
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Robin
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When creating an instance of EmbeddedActiveMQ the port that the broker binds to is taken from the acceptor uri supplied to the configuration. Afterwards there is no easy way to get the port out of the broker instance. In addition, it would have been nice if one could provide 0 for port to have it start up on a random available port. Could this be implemented?
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)