Thanks for digging this up. Appreciate your effort. Regards,
Rajith On Tue, Mar 24, 2009 at 10:44 AM, Jason Copeland <[email protected]> wrote: > Actually I was using the ConnectionFactory.createConnection() API. But I > debugged down into the client code to the point where sending the > ProtocolHeader was the data causing the issue. I was simply trying help > narrow down the data that was causing the issue. > > But I'm all good now. :) > > Thanks, > Jason > > -----Original Message----- > From: Rajith Attapattu [mailto:[email protected]] > Sent: Monday, March 23, 2009 7:42 PM > To: [email protected] > Subject: Re: Clustering segfault on connection > > Jason, > > Are you using the JMS client or did you try to use the low level > classes and work at the AMQP level? > If you did try the latter could you please post your client code? > > Also please note that these classes may change btw AMQP versions as in > the java side we only support the JMS API. > Is there a reason why you didn't use JMS? > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
