You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2023/10/21 12:39:00 UTC
[jira] [Commented] (AMQ-9365) Use different transport port number in tests and JMX instances
[ https://issues.apache.org/jira/browse/AMQ-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778072#comment-17778072 ]
Jean-Baptiste Onofré commented on AMQ-9365:
-------------------------------------------
We should do the same for JMX instance to avoid:
{code:java}
[ERROR] Run 2: KahaDBPendingMessageCursorTest>AbstractPendingMessageCursorTest.startBroker:91->setUpBroker:98->AbstractPendingMessageCursorTest.setUpBroker:112 » InstanceAlreadyExists org.apache.activemq:type=Broker,brokerName=localhost {code}
> Use different transport port number in tests and JMX instances
> --------------------------------------------------------------
>
> Key: AMQ-9365
> URL: https://issues.apache.org/jira/browse/AMQ-9365
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Test Cases
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 6.0.1
>
>
> On Jenkins, often, we have several tests executed on the same executor. Then, we have port number conflict between test:
> {code:java}
> java.net.BindException: Address already in use {code}
> That's especially true on the {{org.apache.activemq.transport.tcp.TcpTransportServer.bind}} method.
> In the test, we should test the port number and use an unique port to avoid conflict.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)