| Author |
Message
|
| mqceries |
 Posted: Fri Mar 09, 2012 3:44 pm Post subject: Frequent Restarts of Execution Group. |
 |
|
Acolyte
Joined: 02 Dec 2011
Posts: 70
|
We are having frequent restarts of an Execution group today.
Os : Windows
Broker : 6.1.09
I checked the Execution group for any new deployments, there are no new deployments or modifications made on this execution groups. Messages are failing that are put on the flows running in that Execution group.
Some of the Messages from the Event Viewer
| Quote: |
Execution group finished with Configuration message.
A command response will be sent to the broker.
No user action required.
------
Source field ''700072006f00640070006f00770065007200620072006f006b0065007200'' is too long for a target field of length '12' when converting from Unicode to codepage '437'.
When the character data in the source field is converted to the target codepage, the resulting character string is longer than the defined length of the target field.
Correct the application or compute expression that generated the message. Ensure that the definition of the field in the output message is correctly specified, bearing in mind the codepage required for the message, and check that the origin of the data within the source field is providing correct data.
-----
Error in parser ''MQMD'' whilst writing the field named ''UserIdentifier'' to the bitstream.
This message gives the name of the field in the parser that was being written at the time the error occurred. The parser was trying to write ''prodpowerbroker'' into this field.
You should check for other messages issued with this one for the full context of the error.
---
Exception condition detected while sending deferred message of type 1. Failure count is 1.
The publish/subscribe service detected an error whilst sending a deferred message of type 1, where 1 indicates an administrative event publication, 2 indicates a command message destined for another broker, and 3 indicates an internal command message destined for another execution group. The number of times this message has been tried is 1. The attempt to send the message will be retried later, unless the message is an administrative event publication, in which case it will only be retried three times before being discarded. 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.
----
Publish/Subscribe state recovery completed.
Recovery of the Publish/Subscribe state from the broker's database is complete.
This message is for information only. No action is required.
---
Broker process terminating abnormally: The following diagnostic information will be required when contacting IBM: '
Severe Abend Error detected.
For full details see Abend File: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/HWSBRKP7.DI.42048.46820.Abend
A summary of the Error follows:
An Unhandled Exception detected in process 42048, on thread 0xB6E4.
Type: EXCEPTION_ACCESS_VIOLATION (C0000005).
Address: 001B:28730352.
The thread could not write to memory address 0x00000000.
'.
A broker process is terminating abnormally.
|
I hope this one will be a think to look for
| Quote: |
Broker process terminating abnormally: The following diagnostic information will be required when contacting IBM: '
Severe Abend Error detected.
For full details see Abend File: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/HWSBRKP7.DI.42048.46820.Abend
A summary of the Error follows:
An Unhandled Exception detected in process 42048, on thread 0xB6E4.
Type: EXCEPTION_ACCESS_VIOLATION (C0000005).
Address: 001B:28730352.
The thread could not write to memory address 0x00000000.
'.
A broker process is terminating abnormally.
|
Please advice me what else to be checked and what to be done.
Thanks |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Mar 09, 2012 3:57 pm Post subject: Re: Frequent Restarts of Execution Group. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqceries wrote: |
| Please advice me what else to be checked and what to be done. |
By some means, a publication is trying to be made with the user id quoted in the User Id field (not sure why you'd want to) but that user id doesn't fit. You'd hope that when the Publication node tried & failed to serialize the bitstream it would simply abend (as indicated) and not cause the process to abend as well but there you go. I imagine it happening now because the code's been wrong for a while & you've just hit the circumstance.
First point is stop whatever's resulting in that publication. That will stop the abends & the restarts.
Second point is to review the design that requires the user id to be set, and the code that doesn't check the value against the field length.
Third point is to upgrade to WMBv7. Nothing to do with the problem, just something you should be planning
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqceries |
| Posted: Fri Mar 09, 2012 4:18 pm Post subject: |
|
|
Acolyte
Joined: 02 Dec 2011
Posts: 70
|
Thanks Vitor,
My only problem is that this was started just today, all together this was stable server ..the other eg having trouble with configuration time out.
I will check what you advised, is there anyway to see what its trying to publish. I am quite certain there are no deployments. Will right clicking Eg and cancelling deployments will cure this. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Mar 10, 2012 9:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqceries wrote: |
| My only problem is that this was started just today, all together this was stable server |
The publish problem can be some kind of input and/or code problem that's been waiting to happen. ..
| mqceries wrote: |
| the other eg having trouble with configuration time out. |
Then your assertion that there have been no deployments is false.
| mqceries wrote: |
| I am quite certain there are no deployments. Will right clicking Eg and cancelling deployments will cure this. |
If there are no deployments why is there a configuration timeout on one EG?
If there are no deployments then how can cancelling the non-existant deployments help?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Mar 10, 2012 2:22 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mqceries wrote: |
| Will right clicking Eg and cancelling deployments will cure this. |
Absolutely not!   As Vitor has told you, you have a flow that is trying to write a userid into the corresponding MQMD field. The length of the string exceeds the max length for the MQMD user id field. This is the error you need to fix.
Stop the publish flow to avoid constant restarting of the e.g., redeploy with correct length user id and everything should be fine again.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqceries |
| Posted: Sat Mar 10, 2012 6:46 pm Post subject: |
|
|
Acolyte
Joined: 02 Dec 2011
Posts: 70
|
| Very interesting, can you please more info how to check. Thanks for your advise. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Mar 10, 2012 7:41 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqceries wrote: |
| can you please more info how to check. |
Check what? How this user id is getting into the MQMD? It's your code, debug it as you would anything else.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqceries |
| Posted: Wed Mar 14, 2012 12:45 pm Post subject: |
|
|
Acolyte
Joined: 02 Dec 2011
Posts: 70
|
we are getting different errors today for the execution group
| Quote: |
Message broker internal error: diagnostic information 'Severe Abend Error: Double Faulted during Abend Processing in Function ImbAbend::logSystemErrorAndTerminateProcessInternal(), Terminating Process'.
An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The diagnostic information associated with this message is: 'Severe Abend Error: Double Faulted during Abend Processing in Function ImbAbend::logSystemErrorAndTerminateProcessInternal(), Terminating Process'.
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.
-------------------------------------------
Source field ''700072006f00640070006f00770065007200620072006f006b0065007200'' is too long for a target field of length '12' when converting from Unicode to codepage '437'.
When the character data in the source field is converted to the target codepage, the resulting character string is longer than the defined length of the target field.
Correct the application or compute expression that generated the message. Ensure that the definition of the field in the output message is correctly specified, bearing in mind the codepage required for the message, and check that the origin of the data within the source field is providing correct data.
----------------------
Message broker internal error: diagnostic information '
Severe Abend Error detected.
For full details see Abend File: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/HWSBRKP7.DI.33856.30900.Abend '.
An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The diagnostic information associated with this message is: '
Severe Abend Error detected.
For full details see Abend File: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/HWSBRKP7.DI.33856.30900.Abend '.
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.
|
Few lines from abend file
| Quote: |
Abend Record for PID: 33856 TID: 0x78B4 on: Wed Mar 14 14:39:31 2012
---> Location <---
File: F:\build\S610_P\src\CommonServices\Win32\ImbAbend.cpp
Line: 3097
Function: ImbAbend::newHandler
AbendAction: 3
---> Inserts <---
Failed to allocate memory
165915
---> Last Errors <---
Note these error codes are not necessarily reliable
GetLastError() returned: 0
errno returned: 0
|
|
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Mar 14, 2012 2:14 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqceries wrote: |
| we are getting different errors today for the execution group |
And yet the cause is the same:
| mqceries wrote: |
| Source field ''700072006f00640070006f00770065007200620072006f006b0065007200'' is too long for a target field of length '12' when converting from Unicode to codepage '437'. |
i.e. your code is hosed; as indicated in the error:
| mqceries wrote: |
| Correct the application or compute expression that generated the message. Ensure that the definition of the field in the output message is correctly specified, bearing in mind the codepage required for the message, and check that the origin of the data within the source field is providing correct data. |
etc
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
