Soap Call is taking alot of the resources on the IS

Kris,

Seems that IS is having difficulty parsing the soap message you included above. The pub.soap.utils:getBody service doesn’t fail but only returns null for the body output parm in my test.

Two observations:

  1. The prefix “soapsdk4” is not associated with a namespace The contents of the publishrstouchpoint element appear to be a blob of text or a long string. This is valid XML, but you would not be able to process any of the embedded elements such as PLAN_ID without manually parsing them in IS.

Mark

Your soap envelope is not valid. Try something like this: