| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message not getting parsed after recreating the broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| sachinramesh |
 Posted: Fri Sep 05, 2008 2:24 am Post subject: Message not getting parsed after recreating the broker |
 |
|
Disciple
Joined: 20 Feb 2007
Posts: 170
|
My problem is that i had a configmgr running on windows and the broker running on unix.
Recently we had deleted the broker on unix and recreated again .While deleteing the broker we did not delete the BrokerQM and the Brk DB.
Now the flows are deploying into the broker but when we run the flow the i/p message is going to the error flow .
When we trace the flow it says
2008-09-05 12:47:30.300146 10281 UserTrace BIP4040I: The Execution Group 'default' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2008-09-05 12:47:30.300849 10281 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'ISSQM'. The MQCC was '0' and the MQRC was '0'.
2008-09-05 12:47:30.300903 10281 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'ISSQM'.
2008-09-05 12:54:41.421493 7197 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.INPUT'.
2008-09-05 12:54:41.421730 7197 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.INPUT' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2008-09-05 12:54:41.439102 7197 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.INPUT' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2008-09-05 12:54:41.464843 7197 UserTrace BIP6061I: Parser type 'MRM' created on behalf of node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.INPUT' to handle portion of incoming message of length '413' bytes beginning at offset '364'. Parser type selected based on value 'MRM' from previous parser.
2008-09-05 12:54:44.348758 7197 UserTrace BIP2231E: Error detected whilst processing a message 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP.FF_TO_DBXML_PRCG'.
The message broker detected an error whilst processing a message in node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP.FF_TO_DBXML_PRCG'. 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.
2008-09-05 12:54:44.348815 7197 RecoverableException BIP2488E: (.CUP_PCP_TO_UNIFY_SKU7_MF_CUP.PCP.FF_TO_DBXML_PRCG.main, 74.3) Error detected whilst executing the SQL statement 'SET IN_NoOfMRP = CARDINALITY(InputBody.MRDR_RECORD1.MRP[ ]);'.
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.
2008-09-05 12:54:44.348857 7197 ParserException BIP5347E: MtiImbParser2: RM has thrown an unknown exception.
Returned by the RM when an unknown exception is thrown. This is an internal error.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center providing system trace files where possible.
2008-09-05 12:54:44.382244 7197 UserTrace BIP4006I: Message propagated to 'unknown' terminal of filter node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.ERROR.Filter1'.
2008-09-05 12:54:44.806491 7197 Error BIP2232E: Error detected whilst handling a previous error in node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.ERROR.Generating Error Message'.
The message broker has detected an error in node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.ERROR.Generating Error Message' whilst handling a previous error.
See the following messages for details of the exception list associated with the original error. Thereafter messages will be associated with the new error.
2008-09-05 12:54:44.806533 7197 RecoverableException BIP2230E: Error detected whilst processing a message in node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP.FF_TO_DBXML_PRCG'.
The message broker detected an error whilst processing a message in node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP.FF_TO_DBXML_PRCG'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2008-09-05 12:54:44.806545 7197 RecoverableException BIP2488E: (.CUP_PCP_TO_UNIFY_SKU7_MF_CUP.PCP.FF_TO_DBXML_PRCG.main, 74.3) Error detected whilst executing the SQL statement 'SET IN_NoOfMRP = CARDINALITY(InputBody.MRDR_RECORD1.MRP[ ]);'.
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.
2008-09-05 12:54:44.806552 7197 ParserException BIP5347E: MtiImbParser2: RM has thrown an unknown exception.
Returned by the RM when an unknown exception is thrown. This is an internal error.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center providing system trace files where possible.
2008-09-05 12:54:44.806877 7197 UserTrace BIP2231E: Error detected whilst processing a message 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.INPUT'.
The message broker detected an error whilst processing a message in node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.INPUT'. 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.
2008-09-05 12:54:44.806896 7197 RecoverableException BIP2230E: Error detected whilst processing a message in node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.ERROR.Generating Error Message'.
The message broker detected an error whilst processing a message in node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.ERROR.Generating Error Message'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2008-09-05 12:54:44.806907 7197 RecoverableException BIP2488E: (.ERROR_PCP_SKU7_Generating Error Message.main, 122.2) Error detected whilst executing the SQL statement 'SET OutputRoot.XML.Error.MessageAtFailure = InputRoot;'.
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.
2008-09-05 12:54:44.806945 7197 ParserException BIP5347E: MtiImbParser2: RM has thrown an unknown exception.
Returned by the RM when an unknown exception is thrown. This is an internal error.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center providing system trace files where possible.
2008-09-05 12:54:44.807060 7197 UserTrace BIP4006I: Message propagated to 'unknown' terminal of filter node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.ERROR.Filter1'.
2008-09-05 12:54:44.821620 7197 Error BIP2232E: Error detected whilst handling a previous error in node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.ERROR.Generating Error Message'.
The message broker has detected an error in node 'CUP_PCP_TO_UNIFY_SKU7_MF.CUP.PCP_TO_UNIFY.SKU7.ERROR.Generating Error Message' whilst handling a previous error.
See the following messages for details of the exception list associated with the original error. Thereafter messages will be associated with the new error.
what i understood from The trace is that the broker is not able to parse the messaage.
Does anything went wrong with Broker installation.do we need to delete BrokerQM and DB before recreating it.
I am working on MB5.0 |
|
| Back to top |
|
 |
