Take a look at http://activemq.apache.org/configuring-wire-formats.html
to see an example.
On 31/01/13 20:46, Mohit Anchlia wrote:
Thanks! but I am not even able to add maxInactivityDuration to the uri. Is
there a workaround for that?
On Thu, Jan 31, 2013 at 11:17 AM, Andreas Calvo Gómez
Hi,
I started the producer with the below URI
std::string brokerURI =
failover://(tcp://10.29.9.229:61617?timeout=3000);
so while the producer is sending the messages to the broker, I stopped the
broker
So currently it is waiting on the send method.
Thread 1 (Thread
Hi Christian,
Thank you very much for your reply.
Actually I am creating N number of threads with N number of queues so each
thread would be executing messages from separate queue. As you can see from
the code I am creating threads in a loop (for N times) and adding those
threads in threads
consider using the generic (un versioned) schema reference that can be
resolved from the distro, so that you don't depend on the web
see: http://activemq.apache.org/xml-reference.html
On 31 January 2013 18:55, Joe Milora jmil...@uci.edu wrote:
Hi,
We've been using
Hey Liny I've been searching the net all day trying to solve the same problem
as yours. I tried tomcat 7.0.x I tried even using TomEE as suggested on the
ActiveMQ site. I don't even know why ActiveMQ wrote a tutorial using Tomcat?
It does not work with Tomcat.
I downloaded Jetty v8 and configured
I have a receiver class, but I never used the countdownlatch objects that are
listed in this example program. http://activemq.apache.org/cms/example.html
Im wondering what the latch actually does and how will not using it affect
my program. Since upgrading to 3.5.0 my receiver now core dumps
On Fri, 2013-02-01 at 11:11 -0800, jeffrey wrote:
I have a receiver class, but I never used the countdownlatch objects that are
listed in this example program. http://activemq.apache.org/cms/example.html
Im wondering what the latch actually does and how will not using it affect
my program.
On Fri, 2013-02-01 at 00:39 -0800, Gangadhar Rao wrote:
Hi,
I started the producer with the below URI
std::string brokerURI =
failover://(tcp://10.29.9.229:61617?timeout=3000);
I believe this is the correct URI.
failover://(tcp://10.29.9.229:61617)?transport.timeout=3000
so while
Well, my tester has encountered more prioritized message queue test failures
even though she removed those prefetch=0 policies from the activemq.xml
config file, and the failures are resolved if she uses a queue name when
specifying the prioritizedMessages=true policy, instead of attempting to
The program is broken down to simply
activemq::library::ActiveMQCPP::initializeLibrary();
HBconsumer *hbc = new HBconsumer(brokerURI, destURI, 3); //This is my
receiver class it implements public
ExceptionListener, public MessageListener, public Runnable
Thread
On Fri, 2013-02-01 at 13:20 -0800, jeffrey wrote:
The program is broken down to simply
activemq::library::ActiveMQCPP::initializeLibrary();
HBconsumer *hbc = new HBconsumer(brokerURI, destURI, 3); //This is my
receiver class it implements public
That helps, thanks.
gtully [via ActiveMQ] wrote:
consider using the generic (un versioned) schema reference that can be
resolved from the distro, so that you don't depend on the web
see: http://activemq.apache.org/xml-reference.html
On 31 January 2013 18:55, Joe Milora [hidden email]
If I abruptly kill my REST API client, I am sometimes left with an orphaned
consumer over on the server. Aside from bouncing the server/broker, how do
I kill those left-over consumers? The web admin interface doesn't seem to
provide a way.
-
Stephen Vincent
--
View this message in
13 matches
Mail list logo
