Description:

Found below issues in Axis2 RabbitMQ Transport,

• The thread named HotDeploymentSchedulerThread does not have a timeout if it would come to the “Waiting on Condition” state
• The following parameter is not set properly to customize RabbitMQ connections for a particular ConnectionFactory

    public RabbitMQConnectionPool(RabbitMQConnectionFactory factory, int poolSize) {
        super(factory);
        this.setTestOnBorrow(true);
        this.setMaxTotal(poolSize);
        this.setMaxTotalPerKey(poolSize);
    }

• The Toml file configuration for increasing pool size value does not reflect in the codebase

[transport.rabbitmq]
sender_enable = true
listener_enable = true

[[transport.rabbitmq.listener]]
name = "AMQPConnectionFactory"
parameter.hostname = "localhost"
parameter.port = 5672
parameter.username = "guest"
parameter.password = "guest"
parameter.retry_interval = "10s"
parameter.retry_count = 5
parameter.connection_pool_size = 100

Steps to reproduce:

Please follow the below steps to reproduce the above mentioned issues.

1. Create 10 sample RabbitMQ proxy listeners
2. Update the MI v4.1.0 to update level 52
3. Setup a RabbitMQ v3.12.6 or v3.11.13
4. Enable RabbitMQ Listener configuration
5. Deploy above created RabbitMQ proxy listeners

Expected behaviour:

• should be able to deploy all the RabbitMQ proxy listeners without any issue
• If the RabbitMQ proxy listeners were in separate CAR files(such as 5 CARs each CAR has 2 RabbitMQ proxy listeners) all the CAR files should be deployed

Current behaviour:

• only 8 RabbitMQ proxy listeners will be deployed
• If the RabbitMQ proxy listeners were in separate CAR files(such as 5 CARs each CAR has 2 RabbitMQ proxy listeners) then only 4 CARs will be deployed

Thank you,
Pasindu G.