[ 
https://issues.apache.org/jira/browse/ARTEMIS-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell closed ARTEMIS-1976.
-----------------------------------
    Resolution: Invalid

You are apparently using Artemis 2.6.2, which does not contain the 
functionality from ARTEMIS-1924 according to the JIRA.

Seperately, you are misinterpretting the actual activity shown by the logs. 
They show the python client *receiving* lots of heartbeats (probably every 
750ms), which the broker has sent to satisfy the python clients 1500ms 
idle-timeout value advertised in its Open frame (because you set the actual 
timeout to 3000ms). The client will be sending every 15sec to satisfy the 
brokers advertised 30sec Open frame idle-timeout (based on its default 60sec 
actual timeout).

The final logs, from a JMS client, dont show any heartbeats because actual 
traffic is occurring in both directions (presumably from a consumer recieve 
call with 3sec timeout completing without any message being available). There 
will be no heartbeats in that case, since it would require 15 seconds of 
inactivity in either direction.

> AMQP IdleTimeout ignoring user defined value
> --------------------------------------------
>
>                 Key: ARTEMIS-1976
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1976
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Oleg Sushchenko
>            Priority: Major
>
> Steps:
>  * configure broker.xml with amqpIdleTimeout=4000 value:
> {code:java}
> <acceptor 
> name="amqp">tcp://0.0.0.0:5672?amqpIdleTimeout=4000;tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpLowCredits=300</acceptor>
>  {code}
>  
>  * start broker
>  * connect to broker with client
>  * check broker logs
> Expected result:
>  * I get Empty Frames every 2 seconds
> Actual results:
>  * Seems that value is not working because I get an Empty Frame every 15 
> seconds
> {code:java}
> 2018-07-10 10:08:29,282 FINE  [proton.trace] IN: CH[0] : Empty Frame
> 2018-07-10 10:08:44,282 FINE  [proton.trace] IN: CH[0] : Empty Frame
> 2018-07-10 10:08:59,282 FINE  [proton.trace] IN: CH[0] : Empty Frame
> 2018-07-10 10:09:14,282 FINE  [proton.trace] IN: CH[0] : Empty Frame
> 2018-07-10 10:09:29,283 FINE  [proton.trace] IN: CH[0] : Empty Frame
> 2018-07-10 10:09:44,282 FINE  [proton.trace] IN: CH[0] : Empty Frame
> 2018-07-10 10:09:59,282 FINE  [proton.trace] IN: CH[0] : Empty Frame
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to