[Rhm-users] Getting started with C++ broker

[Andy Grove]

Carl,

 

Thanks for the advice. I'll start working with the M2 release for now as you
suggest. 

 

Thanks,

 

Andy.

 

  _____  

From: Carl Trieloff [mailto:cctrieloff at redhat.com] 
Sent: 19 October 2007 18:39
To: Andy Grove
Cc: rhm-users at redhat.com
Subject: Re: [Rhm-users] Getting started with C++ broker

 


Andy,

There is not a nice clean answer for the RCs that are currently built. In
the early versions the Java broker was extended to resolve some of the JMS
issues which has not made it to the AMQP spec yet - where the yum install is
on AMQP 0-9.

Qpid has only released a 0-8 of AMQP, and we as busy releasing a M2 at qpid
(looking for one more bug)... hopefully we start a vote today.

To for JMS M2 Java - Java wold be best or M2 C++ broker. E.g.
http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.x86_64.rpm

However, I'm not sure there would be any notable performance benefit on M2.
Most of the performance work is being done on trunk for 0-10 in C++, which
we are in the middle of testing / fixing and I expect that this will be the
next version pushed to Fedora.

If you want to most stable I would pick up M2 from the download links
above... then cut across to 0-10 from yum in a few weeks.. If you want to be
on the latest and help file issues while we close down pick up this set
*-0.2-*.rpm.  We have shown maxed G IO (non-RDMA) tuned. 

Sorry for the options answer, let me know if you want comments on anything
else.
Carl

Andy Grove wrote: 

Hi,

I have just started using RHM. I have a Java client which works correctly
when I run it against the Java broker. I am now trying to use the C++ broker
for performance reasons. I installed the broker using "yum install qpidd" on
a 64 bit Intel machine running an early version of Fedora 8. The install ran
smoothly and the broker appears to be running ok, 

When I run my client it basically seems to time out with this error:

javax.jms.JMSException: Error creating connection: State not achieved within
permitted time.  Current state AMQState: id = 1 name:
CONNECTION_NOT_STARTED, desired state: AMQState: id = 4 name:
CONNECTION_OPEN 

After I get this error I see some output on the broker:

Closing socket 0x60b230 at 0x625f70
Session closed [0x625f70]

This is the code I am using to get a connection.

            InitialContext ctx = new InitialContext(properties); 
            AMQConnectionFactory cf = (AMQConnectionFactory)
ctx.lookup("local");
            Connection connection = cf.createConnection();

These are the properties I am passing in to the InitialContext: 

java.naming.factory.initial =
org.apache.qpid.jndi.PropertiesFileInitialContextFactory
connectionfactory.local =
amqp://guest:guest@clientid/test?brokerlist='tcp://192.168.1.14:5672'

To summarize, this works fine when I run against a Java broker on the same
machine but fails if I run it against a remote C++ broker. I've disabled the
firewall on the broker machine so that's not the issue. 

I would appreciate some pointers so I can debug this further.

Thanks,

Andy.





 





  _____  



 
_______________________________________________
Rhm-users mailing list
Rhm-users at redhat.com
https://www.redhat.com/mailman/listinfo/rhm-users

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/rhm-users/attachments/20071023/19e0396d/attachment.htm>