Croway commented on issue #60: URL: https://github.com/apache/camel-jbang-examples/issues/60#issuecomment-4105926810
Thanks for the ping @christophd , the potential issue is related to changes to https://github.com/apache/camel/blob/aed48e70e583267eff1c147216a521ed7c00f1b1/test-infra/camel-test-infra-common/src/main/java/org/apache/camel/test/infra/common/services/ContainerEnvironmentUtil.java#L99 in particular, in camel test infra 4.17, citrus was using the default fixed port (9092 for kafka), and it was working as expected since ``` variables: - name: kafka.broker value: localhost:9092 ``` is defined. In Camel 4.18, [a random port is used](https://github.com/apache/camel/blob/aed48e70e583267eff1c147216a521ed7c00f1b1/test-infra/camel-test-infra-common/src/main/java/org/apache/camel/test/infra/common/services/ContainerEnvironmentUtil.java#L100C9-L100C106) but the test code still expect kafka to run on 9092. What should be the correct behaviour from citrus perspective? Using random port, or the fixed one? In case of the fixed one, somehow the property `camel.infra.fixedPort=true` should be passed to the test infra. Otherwise, in case the random port approach is correct, the test itself should be updated and the variable `${CITRUS_CAMEL_INFRA_KAFKA_BROKERS}` should be used -- 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]
