ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQMD issue in message 6.1

Post new topic  Reply to topic
 MQMD issue in message 6.1 « View previous topic :: View next topic » 
Author Message
dipankar
PostPosted: Wed Jul 02, 2008 5:17 am    Post subject: MQMD issue in message 6.1 Reply with quote

Disciple

Joined: 03 Feb 2005
Posts: 171

Hi All,
Environment: Message broker runtime - 6.1 CSD 01
WINDOWS XP.

I was under the impression that without MQMD header broker is not able to put the message into MQ queue. It should throw an exception that message does not have any MQMD header.

But using message broker 6.1, I just noticed that there is no need of having MQMD header for putting message into MQ queue. I am really surprised with this behaviour. I also did not see any documentation on this.

Could anyone give me some light on this? Is this any issue with broker 6.1?

Thanks in advance
_________________
Regards
Back to top
View user's profile Send private message
mqmatt
PostPosted: Wed Jul 02, 2008 5:36 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

No, this is a new deliberate feature.
In v6.1 the MQOutput node makes good any missing MQMD information.

The 6.1 docs (http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=/com.ibm.etools.mft.doc/ab67750_.htm) wrote:
The MQOutput node checks for the presence of an MQMD (WebSphere MQ message descriptor) header in the message tree. If no MQMD is present, the MQOutput node creates an MQMD header in the message tree, and populates it with MQMD default properties. If an MQMD header is found, the MQOutput node checks that it is an MQ type header; if it is not, the Message Context property is set to Default. The MQOutput node treats any other transport headers in the message tree as data.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQMD issue in message 6.1
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.