MQ connection overridden


Currently we are overriding the MQ connection related attributes during run-time for MQ delilvery.
Is it advantage to override the connection.
Will it poses a performance issue, as we will not be able to use the connection pooling capability.

Please provide your suggestions whether to go for overridden connection.

Actually, you will take advantage of the connection pooling unless you are using any of the internal services that are not exposed directly through the APIs.

My suggestion. STOP RIGHT NOW.

If you use override, you’re not simply overriding one setting, but ALL settings. You won’t be able to enforce minimum, maximum, timeout, or any of the settings you configure through the Admin UI.

This was a HUGE issue for us last year as we were unable to limit the maximum connections to a system.