SOAP service WSDL when hit from external doesnt create WO.
Hi
Am working on exposing a case so that users can just invoke this case by hitting wsdl from outside.
The process is working perfectly fine when running and testing soap service from with in developer studio. Its doing necessary validations and creates a WO.
The same is not happening while hitting the WSDL from SOAP UI. All the log messages with in the service activity is logging properly except for creating of WO
Thanks in advance
Sanal
Accepted Solution
Aaseya IT Services Pvt Ltd
KW
Hey @AsifHasan,
This is resolved, as it was due to some ConcurrentModification exception being thrown each time when we tried updating pyWorkPage.
This is believe as due to lock not getting acquired properly on the same page each time when we tried hitting the WSDl from SOAP UI.
I have made a work around on it by assigning it to a new operator and calling WorkLock activity before creating work object(call CreateWorkPage and Add activities).
Thanks for response.
EPAM Systems, Inc.
ES
Hi Sanal,
Thanks for posting on PSC.
I have few questions to understand the issue:-
- Is there authentication failure?
- Have you tried configuring error flow to trace the error?
- Is response coming from soap wizard correctly creating pages on the clipboard?
- Try configuring flag properties in response data transform to understand where the error is appearing.
Kindly share the logs for further investigation as well.
Regards,
Asif
Accepted Solution
Aaseya IT Services Pvt Ltd
KW
Hey @AsifHasan,
This is resolved, as it was due to some ConcurrentModification exception being thrown each time when we tried updating pyWorkPage.
This is believe as due to lock not getting acquired properly on the same page each time when we tried hitting the WSDl from SOAP UI.
I have made a work around on it by assigning it to a new operator and calling WorkLock activity before creating work object(call CreateWorkPage and Add activities).
Thanks for response.
Aaseya IT Services Pvt Ltd
KW
Forgot to mention: The issue was rectified by tracing the thread which gets created each time when we hit the WSDL from SOAP UI ( even though hit is from outside pega, thanks to Pega :) that it creates a new thread which we can trace remotely )