qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomas Vavricka (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPIDJMS-114) When failover.initialReconnectDelay is set, client cannot connect
Date Wed, 23 Sep 2015 07:33:04 GMT

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

Tomas Vavricka updated QPIDJMS-114:
-----------------------------------
    Description: 
When option failover.initialReconnectDelay is set to other value than 0, client hangs up during
creating a session.

{{session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE);}}


Connection string used:

{{failover:(amqp://server:21415?amqp.saslMechanisms=PLAIN)?failover.initialReconnectDelay=1&failover.maxReconnectAttempts=5&failover.reconnectDelay=60000&jms.username=admin&jms.password=admin&jms.forceAsyncSend=false&jms.alwaysSyncSend=true&jms.sendAcksAsync=false}}

Broker was started day before test and broker still is running. In broker logs there are no
signs about connection and client is just stuck (i waited 10 minutes).

Broker is qpidd - the Qpid AMQP Message Broker Daemon, versions of qpidd and mrg-m below.
{quote}
$ qpidd --version
qpidd (qpid-cpp) version 0.22
$ rpm -qa | grep mrg-m
mrg-messaging-release-3.0.0-3.el6.noarch
{quote}

  was:
When option failover.initialReconnectDelay is set to other value than 0, client hangs up during
creating a session.

{{session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE);}}


Connection string used:

{{failover:(amqp://server:21415?amqp.saslMechanisms=PLAIN)?failover.initialReconnectDelay=1&failover.maxReconnectAttempts=5&failover.reconnectDelay=60000&jms.username=admin&jms.password=admin&jms.forceAsyncSend=false&jms.alwaysSyncSend=true&jms.sendAcksAsync=false}}

Broker is qpidd - the Qpid AMQP Message Broker Daemon, versions of qpidd and mrg-m below.
{quote}
$ qpidd --version
qpidd (qpid-cpp) version 0.22
$ rpm -qa | grep mrg-m
mrg-messaging-release-3.0.0-3.el6.noarch
{quote}


> When failover.initialReconnectDelay is set, client cannot connect
> -----------------------------------------------------------------
>
>                 Key: QPIDJMS-114
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-114
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.5.0, 0.6.0
>         Environment: Java 1.7
>            Reporter: Tomas Vavricka
>            Assignee: Timothy Bish
>              Labels: connection
>
> When option failover.initialReconnectDelay is set to other value than 0, client hangs
up during creating a session.
> {{session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE);}}
> Connection string used:
> {{failover:(amqp://server:21415?amqp.saslMechanisms=PLAIN)?failover.initialReconnectDelay=1&failover.maxReconnectAttempts=5&failover.reconnectDelay=60000&jms.username=admin&jms.password=admin&jms.forceAsyncSend=false&jms.alwaysSyncSend=true&jms.sendAcksAsync=false}}
> Broker was started day before test and broker still is running. In broker logs there
are no signs about connection and client is just stuck (i waited 10 minutes).
> Broker is qpidd - the Qpid AMQP Message Broker Daemon, versions of qpidd and mrg-m below.
> {quote}
> $ qpidd --version
> qpidd (qpid-cpp) version 0.22
> $ rpm -qa | grep mrg-m
> mrg-messaging-release-3.0.0-3.el6.noarch
> {quote}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message