amqp | Prefer Bunny | Pub Sub library

There is an entire exchange property you can use for the channel binding for AMQP. The binding you are currently using is the operation binding.

This means that you can define it as such

form the official pika documentation

Is Pika thread safe?

Pika does not have any notion of threading in the code. If you want to use Pika with threading, make sure you have a Pika connection per thread, created in that thread. It is not safe to share one Pika connection across threads, with one exception: you may call the connection method add_callback_threadsafe from another thread to schedule a callback within an active pika connection.

so your solution can work with a single thread

Let's see the definition for Http[F, G], which is at the core of http4s:

Finally solved - you have to define a custom AMQPChannel with a custom AMQPConnection with SSL options and then set this AMQPChannel to the producer:

Boot 1.5.x and Spring AMQP 1.7.x are end of life and no longer supported.

That said, the following applies to 1.7.x too.

This situation will occur if queue recovery takes longer then 15 seconds (by default).

This is controlled by 2 container properties.

ActiveMQ Artemis has no default connection limit. I just wrote a quick test based on this which uses the Paho 1.2.5 MQTT client. It spun up 500 concurrent connections using both normal TCP and WebSockets. The test finished in less than 20 seconds with no errors. I'm just running this test on my laptop.

I noticed that your journal-buffer-timeout is 700000 which seems quite high which means you have a very low write speed of 1.43 writes per millisecond (i.e. a slow disk). The journal-buffer-timeout that is calculated, for example, on my laptop is 4000 which translates into a write-speed of 250 which is significantly faster than yours. My laptop is nothing special, but it does have an SSD. That said, SSDs are pretty common. If this low write-speed is indicative of the overall performance of your VM it may simply be too weak to handle the load you want. To be clear, this value isn't related directly to MQTT connections. It's just something I noticed while reviewing your configuration that may be indirect evidence of your issue.

The journal-buffer-timeout value is calculated and configured automatically when the instance is created. You can re-calculate this value later and configure it manually using the bin/artemis perf-journal command.

Ultimately, your issue looks environmental to me. I recommend you inspect your VM and network. TCP dumps may be useful to see perhaps how/why the connection is being reset. Thread dumps from the server during the time of the trouble would also be worth inspecting.

I fixed the issue. I got the wrong package version...

The 2.6.3.redhat-00015 version corresponds to AMQ 7.2.3 which is quite old at this point. The current AMQ release is 7.8.1. I strongly recommend you upgrade as it's likely you're hitting a bug that's already been fixed.

You may be able to work around the issue by increasing the minimum large message size (e.g using minLargeMessageSize on core client URLs or amqpMinLargeMessageSize on your AMQP acceptor). For what it's worth, the stack-trace indicates that the core JMS client (i.e. not AMQP) is in use when the exception is thrown.

Lastly, it's worth noting that the default minimum large message size is 100 KB not 2 GB as explained in the documentation.

The conversion is performed before a message is created.

Conversion errors are generally considered to be fatal - there is no point in retrying it because it will fail again.

Add an .errorChannel to the inbound adapter; its downstream flow will get an ErrorMessage for conversion errors.

However, it will also get error messages from the downstream flow too, so you will have to handle all error types there.

EDIT

You can add an error channel and handle the conversion exception on its flow. Bear in mind, though, that the message will be redelivered over and over again, with no delay.