jms | A configurable CMS based on JSON schema specification | JSON Processing library

I'm not sure to fully understand your setup, but"Routes"only route HTTP traffic (On ports 80 or 443 onyl), not TCP traffic.
If you want to access your MQ server from outside the cluster, there are a few solutions, one is to create a service of type: "NodePort"

Doc: https://docs.openshift.com/container-platform/4.7/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.html

Your Service is not a NodePort Service. In your case, it should be something like

In order to remove specific messages you need to know the ID which you can get via a browse of the scheduled messages. The only other option available is to use the start and stop time options in the remove operations to remove all messages inside a range.

Best way is to take a look at existing sulu entities with tags e.g. Account or Contact.

The property can be implemented like this:

The job has huge data to process , many partition messages are publishing to queue and the aggregator of response from replyChannnel is failing with timeout of messages as all messages cant be processed in a given time.

You need to increase your timeout or add more workers. The Javadoc of MessageChannelPartitionHandler is clear about that:

There's a suspicious library com.fasterxml.jackson.databind.jar in your WEB-INF/lib. I'd kick it out, because it's probably shadowing jackson-databind-2.9.4.jar. The addMixin method exists since 2.5, so that com.fasterxml.jackson.databind.jar must be 2.4 or older.

BTW, according to https://mvnrepository.com/artifact/org.springframework/spring-web/5.1.0.RELEASE, you should use jackson 2.9.7, but maybe 2.9.4 works, too.

The application context was loading 3 times(due to code issue from our end) causing this behaviour. hope this will helpful for others. Thank you.

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.

The doc says the JMS MessageID is available as header. So you should be able to return it like this:

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.