XI52 on 184.108.40.206.
I know one answer to this... which is if the processing is set to passthrough. This is not my case. Request/Response is set to JSON on an MPG.
We are trying to debug a situation where messages are being randomly "dropped". So, I have a probe on the MPG that handles the servicing of the requests. Here is the traffic pattern:
- JSON Inbound to MPG-1
- MPG-1 forwards the JSON request to an APP server
- The APP server then sends a different JSON request out to a different MPG-2
- MPG-2 sends the request on to another server.....
At least, that's the happy day scenario. Every so often, DataPower is throwing an error with "Missing Input on Action". There is no rhyme or reason to when or why. The same exact request can go through successfully many times, then it just fails. There are many different requests. Same thing. Some go through, others don't. It isn't always the same request that fails.
Anyway... enough of that. The service has 2 request rules, 1 Response rule, and 1 Error rule. In error rule, there is a transform that creates a JSON error response. I have setup an XSLT parameter to give it a simple uniquely identifying String to tell us which device (on an AO load balanced pair of DPs) is throwing the error. (Also no science to which appliance generates the error).
So, we start sending requests through. Say we send 5 requests through and 2 of them fail. We clearly see the probes on the 3 that succeed. However, I do not see the probe on the 2 that fail, yet, we get back the JSON error transformed by the appliance!
Again, policy is JSON/JSON, no passthrough.
Does anyone have any explanation why I cannot see anything in the probes just because the request fails?