This is of interest to me too.
Could use a description of it's behaviour which that page does not provide.
James
On 8 November 2011 01:45, Jason Dillon wrote:
> ... is this any good? I keep getting folks in the backseat making
> tunneling over HTTP a meta-requirement. Are there any significa
... is this any good? I keep getting folks in the backseat making tunneling
over HTTP a meta-requirement. Are there any significant issues with using the
http[s] transport in the activemq-optional module for this? Will use of it
totally kill performance?
Documentation is a bit weak here, I'v
Hi,
I have an issue where ActiveMQ stop routing messages to clients after about
12 hours of running, which I would really appreciate some help with.
When the problem occurs, clients can connect to the server fine. When they
subscribe to a topic, they get the a old message if using retroactive, bu
Hi
I am using ActiveMQ 5.4.2 and trying to connect to the Command Agent using
Smack 3.2.1. I connect, but do not get any messages back. Your help is
appreciated. Below is the code:
@Test
public void testSmack() {
try
{
I am using version 5.5.0 and after connecting 1000 clients with nio transport
connector, clients start to disconnect with the exception:
15:24:11,307 WARN FailoverTransport:231 - Transport (null) failed to
nio://server2:61618 , attempting to automatically reconnect due to:
org.apache.activemq.t
Thanks Gary,what if producer failover to the other broker which is networked
with the previous broker?
In this case, the other broker which does not know the message sent by the
producer before its failover.
So the reduplicate messages are coming out,arenot they?
At 2011-11-01 19:15:20,"Gary
Hi,
i have embedded an additional component into activemq by adding a bean
configuration to the activemq.xml config.
now when activemq is started a bean for my component is created and
initialized with the configured init-method. BUT when activemq is stopped
the destroy-method is not executed.
m
Hi Stefan,
the problem is that you send non-persistent messages to the topic and if
there's no consumers on the topic (which there isn't in your case), the
message is being discarded. As you suggested, the solution would be to use
advisory messages to wait for a consumer on your topic, before send
