| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP3915I: Message flow failed to emit an event |
« View previous topic :: View next topic » |
| Author |
Message
|
| paulau |
 Posted: Mon Feb 06, 2017 5:09 pm Post subject: BIP3915I: Message flow failed to emit an event |
 |
|
Novice
Joined: 06 Feb 2017
Posts: 19
|
Hi,
We are using a monitoring profile to generate events. The events from the generated message flow in the REST API are OK. The first event from the RESTRequest node in dynamic library sub flow gets the following errors.
The flow works OK and the node successfully invokes the cloud provider.
Any suggestions other than a PMR?
Platform is RHEL 7.2 IIB 10.0.0.7
Feb 7 11:26:57 esb1-d1 IIB[63759]: IBM Integration Bus v10007 (IBNDDEV1.server01) [Thread 63839] (Msg 1/2) BIP3915I: Message flow 'gen.API_ESB_Person' failed to emit a monitoring event from event source '/v1/provider/alp/operation/read/uid/{uid} (Implementation).getALPPerson.GET/public/api/v1/users/{userIdOrEmail}.terminal.in'.
Feb 7 11:26:57 esb1-d1 IIB[63759]: IBM Integration Bus v10007 (IBNDDEV1.server01) [Thread 63839] (Msg 2/2) BIP2132E: Invalid codepage '0' or conversion table 'ibm-0' missing or invalid. |
|
| Back to top |
|
 |
| ruimadaleno |
| Posted: Tue Feb 07, 2017 2:04 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
not using restNode here but i have hit this error dozens of times.
Monitoring depends on the information stored in the environment tree (outputroot/inputroot), like root.properties.codecharsetid adn root.properties.encoding
Check you message flow and validate that the environment tree is preserved through nodes.
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Feb 07, 2017 5:29 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Typically codepage or ccsid 0 means default code page of the Queue Manager and the value gets resolved and replaced when serializing in the output node... You should never encounter that value on an input node...
You are seeing the value on the in terminal of the request node. This means that the flow does not set properly the CCSID of the request... As you are presumably using an HTTP Request node, the value should not be authorized.
Check the values of Root.Properties.CodedCharSetId, HTTP Request header for content type and codepage etc... and verify that they are consistent.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| paulau |
| Posted: Tue Feb 07, 2017 1:04 pm Post subject: |
|
|
Novice
Joined: 06 Feb 2017
Posts: 19
|
Thanks guys. Your correct, the code saving the properties to the environment created the correct structure however the values were NULL.
Restoring a NULL CodedCharSetId does produce an error saying its invalid! |
|
| 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
|
|
|
|
