Re: Failover Transport hangs forever on connection.start() in Master/Slave

Hi, Following is the stack trace for successful connection to activeMQ: # 2019-04-30 20:51:52 DEBUG TaskRunnerFactory:91 - Initialized TaskRunnerFactory[ActiveMQ Task] using ExecutorService: java.util.concurrent.ThreadPoolExecutor@6504e3b2[Running, pool siz

Re: Failover Transport hangs forever on connection.start() in Master/Slave

Can you upload the full stack dump from the client application when this happens as a GIST on github.com and send the link? It's OK to filter out any proprietary bits as long as all of the threads that have ActiveMQ in the call history are listed. BTW, the "oneWay" method sends a message over the

Re: Failover Transport hangs forever on connection.start() in Master/Slave

I am using activemq version 5.15.8. I see the issue when client first time tries to connect to activemq broker and if the randomly picked broker url happens to be slave, the call is stuck forever in FailoverTransport class at the following point: ## @Override publ

Re: Failover Transport hangs forever on connection.start() in Master/Slave

You haven't mentioned a version of your activemq, there were some issues with that in older versions... We're on 5.6.0 and above - no issues... See http://activemq.apache.org/failover-transport-reference -- Sent from: http://activemq.

Re: failover transport not timing out

You may need to set maxReconnectAttempts and startupMaxReconnectAttempts to get control back from the failover transport when no brokers are available. The failover transport's documentation ( http://activemq.apache.org/failover-transport-reference.html) explicitly says that the timeout URI option

Re: failover transport connect

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: FailOver transport not reconnecting

your config looks ok, but this may be a case of https://issues.apache.org/jira/browse/AMQ-3993 which still needs investigation On 19 September 2012 01:21, pollotek wrote: > I'm seeing this situation happen more often in my servers and seems pretty > random, some servers do connect and some don't.

Re: FailOver transport not reconnecting

I'm seeing this situation happen more often in my servers and seems pretty random, some servers do connect and some don't. Am I missing some parameter in the networkConnector bridge configuration? -- View this message in context: http://activemq.2283324.n4.nabble.com/FailOver-transport-not-rec

Re: failover transport recovery behavior

5.3.x of ActiveMQ is fairly old and lots of things have been fixed since then in the current 5.5 version.You should consider upgrading. In addition, as of 5.4 there is a "rebalanceClusterClients" option you can set on your transportConnector (in conjunction with "updateClusterClients") tha

Re: Failover transport options

Hi,, we used them only as the reference.. we gave maxReconnectAttempts as 500. still it is closing the connection after 10 seconds.. this is our url failover://(tcp:/10.1.37.155:61616)?maxReconnectAttempts=500. Also what significance does maxReconnectionDelay have since we have initialReco

Re: Failover transport options

Hi, checkout http://activemq.apache.org/failover-transport-reference.html Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog -

Re: failover transport + JMS Resource Archive

The ServerUrl property is what you need to change to make is use failover. see: http://activemq.apache.org/resource-adapter-properties.html 2009/8/31 sbuster > > How do you setup the JMS configuration details inside a J2EE container to > listen for multiple brokers such as the in the clustered

Re: Failover transport hangs on startup if it cannot connect to a broker

I'll look at the source and see if I can make it do what I want, and submit a patch. Currently the failover transport blocks on sending a connection info message to the remote broker as part of startup, and I think already has a mechanism to do that on reconnect. Uwe On Thu, 2009-02-19 at 07:42

Re: Failover transport hangs on startup if it cannot connect to a broker

Check out http://activemq.apache.org/failover-transport-reference.html If it is attempting to establish a connection it will block. With the timeouts and such you might be able to get around start() blocking and do your own queuing of messages because if there isn't a valid connection the send(

Re: Failover transport for ajax client

Hi, try setting org.apache.activemq.brokerURL context parameter in your web.xml to the appropriate failover URI and see if it helps. Cheers -- Dejan Bosanac Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On M

