activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <>
Subject Re: Can't Connect to broker using stomp on activemq cpp 3.0.1
Date Sat, 01 Aug 2009 00:15:51 GMT
On Fri, 2009-07-31 at 16:14 -0700, Michael Dehmlow wrote:
> Hello I'm trying to connect a 5.2.0 Active mq broker using the 3.0.1 cpp
> client. 
> I can connect send and receive fine when I use openwire:
> tcp://localhost:61616?wireFormat=openwire
> But if I use stomp:
> tcp://localhost:61613?wireFormat=stomp

My first question is why do you want to use Stomp?  The CPP client uses
Openwire as its native Wire Format and will provide the best performance
and be most reliable when used with the default OpenWire transport.  The
Stomp Transport in the CPP client is legacy and isn't really maintained
or tested very well anymore so I wouldn't rely on it for a production

> I send messages and never receive them.

Can you provide a simple but complete example that demonstrates the

> My initial thought was that my URI was malformed based on the broker
> configuration:
> <transportConnectors>
>   <transportConnector name="openwire" uri="tcp://localhost:61616"
> discoveryUri="multicast://default" /> 
>   <transportConnector name="ssl" uri="ssl://localhost:61617" /> 
>   <transportConnector name="stomp" uri="stomp://localhost:61613" /> 
>   <transportConnector name="xmpp" uri="xmpp://localhost:61222" /> 
> </transportConnectors>
> However if I connect to:
>    stomp://localhost:61613?wireFormat=stomp
> I get an exception at startup stating the stomp is not a valid transport.

That's because that URI is invalid, the one above is correct:

> Modifiying the broker as follows:
>   <transportConnector name="stomp" uri="tcp://localhost:61613" /> 
> I never return from the connect call and just sit there.
> Any thoughs?
> Thanks

Tim Bish

View raw message