Skip Menu |

This queue is for tickets about the Net-Stomp CPAN distribution.

Report information
The Basics
Id: 96767
Status: resolved
Priority: 0/
Queue: Net-Stomp

Owner: DAKKAR [...]
Requestors: geogeurt [...]

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

Subject: failover: re-loop through the failover-hosts ?
Date: Fri, 27 Jun 2014 14:54:48 +0200
To: bug-Net-Stomp [...]
From: Geurt Schimmel <geogeurt [...]>
Download (untitled) / with headers
text/plain 455b
version 0.46 with failover, it goes through the list of failover-hosts, and dies at the end of the list. Would be nice if it would start at the beginning of the hostlist again after reaching the end of the list. A typical example where this would be helpful is when ActiveMQ is shut on hostA for maintenance, Net::Stomp fails over to hostB. Subsequently, ActiveMQ on hostA is started again, and ActiveMQ on hostB is shut for maintenance. Thanks, Geurt
Download (untitled) / with headers
text/plain 383b
I can't reproduce this behaviour *after the initial connection*. When you create a Net::Stomp object, it expects at least one broker to be up. After you've created it, it will keep trying all brokers when it notices a connection error while writing. Yes, this behaviour is a bit inconsistent. I may add a constructor option to keep re-trying during the initial connection, as well.
0.47 has C<initial_reconnect_attempt> and C<reconnect_attempt>, fixing this.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to