I don't see any reason why this shouldn't work. I've modified our
example and can set that property without causing an error while using
queues.
I don't think that the c++ client would be causing it. However, if you
can create a sample app that causes this to happen then I'd create an
issue and
Yes, the error message is coming out in the ActiveMQ console window.
In the C++ module that sends a message into ActiveMQ we are using:
void MQProducer::sendMessage(const std::string &gameMessage, const
std::string& tag)
{
std::auto_ptr
message(session->createTextMessage(gameMessage));
me
You are going to need provide a little more information than this. What
are you doing in the C++ code. Can you provide a sample app that
demonstrates the problem?
I assume that this is coming out in the ActiveMQ console window, not
from the c++ client as a BrokerError?
Regards
Tim.
On Wed, 2
Hi
Running SUSE 10.2 using CMS 2.1.1 with ActiveMQ 4.1 and stomp.
Set up is one producer and two consumers (for failover).
We have set JMSXGroupID in the producer, to make failover work, so only one
consumer consumes.
And on receiving messages the producer dumps the following errors:
<-sn
