| Author |
Message
|
| abiram8 |
 Posted: Thu Apr 04, 2002 5:06 am Post subject: |
 |
|
Master
Joined: 27 Mar 2002
Posts: 207
Location: India
|
Hi
We are trying the Publish Subscribe Programme with MQSI using RFH2 header
The RFH2 Header of NT works fine but with AIX Iam getting Error
What are the changes I have to do with the RFH2 header while using in AIX in terms of ccisd , structId , format etc., in RFH2 Class If some one knows please let me know the Solution.
Thanks
R.Abiram |
|
| Back to top |
|
 |
| kolban |
| Posted: Thu Apr 04, 2002 5:55 am Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
| Please post the details of the error you are receiving as well as any pertinent information that will allow the group to assist. |
|
| Back to top |
|
|
| abiram8 |
| Posted: Thu Apr 04, 2002 6:54 am Post subject: |
|
|
Master
Joined: 27 Mar 2002
Posts: 207
Location: India
|
Hi
Iam sending the Windows NT Event Viewer Output As well as the Trace output
Actually same programme works fine in the Windows NT Server but when I deploy the RFH2 & Required Classes in AIX it gives me following Error
1 EVENT VIEWER OUTPUT
My Event Viewer in Nt Showed me Following Error
I) ( MQSIV2.default ) Header invalid, structure identifier incorrect at offset '0'.
A parser was constructed to process part of a message. That part of the message does not appear to be a valid bitstream for the parser constructed.
Contact your IBM support center.
II) ( MQSIV2.default ) An error occurred in parser 'Root' whilst parsing the field named 'MQRFH2' on behalf of node 'Test.MQInput1'. The data being parsed was '4d442020020000000000000008000000ffffffff0000000022020000b80400004d514852463220200000000000000000414d51204d5153495632202020202020ff19a83c12d0ca00000000000000000000000000000000000000000000000000000000004d5153495f654242535055424c49434154494f4e5f5155455545202020202020202020202020202020202020202020204d51534956322020202020202020202020202020202020202020202020202020202020202020202020202020202020204d5553525f4d5141444d494e16010515000000b70fb66007089e29c94620120904000000000000000000000b20202020202020202020202020202020202020202020202020202020202020201c0000004d5153657269657320436c69656e7420666f72204a617661202020203230303230343032313330323239363520202020000000000000000000000000000000000000000000000000010000000000000000000000ffffffff0000000002000000fc00000022020000b8040000000000000000000000000000b8040000940000003c7073633e3c436f6d6d616e643e5075626c6973683c2f436f6d6d616e643e3c546f7069633e5343422f41452f654242532f4163636f756e744e756d6265723c2f546f7069633e3c514d67724e616d653e4d51534956323c2f514d67724e616d653e3c514e616d653e4d5153495f654242535055424c49434154494f4e5f51554555453c2f514e616d653e3c2f7073633e2020203c0000003c6d63643e3c4d73643e584d4c3c2f4d73643e3c5365743e3c2f5365743e3c547970653e3c2f547970653e3c466d743e3c2f466d743e3c2f6d63643e5247485a5631554e355758334656455952495632424a492c7363622e777261707065722e54726176656c696e674f626a6563744038386136303766392c5343422f41452f654242532f4163636f756e744e756d6265724d5152464832'.
This message gives the name of the field in the parser that was being parsed at the time the error occurred.
You should check for other messages issued with this one for the full context of the error.
III) ( MQSIV2.default ) Error detected whilst processing a message in node 'Test.Trace1'.
The message broker detected an error whilst processing a message in node 'Test.Trace1'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
IV) ( MQSIV2.default ) Exception condition detected on input node 'Test.MQInput1'.
The input node 'Test.MQInput1' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2) My "UserTrace" Gives me the Following Error
Timestamps are formatted in local time, 240 minutes past GMT.
2002-03-30 16:47:20.436000 567 UserTrace BIP2632I: Message being propagated to the output terminal; node 'DEMO_1.MQInput1'.
An input message received from MQSeries input queue in node 'DEMO_1.MQInput1' is being propagated to any nodes connected to the output terminal.
No user action required.
2002-03-30 16:47:20.436000 567 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'DEMO_1.MQInput1' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
The message broker has created a parser of type 'Properties' on behalf of node 'DEMO_1.MQInput1' to handle the first part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '0' bytes long.
No user action required.
2002-03-30 16:47:20.436000 567 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'DEMO_1.MQInput1' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
The message broker has created a parser of type 'MQMD' on behalf of node 'DEMO_1.MQInput1' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '364' bytes long. This parser type was selected as the best match given the value 'MQHMD' from the previous parser.
No user action required.
2002-03-30 16:47:20.436000 567 UserTrace BIP7086I: Node 'DEMO_1.Publication1.PSService1': The Publication Node with Subscription Point '' has received an error code 3008.
The Publication Node with Subscription Point '' has received an error with code 3008. No response message has been sent as one was not requested.
No user action required.
2002-03-30 16:47:20.436000 567 Error BIP2628E: Exception condition detected on input node 'DEMO_1.MQInput1'.
The input node 'DEMO_1.MQInput1' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2002-03-30 16:47:20.436000 567 ImbPubSubEngineNode::evaluate
2002-03-30 16:47:20.436000 567 ImbPubSubEngineNode::evaluate
2002-03-30 16:47:20.436000 567 ImbRootParser::parseNextItem , Root, MQRFH2, 4d442020020000000000000008000000ffffffff0000000022020000b80400004d514852463220200000000000000000414d51204d5153495632202020202020e7b2a53c12f00100000000000000000000000000000000000000000000000000000000004d5153495f654242535055424c49434154494f4e5f5155455545202020202020202020202020202020202020202020204d51534956322020202020202020202020202020202020202020202020202020202020202020202020202020202020204d5553525f4d5141444d494e16010515000000b70fb66007089e29c94620120904000000000000000000000b20202020202020202020202020202020202020202020202020202020202020201c0000004d5153657269657320436c69656e7420666f72204a617661202020203230303230333330313234373230343320202020000000000000000000000000000000000000000000000000010000000000000000000000ffffffff0000000002000000fc00000022020000b8040000000000000000000000000000b8040000940000003c7073633e3c436f6d6d616e643e5075626c6973683c2f436f6d6d616e643e3c546f7069633e5343422f41452f654242532f4163636f756e744e756d6265723c2f546f7069633e3c514d67724e616d653e4d51534956323c2f514d67724e616d653e3c514e616d653e4d5153495f654242535055424c49434154494f4e5f51554555453c2f514e616d653e3c2f7073633e2020203c0000003c6d63643e3c4d73643e786d6c3c2f4d73643e3c5365743e3c2f5365743e3c547970653e3c2f547970653e3c466d743e3c2f466d743e3c2f6d63643e425355583341505430344b31503344304b52495a4d52492c7363622e777261707065722e54726176656c696e674f626a6563744065633733303765392c5343422f41452f654242532f4163636f756e744e756d626572
2002-03-30 16:47:20.436000 567 ImbMqrfh2Parser::refreshElementsFromBitStream , 0
2002-03-30 16:47:21.437000 567 UserTrace BIP2638I: MQPUT to queue 'MQSIV2.DL.Q' on queue manager 'MQSIV2': MQCC=0, MQRC=0; node 'DEMO_1.MQInput1'.
The node 'DEMO_1.MQInput1' attempted to write a message to the specified queue 'MQSIV2.DL.Q' connected to queue manager 'MQSIV2'. The MQCC was 0 and the MQRC was 0.
No user action required.
2002-03-30 16:47:21.437000 567 UserTrace BIP2615I: The MQSeries input node 'DEMO_1.MQInput1' has backed out the message to the backout requeue or the dead letter queue.
Message backout processing has been invoked, and the message has either been backed out by being written to the backout requeue or dead letter queue, as determined by the MQSeries queue manager and queue configuration.
No user action required.
Threads encountered in this trace:
567
Thanks
R.Abiram
|
|
| Back to top |
|
|
| vmcgloin |
| Posted: Fri Apr 05, 2002 4:31 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Are you trying to publish exactly the same message on NT as AIX?
Are you using the local CCSID e.g 819?
Regards,
Vicky
|
|
| Back to top |
|
|
| abiram8 |
| Posted: Fri Apr 05, 2002 4:46 am Post subject: |
|
|
Master
Joined: 27 Mar 2002
Posts: 207
Location: India
|
Actually we are using the same publish in NT & AIX our CCISD value is 1208
|
|
| Back to top |
|
|
| Miriam Kaestner |
| Posted: Mon Apr 08, 2002 12:15 pm Post subject: |
|
|
Centurion
Joined: 26 Jun 2001
Posts: 103
Location: IBM IT Education Services, Germany
|
| It looks as if your RFH2 is not parsed as MQ header, but as body of the message. Your MQMD.Format field must have a value 'MQHRF2 ' to instruct MQ and WMQI that next data is to be parsed as MQRFH2 (this is called MQSeries header chaining). |
|
| Back to top |
|
|
| abiram8 |
| Posted: Tue Apr 09, 2002 3:41 am Post subject: |
|
|
Master
Joined: 27 Mar 2002
Posts: 207
Location: India
|
Hi,
Then in that case why it should work in the Windows NT but not in AIX
This programme works fine in the NT but on AIX it throws Error
R.Abiram
|
|
| Back to top |
|
|
| Naftalanja |
| Posted: Wed Apr 10, 2002 12:03 pm Post subject: |
|
|
Acolyte
Joined: 30 Jan 2002
Posts: 63
Location: Los Angeles
|
guess what Abhiram, i had similar kind of problems while creating the pub/ sub
using both the MQSI and MQ. Let me know more details i should be able to help you get thru this prob. thanx
|
|
| Back to top |
|
|
| abiram8 |
| Posted: Wed Apr 10, 2002 10:32 pm Post subject: |
|
|
Master
Joined: 27 Mar 2002
Posts: 207
Location: India
|
Hi,
I have given the Event Log & the Usertrace Output as in above
To be more presice this problem occures Some times
say if I stop & restart the server
& then again if I try restarting Server it dissapears
The worst part is that I dont know the cause of my problem when it comes
Thanks
R.Abiram
|
|
| Back to top |
|
|
|
|
