I'm using a handler to log web service request/response. I put a timer around the 'context.getMessage()' call and surprised how long the call takes to get the soap message. For example, a soap message with 2,151 characters would take 2156 milliseconds. On a different service call, a soap message having 2003 characters takes 2954 milliseconds. However, I've seen a soap message having 29,149 characters that would only take 93 milliseconds! Has anybody noticed this? Is there a trick to consistently get good response time from calling getMessage()? Or a better performance alternative to logging service calls?
posted 4 years ago
... and just a bit of additional info:
I am noticing that the delay when calling context.getMessage() are on request (outbound) service calls. On inbound, regardless of how big data is returned from a service, the response time on the function call is quick. SO... why should inbound/outbound matter especially if the size of data on outbound is significantly less?