Re: Failover Transport - pyactivemq

About all you can do right now would be to setup an ExceptionListener on the Connection and destroy and recreate your connection to some pre-configured fallback broker or set of brokers. In this case you would need to recreate all you sessions, consumers, producers, destinations, etc. Regards Tim

Re: Failover Transport - pyactivemq

Much appreciated, Do you know if there is any other way to achieve such a functionality without the use of Failover? -Other than having a second activemq service running, and connecting to it if an error occurs. Timothy Bish wrote: > > pyActiveMQ uses ActiveMQ-CPP which currently does not sup

Re: Failover Transport - pyactivemq

pyActiveMQ uses ActiveMQ-CPP which currently does not support Failover. There is work ongoing to add Failover to ActiveMQ-CPP v3.0 once that's done the author of pyActiveMQ could then release a new version that would give you Failover functionality. Regards Tim. On Mon, 2009-01-12 at 06:55 -080

Re: Failover transport

Hi, Please could somebody explain exactly what is going wrong to hit this cyclic redundancy problem? The log4j JMSAppender is a very useful thing to have. We have created a little jms logging server where we want clients (using the jmsAppender) to be able to log to. We want to use the Failover t

Re: Failover transport

YES, I am using the log4j JMS appender. That is mentioned in my first message for this thread. In my simple client, I am using the log4j JMS appender, which appends messages to a JMS topic and it WORKS ! It doesn't give any problems. The problem occurs once I include the commons-logging JAR. I

Re: Failover transport

2008/10/28 James Strachan <[EMAIL PROTECTED]>: > 2008/10/28 selezovikj <[EMAIL PROTECTED]>: >> >> PROBLEM FOUND !!! >> >> I wrote a simple client connecting to my activemq broker using the failover >> transport and it worked. >> Then I started adding the jar files that my bigger project uses, and a

Re: Failover transport

2008/10/28 selezovikj <[EMAIL PROTECTED]>: > > PROBLEM FOUND !!! > > I wrote a simple client connecting to my activemq broker using the failover > transport and it worked. > Then I started adding the jar files that my bigger project uses, and at one > point the same problem appeared: it was saying

Re: Failover transport

PROBLEM FOUND !!! I wrote a simple client connecting to my activemq broker using the failover transport and it worked. Then I started adding the jar files that my bigger project uses, and at one point the same problem appeared: it was saying attempting to connect for hours. After some adding an

Re: Failover transport

Jconsole shows the following stack trace: Name: main State: BLOCKED on [EMAIL PROTECTED] owned by: ActiveMQ Task Total blocked: 1 Total waited: 1 Stack trace: org.apache.activemq.transport.failover.FailoverTransport.start(FailoverTransport.java:228) selezovikj wrote: > > I am getting rea

Re: Failover transport

I am getting really confused. I should be getting an "Invalid broker URL" but I am not. What is even more confusing is that I get "Invalid broker URL" when I only specify "tcp:localhost:61617", and then whatever correct address that I specify just results in me getting an Invalid broker URL. Th

Re: Failover transport

I've tried to reproduce your problem in my AMQ 5.1 testbed w/out success; the failover transport works as expected. However the url, failover://tcp://localhost:61617 is not properly formatted and you should be getting an "Invalid broker URL" exception. It should be formatted as follows failov

Re: Failover transport

I saw that in the Apache ActiveMq 5.2 release the default ActiveMQConnectionFactory brokerUrl uses the failover transport. Is this going to solve my problem ? I tried running my application on different machines and it is giving the same error. Can anyone suggest anything ? selezovikj wr

Re: Failover transport

Even only: failover://tcp://localhost:61617 does not work selezovikj wrote: > > I have a jms appender sending logging events to active mq broker. In the > jndi.properties I have the following provider url: > > java.naming.provider.url = > failover:(tcp://localhost:61617,tcp://localhost:616