producer->send blocks ( ActiveMQ CPP )

Hi there Have been integrating ActiveMQ CPP client into our project, and I now have a question. For example: if we do 10 producer->send then each send seems to be blocking, so 1) send 2) wait for ack? 3) goto 1 with a latency of 100ms, 10 sends take 1 second. I am looking for nonblocking send, so

Error During starting activemq

I've installed activemq. but after starting activemq encountered the following error : Exception in thread "main" java.lang.UnsupportedClassVersionError: org/apache/ac tivemq/console/Main (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at

Re: ActiveMQ Client Pooling ( What to pool, Connections or sessions?)

On Sun, Sep 28, 2008 at 3:25 PM, Andres Rangel <[EMAIL PROTECTED]> wrote: > Hi, > I am writting my on jms libraary for an internal application using java, and > would like to know what should I cache, connections or sessions (all from the > same connection)? > > Also, would like to know if I have

Re: Sending message hangs when negotiating wire format

By any chance, do you have 'maxInactivityDuration' turned off? Joe Get a free ActiveMQ user guide @ http://www.ttmsolutions.com Mark Chaimungkalanont wrote: > > We have a problem where our network would occasionally goes down and one > of the threads sending a message the hang. We're usin

Sending message hangs when negotiating wire format

We have a problem where our network would occasionally goes down and one of the threads sending a message the hang. We're using Spring 2.0.7, ActiveMQ 4.1.2, Jencks 2.1 (for pooling). & the Failover transport with a single embedded broker. The thread dump is: "CONFFUNC-T5PG:Output Pump" daemon pr

Re: maxResponseWaitTime removed?

To better deal with the Broker's producer flow control mechanism that maxReponseWaitTime option was removed. The client now waits for a response from the broker before returning from the send unless the connection.sendTimeout option is set to something other than 0 or an exception is thrown from t

ActiveMQ Client Pooling ( What to pool, Connections or sessions?)

Hi, I am writting my on jms libraary for an internal application using java, and would like to know what should I cache, connections or sessions (all from the same connection)? Also, would like to know if I have an application that would run indefinetely, should I every so foten check the "stat