[
https://issues.apache.org/jira/browse/ARTEMIS-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298311#comment-17298311
]
Justin Bertram commented on ARTEMIS-3146:
-----------------------------------------
It's worth noting that the {{ActiveMQConnectionFactory}} implementation you're
using is from the OpenWire JMS client shipped with ActiveMQ 5.x. However, the
{{clientFailureCheckPeriod}} parameter you're attempting to use is for the core
JMS client shipped with ActiveMQ Artemis. You can't mix parameters between
these two implementations as they are not compatible at that level.
In order to investigate further you need to provide additional details. For
example, do you have a reliable way to reproduce this? Do you have thread dumps
from the client during the time the delay is observed?
> Sometimes connection.start() call get stuck
> -------------------------------------------
>
> Key: ARTEMIS-3146
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3146
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.11.0
> Reporter: Karan Aggarwal
> Priority: Critical
>
> Code:
> {code:java}
> String brokerUrl =
> failover:(tcp://192.168.xx.xx:61616,tcp://192.168.xx.xx:61616)?startupMaxReconnectAttempts=10
> ActiveMQConnectionFactory connectionFactory =
> new ActiveMQConnectionFactory(brokerUrl);
> connectionFactory.setTrustAllPackages(true);
> connection = connectionFactory.createConnection();
> connection.start();
> {code}
> We have seen that sometimes it takes 10Hrs to get out of this call.
> Tried adding {{clientFailureCheckPeriod}} attribute to broker url. But it is
> not being accepted.
> {noformat}
> Caused by: javax.jms.JMSException: Could not create Transport. Reason:
> java.lang.IllegalArgumentException: Invalid connect parameters:
> {clientFailureCheckPeriod=10000}
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
