Closed mschorsch closed 1 year ago
/cc @geoand (devservices), @stuartwdouglas (devservices)
@cescoffier any idea who we should ping about this?
@geoand No, not really. I was afraid one day they would change the parameters.
I would recommend configuring the extra-args to:
quarkus.amqp.devservices.exta-args=--no-autotune --mapped --no-fsync --relax-jolokia
@geoand No, not really. I was afraid one day they would change the parameters.
I would recommend configuring the extra-args to:
quarkus.amqp.devservices.exta-args=--no-autotune --mapped --no-fsync --relax-jolokia
Unfortunately, this does not seem to fix the problem.
Just tested it works.... without the typo:
quarkus.amqp.devservices.extra-args=--no-autotune --mapped --no-fsync --relax-jolokia
Just tested it works.... without the typo:
quarkus.amqp.devservices.extra-args=--no-autotune --mapped --no-fsync --relax-jolokia
Thanks @cescoffier. I can confirm that it works without the typo 👍
Describe the bug
In one of our projects, we use the amqp dev services to start an
quay.io/artemiscloud/activemq-artemis-broker
. With version1.0.22
we get the following exception, version1.0.21
starts normally:Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
Ubuntu 22.04.3 LTS
Output of
java -version
Java 17
GraalVM version (if different from Java)
No response
Quarkus version or git rev
3.4.1.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Maven
Additional information
No response