| Author |
Message
|
| cc |
 Posted: Thu Aug 09, 2012 12:29 pm Post subject: Event Monitoring event not emmitted due to code page isse |
 |
|
Novice
Joined: 28 May 2008
Posts: 19
|
We are running WMB 8.0.0.0 runtime on Linux. We have configured a flow to emit an event upon entry and exit from several nodes, We have run the mqsichangeflowmonitoring command and created the Subscription to point the event to a local queue. However, when a message arives at the node, we are seeing the following messages in the Broker Log. We have an MQInput Node in the flow that is not having any codepage errors, with the convert option set.
Aug 8 10:23:04 lwmqd001 WebSphere Broker v8000[13374]: (BRKDWMB01.EG_DEV)[38]BIP3915I: Message flow 'EnrollmentInboundAdapterV2' failed to emit a monitoring event from event source 'processBusinessRules.terminal.in'. : BRKDWMB01.1256714d-3801-0000-0080-aa8eada554a5: /build/S000_P/src/DataFlowEngine/Monitoring/ImbEventGatherer.cpp: 712: ImbEventGatherer::constructMonitoringEvent: :
Aug 8 10:23:04 lwmqd001 WebSphere Broker v8000[13374]: (BRKDWMB01.EG_DEV)[38]BIP2132E: Invalid codepage '0' or conversion table 'ibm-0' missing or invalid. : BRKDWMB01.1256714d-3801-0000-0080-aa8eada554a5: /build/S000_P/src/CommonServices/ImbConverter.cpp: 100: ImbConverterCPP::ImbConverterCPP: : ug 8 10:23:04 lwmqd001 WebSphere Broker v8000[13374]: (BRKDWMB01.EG_DEV)[38]BIP3915I: Message flow 'EnrollmentInboundAdapterV2' failed to emit a monitoring event from event source 'processBusinessRules.terminal.in'. : BRKDWMB01.1256714d-3801-0000-0080-aa8eada554a5: /build/S000_P/src/DataFlowEngine/Monitoring/ImbEventGatherer.cpp: 712: ImbEventGatherer::constructMonitoringEvent: : |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Thu Aug 09, 2012 12:32 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| cc |
| Posted: Thu Aug 09, 2012 1:03 pm Post subject: |
|
|
Novice
Joined: 28 May 2008
Posts: 19
|
| processBusinessRules.terminal.in |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Aug 10, 2012 5:04 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| cc |
| Posted: Fri Aug 10, 2012 6:09 am Post subject: |
|
|
Novice
Joined: 28 May 2008
Posts: 19
|
| At this time we are not using a profile, we are defining the events a development time. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Aug 10, 2012 6:11 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So it's complaining that the data has no codepage, and so it can't be converted somehow.
What input node are you using to drive the flow that creates the monitoring event? Not all of the Input nodes in v8.0.0.0 are capable of driving monitoring, if I recall correctly. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Aug 10, 2012 6:17 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| cc wrote: |
| At this time we are not using a profile, we are defining the events a development time. |
I'll wager a pint of ale and some fish & chips at smdavies' chippy that your error will go away once you correctly define a monitoring profile.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| cc |
| Posted: Fri Aug 10, 2012 10:23 am Post subject: |
|
|
Novice
Joined: 28 May 2008
Posts: 19
|
| mqjeff. The input node is an MQInput NOde. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Aug 10, 2012 10:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| cc wrote: |
| mqjeff. The input node is an MQInput NOde. |
Well, that one should work.
Why does the broker think that the message has a CCSID of '0'? that's what the error is complaining about. |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Fri Aug 10, 2012 11:33 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Normal debugging method can perhaps be usefull here. Add trace node before malpracticing node, echo whole root and research is you message valid.
--
Marko |
|
| Back to top |
|
|
|
|
