Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

2016-05-19 Thread Dilshani Subasinghe
Noted and appreciate quick response. Regards, Dilshani On Thu, May 19, 2016 at 11:31 AM, Nuwan Wimalasekara wrote: > Log is corrected as bellow when having below parameter values. > > locked="false">1 > locked="false">6 > > [2016-05-19 11:23:20,338] ERROR -

Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

2016-05-19 Thread Nuwan Wimalasekara
Log is corrected as bellow when having below parameter values. 1 6 [2016-05-19 11:23:20,338] ERROR - ServiceTaskManager Reconnection attempt : 1 for service : JmsProxy failed. Next retry in 20 seconds [2016-05-19 11:23:45,357] ERROR - ServiceTaskManager Reconnection attempt : 2 for

Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

2016-05-18 Thread Dilshani Subasinghe
Noted and reported a jira [1] to cover up fixing the issue. [1] https://wso2.org/jira/browse/ESBJAVA-4625 Regards, Dilshani On Thu, May 19, 2016 at 10:47 AM, Nuwan Wimalasekara wrote: > HI Dilshani, > > On Wed, May 18, 2016 at 6:27 PM, Dilshani Subasinghe

Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

2016-05-18 Thread Nuwan Wimalasekara
HI Dilshani, On Wed, May 18, 2016 at 6:27 PM, Dilshani Subasinghe wrote: > Hi Nuwan, > > Thanks a lot for your clarification. But need more explanation on your > comments. > > 1. *if the user define only transport.jms.InitialReconnectDuration, It > will always be multiplied

Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

2016-05-18 Thread Dilshani Subasinghe
In previous mail, I am referring both points to same thing. Please consider, it should be correct as follows: 1. *transport.jms.ReconnectProgressFactor is set to 2 by default to increasing the reconnect interval exponential until it reach to transport.jms.MaxReconnectDuration. * 2. *if the user

Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

2016-05-18 Thread Dilshani Subasinghe
Hi Nuwan, Thanks a lot for your clarification. But need more explanation on your comments. 1. *if the user define only transport.jms.InitialReconnectDuration, It will always be multiplied by the transport.jms.ReconnectProgressFactor until it reach to transport.jms.MaxReconnectDuration. * We can

Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

2016-05-18 Thread Nuwan Wimalasekara
Hi Dilshani, If the user need to define constant interval for reconnect, user can define transport.jms.ReconnectInterval. Then it will wait defined value for each reconnect attempt. if the user define only transport.jms.InitialReconnectDuration, It will always be multiplied by the

[Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"

2016-05-18 Thread Dilshani Subasinghe
Hi ESB Team, When consider about "JMS connection factory parameters" [1] , user can define "transport.jms.InitialReconnectDuration" parameter to give time duration which will define initial reconnection time after broken JMS connection. But the given value will be multiply with 2. That 2 is