Thank you @marc . We are using JNDI and we are setting reconnect retries+wait properties on connection factory as well as Solace_JMS_JNDI_ReconnectRetries property at client side. But it is taking server value when trying to re-connect. Solace_JMS_JNDI_ConnectRetries is working as expected ( it is taking client side value and trying to connect ). But we are not able to understand why client’s ReconnectRetries is not overriding server’s value.
we are using below JNDI properties at client side
Solace_JMS_JNDI_ReconnectRetryWait
Solace_JMS_JNDI_ConnectRetriesPerHost
Solace_JMS_JNDI_ConnectTimeout
Solace_JMS_JNDI_ConnectRetries
Solace_JMS_JNDI_ReconnectRetries
and all properties are set at connection factory level too. While connecting for the first time , logs shows client side values but when re-connecting , it shows server’s value. Expectation is to make re-connect attempt as per the value used in client side. Could you please help us to understand the issue ?? ( Please let me know if you want any other details )