| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Monitoring Events are not emitted with input validation on |
View previous topic :: View next topic |
| Author |
Message
|
| siddharth_s10 |
 Posted: Mon Jul 15, 2013 10:11 pm Post subject: Monitoring Events are not emitted with input validation on |
 |
|
Newbie
Joined: 15 Jul 2013
Posts: 2
|
Hi,
I am not getting any erros when i am sending the wrong input message (for the field whose data type is "LONG" i am sending an Empty Tag) in Dev env. The input validation is “Content and Value” and Parsing Option as “ON Demand” with Monitoring Enabled. Also no monitoring event is getting emitted. But if i am sending the same input message in local it is throwing error.
Also if the input validation is “Content and Value” and Parsing Option as “ON Demand” and i Disabled the monitoring, then error is thrown.
Kindly suggest some work around so that i could get proper error and also i can generate the Monitoring events. (I need to keep Parsing option as "On Demand").
Thanks,
Siddharth |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Jul 15, 2013 10:19 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
On demand means that the field is not validated until it is used.
Monitoring events should be thrown whenever the message processing passes the point the event is declared on.
If you can show, using user trace, that the flow passes a point where an event is defined to be emitted, and you can show that the event that would be generated at that point is not built from entirely empty data, then you have a found a bug in the product.
If you can show that at some point in the flow, you have accessed an illformed field and the validation of Content and Value has failed to cause an exception to be thrown, you have likely found a bug in the product.
It's slightly possible that if a monitoring event is the only thing that is accessing the known bad field, that the monitoring event will fail to be emitted and that the flow will fail to throw an exception. But I'd believe that represents a bug in the product as well. The event should still be emitted, but with empty data or exception information - in my opinion.
There's likely a lot of room for change in behavior between various levels of Broker, as well. So if you're at an early level of Broker v7, applying the most recent fixpack of v7 may change behavior, and you may see altered behavior if you move to v8 or v9 too. |
|
| Back to top |
|
|
| siddharth_s10 |
| Posted: Mon Jul 15, 2013 10:39 pm Post subject: |
|
|
Newbie
Joined: 15 Jul 2013
Posts: 2
|
Hi Jeff,
Thanks for the reply.
The field which i am sendig in input with wrong value that field is getting utilized in compute node. In the User trace i can see that its throwing error for this field but then its further processing the message and generating the output. Also according to user trace Monitoring event failed to emit.
Thanks,
Siddharth |
|
| 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
|
|
|
|
