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 Fri, 24 Oct 2008 14:25:42 GMT

Jconsole shows the following stack trace: 

Name: main
State: BLOCKED on java.lang.Object@db3331 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 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-tp20130356p20151177.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message