[
https://issues.apache.org/jira/browse/ARTEMIS-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314173#comment-15314173
]
Jakub Korab commented on ARTEMIS-543:
-------------------------------------
No, the broker is Artemis 1.2.0. I am using the AMQ5 performance test tool to
place load onto it.
Jakub
> Artemis not respecting ttl-connection-override for OpenWire
> -----------------------------------------------------------
>
> Key: ARTEMIS-543
> URL: https://issues.apache.org/jira/browse/ARTEMIS-543
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
> Affects Versions: 1.2.0
> Environment: Linux
> Reporter: Jakub Korab
> Assignee: Howard Gao
>
> I run the ActiveMQ performance test module with a single consumer.
> mvn activemq-perf:consumer
> -Dfactory.brokerURL="failover:(tcp://localhost:61616)"
> -Dconsumer.destName=queue://foo -Dconsumer.recvType=count
> -Dconsumer.recvCount=10000
> I can see a consumer appearing in Artemis on the queue under test via JMX.
> I interrupt the test with a ctrl-c, and the consumer count stays at 1 in JMX.
> I re-run the same consumer command again, and get the following error:
> javax.jms.InvalidClientIDException: Broker: monolith - Client: JmsConsumer0
> already connected from /127.0.0.1:52525
> I have added the following to the broker.xml config:
> <connection-ttl-override>100</connection-ttl-override>
> This seems to have no effect, and does not clean up the consumer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
