activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From MattG987 <>
Subject Re: Activemq IPV6 Client Connection (Java and C++)
Date Tue, 06 Aug 2013 15:58:35 GMT
oscarp wrote
> Hi all,
> Im trying to use ActiveMQ with IPV6 but Im running into some problems. I'm
> in debian linux, and seems that ActiveMQ(5.5.1) is up and listening IPV6.
>     tcp6   0   0 :::61616      :::*          LISTEN      24671/java
> I can make a ping and a telnet to ::1 61616 and all seems that works fine.
> Now Im trying to connect two clients (one in Java and one in C++).
> -Java client: If I set the uri tcp://[::1]:61616, connection is
> stablished,
> but if I add the failover transport (failover://(tcp://[::1]:61616)), I
> can
> see an Invalid broker URI exception. Its not compatible, or there is
> another way to use failover with IPV6?
> - C++ Client: Im setting the same URI that it works in Java
> (tcp://[::1]:61616) but doesnt work and I get "Resource temporarily
> unavailable". Any idea of what coulde be reason? I tested too with a
> connection string like this: ""tcp://[fe80::XXX:XXXX:XXXX:XXXX]:61616" and
> I'm receiving this error "the requested name is valid and found in
> database, but doesnt have the correct data that is trying to resolve".
> Any Idea?
> thanks in advance
> -- 
> Óscar Pernas Plaza.

As I encountered this recently, I figured I would post the solution here, in
case someone else encounters it someday.

The problem is Java's URI parser (not ActiveMQ) will not accept the left
bracket in the IPv6 address in "failover://(tcp://[::1]:61616)", where it
WILL accept the corresponding IPv4 structure
"failover://(tcp://" and IPv6 without failover

The solution to this is to exclude the "//" from the failover.
"failover:(tcp://[::1]:61616)" is accepted by the Java URI parser, and will
function correctly.

-Matthew Griffin

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message