AnsweredAssumed Answered

SOAP call open sessions have increased causing long running state

Question asked by britto.parthalomew on Aug 18, 2016
Latest reply on Aug 22, 2016 by Srinivas Chandrakanth Vangari



We have a case where Boomi invokes SOAP client to get some data. Boomi used to pull various entity data (say 5) using various sub processes in the same open session (1 or 2 sessions). It was working fine and used to take just 30 to 60 minutes which was normal. Suddenly from 28th July the same processes started taking 13 to 17 hours creating almost 60 80 open sessions to SOAP. There was no change in Boomi and web service. We have been breaking our head to identify the cause for this but clueless. 

Later what i identified was for another similar requirement, one of my team members, have copied the same process and deployed in DEV and TEST atom. The SOAP URL used was the same as the PROD (they are separate instance). He started his testing on 27th and the process took almost 13 hours. Thats where it all started and the PROD too started taking 13 to 17 hours from then. 

My question is when his processes are only in TEST atom how it could affect PROD? What could be the root cause?

Has anyone faced similar issue and found a fix. 


Your help would be greatly appreciated