er message ack
> basis.
>
> Do you have active consumers for the destinations that are waiting for
> space?
>
> Can you reproduce this scenario?
>
> 2009/8/12 Chetan Sarva
>
>> Hi,
>>
>> We appear to be facing a deadlock during queue message delive
Hi,
We appear to be facing a deadlock during queue message delivery. See
the following stack dump:
"ActiveMQ Transport: tcp:///10.10.10.30:40919" daemon prio=10
tid=0x2aab002a3800 nid=0x281e in Object.wait()
[0x57b77000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
fire when KeepAlives should be failing.
>
> Best - Susmit
>
>
> Chetan Sarva-2 wrote:
> >
> > 3.0 now requires that you initialize the library before using it. Simply
> > call:
> >
> > activemq::library::ActiveMQCPP::initializeLibrary();
> >
> >
Is there a different namespace I should go to for more features?
> Any sample code will be helpful.
>
> Best - Susmit
>
>
> Chetan Sarva-2 wrote:
> >
> > Which version of the library are you using? The latest version, 3.0,
> which
> > was released less than
After creating the queue or topic with createQueue(name) or
createTopic(name), you can specify the selector using createConsumer(name,
selector). Here's the method signature (from the 3.0 library):
virtual MessageConsumer* createConsumer(
const Destination* destination,
Which version of the library are you using? The latest version, 3.0, which
was released less than 2 weeks ago, supports the failover transport for
handling scenarios like this.
chetan
On Mon, Jun 22, 2009 at 8:22 PM, shaldar wrote:
>
> Hi all -
>
> I wrote a publish/subscribe clients that seem
Hi,
Is Jencks still the preferred method of pooling connections for Spring's
JmsTemplate? The jencks.org site is dead and gone, and the codehaus site
seems a bit stale so it's hard to gauge if this is still being used and/or
maintained.
Also, it appears that Mule uses the ActiveMQConnectionFactor