| MrSmith |
| Posted: Mon Sep 08, 2008 12:56 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
First question - you said you deleted the broker - how exactly did you deletet he broekr i.e did you remove it via the config manager then deploy and then delete it or just delete it direct:
If the first then please give more details of the steps performed
If the latter then not suprised the databse tables will still believe the broker exists and you may have corrupt or duplicate records in the DB for the flows or settings. Also if this option your best bet remove the broker properley from the config manager and deploy - ensure it has beeen del;eted from here, then stop the broker, then delete the broker.
You do not have to remove the DB or the QM for broker deletion you just to to ensure that bits of information have not been left "lying" about. |
|
| Back to top |
|
|
| MrSmith |
| Posted: Mon Sep 08, 2008 12:59 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
First question - you said you deleted the broker - how exactly did you delete the broker i.e did you remove it via the config manager then deploy and then stop the service and then delete it or just delete it direct:
If the first then please give more details of the steps performed and their results to ensure a clean removal was achieved
If the latter then not suprised the databse tables will still believe the broker exists possibly and you may have corrupt or duplicate records in the DB for the flows or settings and record retrieval unless specified will normally retireve the first record that matches the criteria and could therefore be wrong (in the case of duplicates). Also if this option your best bet remove the broker properley from the config manager and deploy - ensure it has beeen deleted from here, then stop the broker, then delete the broker.
You do not have to remove the DB or the QM for broker deletion you just to to ensure that bits of information have not been left "lying" about.
Personally i would be inclined to start from scratch if that is possible. |
|
| Back to top |
|
|
| sachinramesh |
| Posted: Mon Sep 08, 2008 2:30 am Post subject: |
|
|
Disciple
Joined: 20 Feb 2007
Posts: 170
|
Thanks for the reply smith,
I had deleted my broker using the command mqsidelete,bcos my config mgr is reciding on another system and that system got crashed..so i could delete the broker from the configmgr adn deploy it..
| MrSmith wrote: |
First question - you said you deleted the broker - how exactly did you delete the broker i.e did you remove it via the config manager then deploy and then stop the service and then delete it or just delete it direct:
If the first then please give more details of the steps performed and their results to ensure a clean removal was achieved
If the latter then not suprised the databse tables will still believe the broker exists possibly and you may have corrupt or duplicate records in the DB for the flows or settings and record retrieval unless specified will normally retireve the first record that matches the criteria and could therefore be wrong (in the case of duplicates). Also if this option your best bet remove the broker properley from the config manager and deploy - ensure it has beeen deleted from here, then stop the broker, then delete the broker.
You do not have to remove the DB or the QM for broker deletion you just to to ensure that bits of information have not been left "lying" about.
Personally i would be inclined to start from scratch if that is possible. |
|
|
| Back to top |
|
|
| MrSmith |
| Posted: Tue Sep 09, 2008 12:40 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
Am not following your reply:
Your config manager is on a remote system i got - but it was that system that crashed with the config manager on it or the broker system?
If it was the config manager system then why did you need to delete the broker, you could have just recreated the config manager and added the broker domain having set up your relevant MQ connection between each QM again. |
|
| 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
|
|
|
|
