activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From selezovikj <semir.elezo...@gmail.com>
Subject Re: Failover transport
Date Tue, 28 Oct 2008 11:42:03 GMT

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 and removing of jar files, I saw that the problem causing
this is the commons-logging-1.1.jar file. 
When I add that jar file the failover transport is useless. 
Any idea why this is so ? 





selezovikj wrote:
> 
> Jconsole shows the following stack trace: 
> 
> Name: main
> State: BLOCKED on java.lang.Object@1bc1fb9 owned by: ActiveMQ Task
> Total blocked: 1  Total waited: 1
> 
> Stack trace: 
> org.apache.activemq.transport.failover.FailoverTransport.start(FailoverTransport.java:228)
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:57)
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:57)
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:258)
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:222)
> org.apache.activemq.ActiveMQConnectionFactory.createTopicConnection(ActiveMQConnectionFactory.java:200)
> org.apache.log4j.net.JMSAppender.activateOptions(Unknown Source)
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:132)
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:96)
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:654)
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
> org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:533)
>    - locked org.apache.log4j.Logger@1898115
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:417)
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441)
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:470)
> org.apache.log4j.LogManager.<clinit>(LogManager.java:122)
> org.apache.log4j.Logger.getLogger(Logger.java:104)
> 
> 
> 
> selezovikj wrote:
>> 
>> 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. 
>> There is definitely something weird going on here. 
>> I guess in the background there are some processes, sessions, whatever
>> not being closed properly and causing all this confusion. I just simply
>> don't know. 
>> 
>> 
>> 
>> 
>> 
>> Joe Fernandez wrote:
>>> 
>>> 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
>>> 
>>> failover:(tcp://localhost:61617)
>>> 
>>> Joe
>>> http://www.ttmsolutions.com - get a free ActiveMQ user guide
>>> 
>>> 
>>> 
>>> 
>>> 
>>> selezovikj wrote:
>>>> 
>>>> 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:61616)?initialReconnectDelay=20&maxReconnectDelay=1000&randomize=false&maxReconnectAttempts=10
>>>>> 
>>>>> 
>>>>> Since randomize is set to false, I am expecting it to connect to
>>>>> tcp://localhost:61617 first. It attempts to connect to it, but I just
>>>>> get the following message:
>>>>> 
>>>>> [2008-10-23 13:25:56,808]
>>>>> org.apache.activemq.transport.failover.FailoverTransport DEBUG  -
>>>>> Waking up reconnect task
>>>>> [2008-10-23 13:25:56,813]
>>>>> org.apache.activemq.transport.failover.FailoverTransport DEBUG  -
>>>>> Attempting connect to: tcp://localhost:61617
>>>>> 
>>>>> When I set the providerURL in my jndi.properties to only
>>>>> "tcp://localhost:61617", it connects successfully.
>>>>> As I see in the TCP transport there is not an option that would make
>>>>> my jms appender reconnect to the server, once the server is shut down
>>>>> and restarted.
>>>>> 
>>>>> Any help with this ? 
>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Failover-transport-tp20130356p20205685.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message