Re: NMS library hangs when connection to ActiveMQ is broken

Well, they say that the sourcs code itself is the ultimate documentation. :). But in this regard, there is not a single location that lists all possible URI parameters for the .NET client in a single location. I think the Java client is documented, and we try to stay compatible, but I know there a

RE: client already connected with same clientId error

Hi Kalana, Check for a code/configuration that sets the client id, either on the ActiveMQConnectionFactory or on an ActiveMQConnection. The client id should be unique among the connected clients (as per the JMS Spec). I believe the issue at the AMQ site was related to InvalidClientIdException,

Can I use jQuery to access the amq servlet directly?

Do I need the amq.js files or can I use native jquery xmlhttp tools to read the queues? I am sending messages as xml and I am having significant issues decoding them with the javascript scripts provided. Single line messages work fine. Any help would be appreciated. Z -- View this message in

queue connecting to wrong broker.

I have a set up where I have 3 servers and 2 brokers: Server A: running an embedded broker (BrokerA) on localhost:61616 providing a message Queue called QueueOne Server B: subscribes to QueueOne on localhost:61616 has an embedded broker (BrokerB) producing a topic

client already connected with same clientId error

We use fuse-message-broker-5.0.0.9, which we use to create a connection factory. And after running the service for sometime, we can't connect to the Activemq(new Sessions). It will give and error saying we are trying to connect from the same clientId. Please see the stack strace below. javax.jms.

Re: Messages hang in Queue even when consumers are present after failover

More info for this problem: Producer output [java] Sending message: A: Message: 67 sent at: Thu Apr 03 17:34:22 EDT 20... [java] Sending message: A: Message: 68 sent at: Thu Apr 03 17:34:23 EDT 20... [java] Sending message: A: Message: 69 sent at: Thu Apr 03 17:34:23 EDT 20...

Re: Unable to connect to remote broker

Now it is working properly the issue was with the Windows FireWall, after disabling firewall it started working.. mir_akhil wrote: > > Hi > I have tried both with and without connectionTimeout property in the > transport URL > but it does not work, I think there is some firewall issue in the ne