[ 
https://issues.apache.org/jira/browse/ARTEMIS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383172#comment-15383172
 ] 

ASF GitHub Bot commented on ARTEMIS-611:
----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/643

    ARTEMIS-611 refactor STOMP cxn TTL + heart-beat

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-611

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/643.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #643
    
----
commit dc76e2a6a00964990fa50ec091d96473616aba87
Author: jbertram <[email protected]>
Date:   2016-07-18T21:34:22Z

    ARTEMIS-640 Allow config of cxn TTL check interval
    
    Add connection-ttl-check-interval configuration attribute to allow
    control of how frequently connection TTL checks are performed.

commit f66472b1f319f79785649ae5c0bb8faa661da7d0
Author: jbertram <[email protected]>
Date:   2016-07-15T13:36:24Z

    ARTEMIS-611 refactor STOMP cxn TTL + heart-beat
    
    Adds 3 new URI properties for STOMP acceptors to allow finer grained
    configuration of heart-beat / connection-TTL behavior.

----


> STOMP 1.0 consumers are killed after some time
> ----------------------------------------------
>
>                 Key: ARTEMIS-611
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-611
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>            Reporter: Lionel Cons
>            Assignee: Justin Bertram
>             Fix For: 1.4.0
>
>
> With the default configuration, a STOMP 1.0 consumer that subscribes to a 
> destination and waits for messages to come gets killed after some time (in 
> case there are no messages coming).
> The broker logs:
> {code}
> 2016-07-04 09:34:31,260 [org.apache.activemq.artemis.core.server] WARN 
> AMQ222067: Connection failure has been detected: AMQ119014: Did not receive 
> data from /192.168.47.193:54716. It is likely the client has exited or 
> crashed without closing its connection, or the network between the server and 
> client has failed. You also might have configured connection-ttl and 
> client-failure-check-period incorrectly. Please check user manual for more 
> information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]
> 2016-07-04 09:34:31,261 [org.apache.activemq.artemis.core.server] WARN 
> AMQ222061: Client connection failed, clearing up resources for session 
> 9ae78c80-41b9-11e6-8647-02163e018512
> 2016-07-04 09:34:31,263 [org.apache.activemq.artemis.core.server] WARN 
> AMQ222107: Cleared up resources for session 
> 9ae78c80-41b9-11e6-8647-02163e018512
> {code}
> STOMP 1.0 clients do not support heart-beats and the broker should not kill 
> connections after some period of inactivity.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to