Greetings, esteemed colleagues, I am in the process of migrating a service from the Apache ActiveMQ message broker to Apache Artemis and have encountered a specific challenge related to connection management. In ActiveMQ, I utilized the transport.closeAsync=false parameter in the transportConnector configuration to ensure synchronous socket closure between the client and the broker. This parameter was critical for ensuring resilience and consistency in message processing within our system.
Transitioning to Apache Artemis, I noticed that there doesn't seem to be a direct analogue to the transport.closeAsync parameter. It appears that Artemis closes connections asynchronously by default, which could potentially impact the behavior of our application. My questions to the community are: Is there a way in Apache Artemis to configure or adjust the connection closure mechanism to achieve behavior similar to transport.closeAsync=false in ActiveMQ? Can anyone suggest methods or practices for ensuring synchronous connection closure in Apache Artemis that could help maintain the sequence and reliability of message processing? If anyone has faced a similar challenge or can share their experience with implementing such configurations in Artemis, I would be grateful for any information or recommendations. Thank you in advance for your time and assistance.