----- Original Message ----- > From: "Gordon Sim" <[email protected]> > To: [email protected] > Sent: Tuesday, October 27, 2015 3:24:37 PM > Subject: Re: "unknown frame type: 0" after upgrading proton-j jar and proton > jms jar (0.4 -> 0.10) in HornetQ > (final). > > On 10/27/2015 03:43 PM, Matthew Karlsen wrote: > > Hello again, > > > > Last time I contacted the list I was having issues with the basic sending > > and receiving of AMQP messages to/from HornetQ. > > I have got quite a bit further by myself (+ docs & e.g.s) but am sorry to > > say that I am stumped again... > > > > I have got HornetQ and the Qpid Proton examples configured and working with > > proton-api-0.4.jar, proton-j-impl-0.4.jar and > > proton-jms-0.4.jar. I have also set up a divert with a filter such that > > some messages are diverted from one queue to another. > > > > It all works fine... > > > > Unfortunately, the Qpid Proton library versions that I am using have a > > connection timeout hard-coded at 60 seconds (if I understand correctly). > > > > I believe this relates to > > https://developer.jboss.org/thread/233539?start=0&tstart=0 [How to set > > AMQP idle-timeout / ping frequency / TTL?] > > > > As I understand it, upgrading to proton-j-0.10.jar and proton-jms-0.10.jar > > should fix this issue by letting you specify the timeout. > > > > However, with the new jars, when trying to send/receive the message I am > > getting the error at the end of the message (below). > > > > I realise that this topic bridges Qpid and HornetQ (unfortunately). I can > > confirm that HornetQ does support SASL and my config should > > be sufficient (indeed, it worked before the upgrade). From the HornetQ > > manual: "The HornetQ Server accepts AMQP SASL Authentication > > and will use this to map onto the underlying session created for the > > connection so you can use the normal HornetQ security configuration." > > > > Does anyone have an idea what may be going on? > > > > I have tried reading the documentation, wiki, e.t.c. (have spent about a > > day on this so far). > > Can you get a capture of the protocol interaction, e.g. using wireshark? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
It sounds like the java code is expecting a Sasl header (type 3) but is receiving a normal AMQP header (type 0). You could try disabling Sasl at your end to see if the connection goes through. A protocol trace will show for sure. -Chuck --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
