| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Problem with '_' (underscore) character when getting parsed. |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Tue Jun 30, 2009 4:20 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| santy wrote: |
| To add more analysis to it - when I select the Validation property of RCD node to "None", the messages gets processed successfully. |
Unsurprising - unless you're using validation the XMLNSC parser doesn't use a message set.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Jun 30, 2009 4:44 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| - I have used the message set name. |
No you have not.
The name of your message set is not 'NBNECJG002001'!
You have used the 13-character message set identitfier, which the error message has clearly told you is incorrect.
Please change the message flow so that OutputRoot.Properties.MessageSet is set to the message set name. |
|
| Back to top |
|
|
| santy |
| Posted: Tue Jun 30, 2009 4:47 am Post subject: |
|
|
Centurion
Joined: 03 Nov 2006
Posts: 141
|
but this is happening only in 6.1, this is working fine in 6.0
and I have not explicitely setting the message set name as 13 char identifier, it is the Properties tree which is getting populated by default with such identifiers.
UserTrace BIP4060I: Data ''( ['MQROOT' : 0x10966b750]
(0x01000000):Properties = ( ['MQPROPERTYPARSER' : 0x123fed368]
(0x03000000):MessageSet = 'NBNECJG002001' (CHARACTER)
(0x03000000):MessageType = 'DEFAULT_CWF' (CHARACTER)
(0x03000000):MessageFormat = 'CWF' (CHARACTER)
(0x03000000):Encoding = 546 (INTEGER)
(0x03000000):CodedCharSetId = 437 (INTEGER)
(0x03000000):Transactional = TRUE (BOOLEAN)
(0x03000000):Persistence = FALSE (BOOLEAN)
(0x03000000):CreationTime = GMTTIMESTAMP '2009-06-30 12:39:20.740' (GMTTIMESTAMP)
(0x03000000):ExpirationTime = -1 (INTEGER)
(0x03000000):Priority = 0 (INTEGER)
(0x03000000):ReplyIdentifier = X'000000000000000000000000000000000000000000000000' (BLOB)
(0x03000000):ReplyProtocol = 'MQ' (CHARACTER)
(0x03000000):Topic = NULL
(0x03000000):ContentType = '' (CHARACTER)
(0x03000000):IdentitySourceType = '' (CHARACTER)
(0x03000000):IdentitySourceToken = '' (CHARACTER)
(0x03000000):IdentitySourcePassword = '' (CHARACTER)
(0x03000000):IdentitySourceIssuedBy = '' (CHARACTER)
(0x03000000):IdentityMappedType = '' (CHARACTER)
(0x03000000):IdentityMappedToken = '' (CHARACTER)
(0x03000000):IdentityMappedPassword = '' (CHARACTER)
(0x03000000):IdentityMappedIssuedBy = '' (CHARACTER)
) |
|
| Back to top |
|
|
| santy |
| Posted: Tue Jun 30, 2009 5:01 am Post subject: |
|
|
Centurion
Joined: 03 Nov 2006
Posts: 141
|
As suggested by you, I have tried by writing code in Compute node to set name of message set instead of 13 char identifier, but still I'm getting the same error, just the diff. is -
The XMLNSC parser cannot find a deployed message set with name ''TEST".
Here is the Properties tree -
( ['MQROOT' : 0x109669b18]
(0x01000000):Properties = ( ['MQPROPERTYPARSER' : 0x123f54320]
(0x03000000):MessageSet = 'TEST' (CHARACTER)
(0x03000000):MessageType = 'DEFAULT_CWF' (CHARACTER)
(0x03000000):MessageFormat = 'CWF' (CHARACTER)
(0x03000000):Encoding = 546 (INTEGER)
(0x03000000):CodedCharSetId = 437 (INTEGER)
(0x03000000):Transactional = TRUE (BOOLEAN)
(0x03000000):Persistence = FALSE (BOOLEAN)
(0x03000000):CreationTime = GMTTIMESTAMP '2009-06-30 12:55:02.860' (GMTTIMESTAMP)
(0x03000000):ExpirationTime = -1 (INTEGER)
(0x03000000):Priority = 0 (INTEGER)
(0x03000000):ReplyIdentifier = X'000000000000000000000000000000000000000000000000' (BLOB)
(0x03000000):ReplyProtocol = 'MQ' (CHARACTER)
(0x03000000):Topic = NULL
(0x03000000):ContentType = '' (CHARACTER)
(0x03000000):IdentitySourceType = '' (CHARACTER)
(0x03000000):IdentitySourceToken = '' (CHARACTER)
(0x03000000):IdentitySourcePassword = '' (CHARACTER)
(0x03000000):IdentitySourceIssuedBy = '' (CHARACTER)
(0x03000000):IdentityMappedType = '' (CHARACTER)
(0x03000000):IdentityMappedToken = '' (CHARACTER)
(0x03000000):IdentityMappedPassword = '' (CHARACTER)
(0x03000000):IdentityMappedIssuedBy = '' (CHARACTER) |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jun 30, 2009 5:24 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
Hi Santy,
You should be able to fix this on your own now - you've probably typed the name wrong, or in the wrong case, or forgotten to (re)deploy it.
The reason this does not happen in v6.0 is because v6.0 XMLNSC did not support validation, so it did not need a message set. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
