activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dehmlow <dehml...@gmail.com>
Subject Re: Can't Connect to broker using stomp on activemq cpp 3.0.1
Date Mon, 03 Aug 2009 14:04:01 GMT

I would like to see the delta between stomp and open wire. With the version
of activemq cpp we had been using stomp was actually much faster then
openwire. We had been hopping to see speeds comparable to Tibco Smart
Sockets, but thus far active mq performs at about half the msgs/sec.

Any performance optimaization ideas?



Timothy Bish wrote:
> 
> 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
> application.
> 
>> I send messages and never receive them.
> 
> Can you provide a simple but complete example that demonstrates the
> problem?
> 
>> 
>> 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:
> tcp://localhost:61613?wireFormat=stomp
> 
> 
> 
>> 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
> 
> Regards
> Tim.
> -- 
> Tim Bish
> http://fusesource.com
> http://timbish.blogspot.com/
> 
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Can%27t-Connect-to-broker-using-stomp-on-activemq-cpp-3.0.1-tp24764325p24791440.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message