Good Day All,
I have written a consumer using pyactivemq, however in-terms of using a
failover connection does anyone know if this is possible?
On the AMQ site: "
http://activemq.apache.org/failover-transport-reference.html
http://activemq.apache.org/failover-transport-reference.html " it says
pyActiveMQ uses ActiveMQ-CPP which currently does not support Failover.
There is work ongoing to add Failover to ActiveMQ-CPP v3.0 once that's
done the author of pyActiveMQ could then release a new version that
would give you Failover functionality.
Regards
Tim.
On Mon, 2009-01-12 at 06:55 -080
Much appreciated,
Do you know if there is any other way to achieve such a functionality
without the use of Failover? -Other than having a second activemq service
running, and connecting to it if an error occurs.
Timothy Bish wrote:
>
> pyActiveMQ uses ActiveMQ-CPP which currently does not sup
About all you can do right now would be to setup an ExceptionListener on
the Connection and destroy and recreate your connection to some
pre-configured fallback broker or set of brokers. In this case you
would need to recreate all you sessions, consumers, producers,
destinations, etc.
Regards
Tim
I have a spring based JAX-RS/Jetty Servlet that also starts an embedded
ActiveMQ broker.
For unit tests, I am using Jetty. Sometimes an error occurs and Jetty
restarts. When this happens, I get the following:
11:36:12,136 INFO [12882...@qtp0-3] broker.BrokerService
(BrokerService.java:454) -
Can anyone in this Forum help me out? I would really like to know how to
properly delete these Queues, or find a workaround for this bug.
M@
MaenXe wrote:
>
> I have a couple of Queues that I am unable to completely get rid of. If I
> delete the Queue either from JMX(using removeQueue) or fr
Are you removing the queue's with there are still attached consumers?
Regards
Tim.
On Mon, 2009-01-12 at 17:07 -0800, MaenXe wrote:
> Can anyone in this Forum help me out? I would really like to know how to
> properly delete these Queues, or find a workaround for this bug.
>
> M@
>
>
> MaenXe
No, but this a part of a Network of Brokers. I just tested on one of our AMQ
servers that is not on a network of brokers and the problem occurs there
too. Here's the order of the test I just performed:
1.) Login to the AMQ Web Console
2.) Create a Queue using the Web Console
3.) Use Ant to l
