cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jens <smix...@dzbank.de>
Subject Re: JMS Message Correlation in CXF 2.3+
Date Fri, 07 Oct 2011 13:23:14 GMT
Hi Christian,

sorry for the slow reponse, I got sidetracked a little.

Anyway, here's a header dump of a request message without the conduit
parameters:

 MQGET of message number 1
****Message descriptor****

  StrucId  : 'MD  '  Version : 2
  Report   : 0  MsgType : 1
  Expiry   : -1  Feedback : 0
  Encoding : 273  CodedCharSetId : 1208
  Format : '        '
  Priority : 4  Persistence : 1
  MsgId : X'414D5120584E475457303154202020204E82B77221057307'
  CorrelId : X'633566363263653466346265343031373862343435306663'
  BackoutCount : 0
  ReplyToQ       : 'QA.XN.0000/HMV_VRS_REP                          '
  ReplyToQMgr    : 'GTW01T                                          '

As you can see, it has a correlationId set regardless. After a bit of
debugging it looks like what I thought was a synchronous exchange in fact is
not (I'm using CXF inside a Camel route). Since all of the msgId vs.
correlationId logic in CXF apparently only applies to the synchronous case I
guess that explains why it doesn't work. Is there a way to enable it for
asynchronous exchanges as well?

Regards,
Jens


Christian Schneider wrote:
> 
> Hi Jens,
> 
> would be really great to get these dumps. I still hope we can make the 
> Websphere MQ case just work without adding a config option. As we are 
> setting up a message selector for the message id on receive this 
> normally should work. If not it must be a speciality of the IBM MQ system.
> 
> Christian
> 


--
View this message in context: http://cxf.547215.n5.nabble.com/JMS-Message-Correlation-in-CXF-2-3-tp4830121p4880031.html
Sent from the cxf-user mailing list archive at Nabble.com.

Mime
View raw message