Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: Dylan Vanderhoof <DylanV@semaphore.com>
To: "'users@activemq.apache.org'" <users@activemq.apache.org>
Date: Fri, 21 Mar 2008 14:44:00 -0700
Subject: RE: Implementing failover for Net::Stomp
Thread-Topic: Implementing failover for Net::Stomp
Thread-Index: AciLlMyLo1Z4mCfMQIq8gm2MVSrBLgACDRog
Message-ID: 
 <EAC75A12BE260246A8145B73D2613087013FBE6C@exchange00.semaphore.lan>
In-Reply-To: <16207964.post@talk.nabble.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

If you get this worked out, would you be willing to release your Net::Stomp=
 hacks?

I'm desperatly needing HA for my perl publishers (and subscribers for that =
matter), but I don't have the hours to do it in house at the moment.

-D

> -----Original Message-----
> From: Ramit Arora [mailto:ramit.arora@gmail.com]
> Sent: Friday, March 21, 2008 1:50 PM
> To: users@activemq.apache.org
> Subject: Implementing failover for Net::Stomp
>
>
>
> Hi,
> I am using ActiveMQ 5.0.0. My application requires Perl
> publishers & Java
> subscribers. Since HA is a necessity, I wish to implement failover
> capability in the Net::Stomp client for Perl.
> I've already come up with a basic solution, but I am facing
> the following
> problem:
> I use the pipe broken signal to detect master broker failure
> from perl. The
> pipe does not break until the master shuts down its Stomp
> connector. If I
> abruptly shut down the master (power down or kill -9), then
> there is no
> issue. But if I cleanly shutdown the master (^C), then the
> master does not
> shut down its Stomp connector until it has done its cleanup.
> This normally
> takes around 10secs. This results in the Perl client sending
> messages to the
> broker for those crucial ten seconds. These messages are lost & not
> delivered to the Java client.
> Is there are any other way of detecting that the master is
> shutting down?
> Perhaps something using the STOMP ERROR frame?
>
> TIA,
> Ramit
> --
> View this message in context:
> http://www.nabble.com/Implementing-failover-for-Net%3A%3AStomp
-tp16207964s2354p16207964.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.