Skip to content

ActiveMQHealthCheck and failover transport #24

Description

@DrMattFaulkner

Hi,

In my very simple test scenario I am using a failover transport layer for the client URI. This URI does not have a maxReconnectAttempts set so will block until it can get a connection.

When there are no brokers up this means the healthcheck API blocks indefinitely.

The URI could be changed to include a maxreconnect (i.e., maxReconnectAttempts=X), but that will affect actual production clients where blocking until we have a connection is a desired behaviour.

Is there any way to prevent the healthcheck from blocking?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions