On Sun, Apr 1, 2018, 11:05 PM Rajesh Malla <mallara...@gmail.com> wrote:
> Thank you, actually we searched but not found any bug fix on inactivity > monitor. there is only one bug which is > https://issues.apache.org/jira/browse/AMQ-6877 on http connector with > queue > prefetch 0. this we applied and queue-prefetch is working fine. > Did you see my message where I indicated that http://issues.apache.org/jira/browse/AMQ-6262 was the one Tim was referring to? can you please help us. because in our case inactivity monitor closes > connection exactly after 300000 seconds. > one more question, how to pass this inactivity configuration through query > parameter for http transport connector ? > do we need to provide it as wireFormat.maxInactivityDurationInitalDelay or > transport.wireFormat.maxInactivityDuration ? > That depends on your URI. If you have a failover URI and you want to specify the maxInactivityDuration on the failover transport and have it applied to each inner transport, you would use the "transport." prefix. If you're not using the failover transport, or if you want to specify the maxInactivityDuration option directly on each inner URI, you would not use the "transport." prefix. Tim >
