Random STOMP Websocket client deconnection from Artemis

Hi ! We encounter random issue with the STOMP WebSocket connection in Artemis : sometimes the clients are disconnected of a channel, due to a ConcurrentModificationException. As the client is not aware that it has been disconnected, it cannot reconnect and it does not received any message any

RE: Artemis JMS queue paging prevents JMS consumer to receive newly added message

Youyo, I think this is expected behaviour. As long as there are messages in memory, the paging files are not swapped-in yet. This means that you might not get the messages with the desired colour in time when messages of other colours are still in memory. A common solution is to use a single

Artemis JMS queue paging prevents JMS consumer to receive newly added message

Hi, While investigating performance related issues, we discovered that once Artemis JMS queue starts paging, newly produced message are not visible (within 60 seconds receive timeout) until most of the messages in the front (of that queue) are consumed. We have Artemis (2.11.0) in

RE: [EXTERNAL] RE: Artemis JMS queue paging prevents JMS consumer to receive newly added message

Thanks you very much Dondorp. We will certainly look into your suggestion. Youyu -Original Message- From: Dondorp, Erwin Sent: Friday, November 5, 2021 12:40 PM To: users@activemq.apache.org Subject: [EXTERNAL] RE: Artemis JMS queue paging prevents JMS consumer to receive newly added