| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Deployed configuration bombs on repeating elements |
« View previous topic :: View next topic » |
| Author |
Message
|
| smahon |
 Posted: Fri Sep 06, 2002 4:02 am Post subject: Deployed configuration bombs on repeating elements |
 |
|
Apprentice
Joined: 24 Apr 2002
Posts: 29
|
I am administering a working test and now 100% down production environment (Win2k, MSCluster, MQSI 2.0.2 CSD3) when I encounter the following: Take a working message flow, export it from test and import it into a working production environment (3 months now). After performing a full deploy, the production environment will no longer process any messages with repeating elements. An exception is raised claiming a CWF read buffer overflow, always on the first value of the repeating element. The broker then hangs and becomes unresponsive. This has affected all messages with repeating elements, even though I did not change any message sets and only one flow. I tried reverting to saved message sets and flows but this does not correct the problem. I tried deleting all the message sets and flows from both the config manager and brokers, deploying empty brokers and reimporting/deploying, but this has no effect. This all works in the test environment and the input data was checked and verified to be the same in both envieonments. Please help! Here is a portion of the trace:
(
(0x1000000)RecoverableException = (
(0x3000000)File = 'F:/build/S202_P/src/DataFlowEngine/ImbTraceNode.cpp'
(0x3000000)Line = 291
(0x3000000)Function = 'ImbTraceNode::evaluate'
(0x3000000)Type = 'ComIbmTraceNode'
(0x3000000)Name = '7b681482-e900-0000-0080-ed58baf9ed9c'
(0x3000000)Label = 'ACTtoSiebel.Trace1'
(0x3000000)Text = 'Caught exception and rethrowing'
(0x3000000)Catalog = 'MQSIv202'
(0x3000000)Severity = 3
(0x3000000)Number = 2230
(0x1000000)ParserException = (
(0x3000000)File = 'F:/build/S202_P/src/MTI/MTIforBroker/MtiImbParser/mtiImbParser.cpp'
(0x3000000)Line = 1297
(0x3000000)Function = 'MtiImbParser::parseFirstChild'
(0x3000000)Type = ''
(0x3000000)Name = ''
(0x3000000)Label = ''
(0x3000000)Text = 'MTI Parsing Errors have occurred'
(0x3000000)Catalog = 'MQSIv202'
(0x3000000)Severity = 3
(0x3000000)Number = 5285
(0x1000000)ParserException = (
(0x3000000)File = 'F:/build/S202_P/src/MTI/MTIforBroker/MtiImbParser/mtiImbParser.cpp'
(0x3000000)Line = 577
(0x3000000)Function = 'MtiImbParser::parseCwfBuffer'
(0x3000000)Type = ''
(0x3000000)Name = ''
(0x3000000)Label = ''
(0x3000000)Text = 'Error Extracting a mesage from the record oriented bitstream.'
(0x3000000)Catalog = 'MQSIv202'
(0x3000000)Severity = 3
(0x3000000)Number = 5125
(0x1000000)Insert = (
(0x3000000)Type = 2
(0x3000000)Text = '-15'
)
(0x1000000)ParserException = (
(0x3000000)File = 'F:/build/S202_P/src/MTI/MTIforBroker/MtiImbParser/mtiImbParser.cpp'
(0x3000000)Line = 2834
(0x3000000)Function = 'MtiImbParser::handlecwferr'
(0x3000000)Type = ''
(0x3000000)Name = ''
(0x3000000)Label = ''
(0x3000000)Text = 'CWF Read Buffer Overflow'
(0x3000000)Catalog = 'MQSIv202'
(0x3000000)Severity = 3
(0x3000000)Number = 5181
(0x1000000)Insert = (
(0x3000000)Type = 2
(0x3000000)Text = '-15'
)
(0x1000000)Insert = (
(0x3000000)Type = 5
(0x3000000)Text = 'GetMessageFromLegacyBitstream'
)
(0x1000000)Insert = (
(0x3000000)Type = 5
(0x3000000)Text = 'DMKG9T007I001'
)
(0x1000000)Insert = (
(0x3000000)Type = 5
(0x3000000)Text = 'ACTtoSiebel'
)
(0x1000000)Insert = (
(0x3000000)Type = 5
(0x3000000)Text = 'MRM'
)
(0x1000000)Insert = (
(0x3000000)Type = 5
(0x3000000)Text = 'ACT_LoanTerm'
)
)
)
)
)
) |
|
| Back to top |
|
 |
| smahon |
| Posted: Sat Sep 07, 2002 12:24 pm Post subject: Problem solved....APAR IY32892 |
|
|
Apprentice
Joined: 24 Apr 2002
Posts: 29
|
| This issue has been resolved with the application of APAR IY32892. MQSI support was able to reproduce the problem and correct it with this efix that was developed about 2 months ago. It seems there was a bug in the latest MQSI CSD (CSD3) that changed the behavior of a message set when deployed from a Config Manager at MQSI level 2.0.X and CSD3 (us). We verified that by either removing CSD3 or installing the efix the problem was corrected. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
