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 » Message set migration issue 5 to 6.1

Post new topic  Reply to topic
 Message set migration issue 5 to 6.1 « View previous topic :: View next topic » 
Author Message
tanishka
PostPosted: Mon Feb 22, 2010 8:21 am    Post subject: Message set migration issue 5 to 6.1 Reply with quote

Centurion

Joined: 24 Nov 2008
Posts: 144

Hi,
I am getting below error when message set migrated from 5 to 6.1. can you plz help it out.


UserTrace BIP2537I: Node 'WMB_XX_XX_001.StringDetails': Executing statement ''BEGIN ... END;'' at ('.WMB_XX_XX_001_StringDetails.Main', '2.2').
2010-02-22 10:26:04.352537 9272 UserTrace BIP2537I: Node 'WMB_XX_XX_001.StringDetails': Executing statement ''SET Environment.Detail = InputRoot.MRM;'' at ('.WMB_XX_XX_001_StringDetails.Main', '5.4').
2010-02-22 10:26:04.353338 9272 UserTrace BIP2231E: Error detected whilst processing a message in node 'WMB_XX_XX_001.MQInput'.
The message broker detected an error whilst processing a message in node 'WMB_XX_XX_001.MQInput'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2010-02-22 10:26:04.353346 9272 RecoverableException BIP2230E: Error detected whilst processing a message in node 'WMB_XX_XX_001.StringDetails'.
The message broker detected an error whilst processing a message in node 'WMB_XX_IXX_001.StringDetails'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2010-02-22 10:26:04.353351 9272 RecoverableException BIP2488E: ('.WMB_XX_IXX_001_StringDetails.Main', '5.4') Error detected whilst executing the SQL statement ''SET Environment.Detail = InputRoot.MRM;''.
The message broker detected an error whilst executing the given statement. An exception has been thrown to cut short the SQL program.
See the following messages for details of the error.
2010-02-22 10:26:04.353367 9272 ParserException BIP5285E: Parsing errors have occurred. Message set name: 'WMB_XX_XX' Message format: 'CWF1' Message type path: '/msg_CM601TDELOGSTOCKDATA00/fill_0'
Review other error messages to find the cause of the errors.
2010-02-22 10:26:04.353372 9272 ParserException BIP5171E: An error occurred while a Custom Wire Format message was being parsed: Current message: 'msg_CM601TDELOGSTOCKDATA00' Current element: 'msg_CM601TDELOGSTOCKDATA00' Path from message root: '' Offset from start of message: 350
See the following errors for more details.
2010-02-22 10:26:04.353377 9272 ParserException BIP5288E: An MRM parsing error has occurred. The bit stream of the message being parsed by the MRM parser is larger than expected for a message of this type. Number of bytes parsed: 350 Actual length of message: 351
When parsing the instance message according to the message model, the parser reached the end of the message definition before it reached the end of the bit stream. Either the message bit stream has been incorrectly constructed, or the message model is incorrect.
Ensure that the message bit stream is correctly formed.
Ensure that the message properties (name, physical format, message set) are correct.
Ensure that the message model for this message type is correct. In particular, check that the element lengths and number of repeats are correct. You should find the message set and message type quoted in other error messages.
If this is a TDS message, enable user trace (debug level) and parse the message. In the trace file check the messages issued by the TDS parser to find the problem.
Back to top
View user's profile Send private message
kimbert
PostPosted: Mon Feb 22, 2010 8:26 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

There were some documented changes of behaviour in the CWF parser between 5.0 and 6.1. Have you checked the migration notes for the CWF parser yet? ( they are in the infocenter ).
Back to top
View user's profile Send private message
tanishka
PostPosted: Mon Feb 22, 2010 9:02 am    Post subject: Reply with quote

Centurion

Joined: 24 Nov 2008
Posts: 144

I chked and it couldn't worked out for this isuue.
Back to top
View user's profile Send private message
kimbert
PostPosted: Mon Feb 22, 2010 9:09 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

What is the structure of your input message?
What is the final byte in the message? ( looks as if the final byte is not being consumed by the CWF parser )

If you could post an example message that would help a lot.
Back to top
View user's profile Send private message
tanishka
PostPosted: Mon Feb 22, 2010 11:22 am    Post subject: Reply with quote

Centurion

Joined: 24 Nov 2008
Posts: 144

I am getting same problem in 5 also. So it could be problem with input message. Trying to get correct input. Keep u posted.
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 » Message set migration issue 5 to 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.