Reply:Re: Reply:failover transport connect

2013-01-22 Thread SuoNayi
Yes, I know your purpose with that setting. After taking a glance through the source code of 5.5.x, I'm afraid that the client will do rebalance when connection control messages arrive. You can disable rebalanceClusterClients option on TransportConnector and try again to verify whether your issue

Re: Reply:failover transport connect

2013-01-22 Thread Nate Faerber
I set randomize to false expecting the clients to connect to the first mq server. In that case, the clients wouldn't need to rebalance. I see this on the first mq server but I feel like this is a result of the client bouncing over to the failover rather than it being the reason it bounces over to

Re: Active MQ broker hang when computer name has Japanese/Chinese character

2013-01-22 Thread ankursha1
Hello, I have attached new log file with previous post. Please have a look. I hope new log will have more information. I tried with java client to connect to mq and everything works but cpp client still hangs. Thank you. -- View this message in context: http://activemq.2283324.n4.nabble.com/

Re: Active MQ broker hang when computer name has Japanese/Chinese character

2013-01-22 Thread ankursha1
Hello , Today i tried to connect to ActiveMQ broker with java lib and sample mq client was able to connect to mq broker successfully. Broker version is 5.5.1 and ActiveMQ CPP 3.4.0 library at client side. I also tried to set the version of wireformat =6 from producer and consumer which worked

REST GET 204

2013-01-22 Thread sweaver
Using 5.7 REST API I can GET a message from a topic but if a new message is POSTed to that same topic before the GET has been reissued (less than 20ms behind the POST and using the same session as the previous GET) the GET will timeout with a 204 and does not retrieve the message. This may be as de

User name [null] or password is invalid.

2013-01-22 Thread abhi1301
I am using embedded activemq 5.7.0. And I have deployed activemq-web-console-5.7.0.war on my tomcat. When open the activemq-web-console on browser then I can see my Broker, all the topics and queues. But when I am trying to send a message to a topic then it throws exception: [dispatcher] Servlet.s

Re: Activemq-C

2013-01-22 Thread Timothy Bish
On Mon, 2013-01-21 at 14:30 +0100, Jason Armstrong wrote: > I notice that the directory for activemq-c is not in the latest > activemq-cpp-3.5.0 (from subversion). > > Is it no longer supported? I have some code that depends on it, and > the latest version that has it is 3.4.5. Should I migrate to

Activemq-C

2013-01-22 Thread Jason Armstrong
I notice that the directory for activemq-c is not in the latest activemq-cpp-3.5.0 (from subversion). Is it no longer supported? I have some code that depends on it, and the latest version that has it is 3.4.5. Should I migrate to another C library for the future? Regards, -- Jason Armstrong

Re: failover transport connect

2013-01-22 Thread Christian Posta
Is your broker (mq-1) failing? On Mon, Jan 21, 2013 at 9:24 PM, Nate Faerber wrote: > Hi, > > I have two ActiveMQ server configured as network of brokers and my clients > with this connect string: > > > failover:(tcp://mq1-master:61616,tcp://mq2-master:61616)?randomize=false&backup=true&maxReco

Re: NoSuchElementException

2013-01-22 Thread Christian Posta
Yep, https://issues.apache.org/jira/browse/AMQ-3319 Seems to be fixed for 5.6.0 Cheers On Mon, Jan 21, 2013 at 4:30 PM, Steve Angelovich wrote: > NoSuchElementException -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta

Re: Active MQ broker hang when computer name has Japanese/Chinese character

2013-01-22 Thread Christian Posta
The reason would be to help in debugging. It's another option to try the Java libs (if it's not too big of a deal) and narrow down if there is a bug in the C++ client or if it exists in the core of the implementation. From what info you've given, it's not entirely clear what is happening. On Mon,

Reply:failover transport connect

2013-01-22 Thread SuoNayi
Hi, I guess: 1. The broker sends the rebalance control messages to your client and your client do rebalance and reconnect to the other broker; 2. The second broker has some consumers while none on the first broker so messages sent to the first broker are forwarded to the second broker by demand.