Hi All,

We are currently using webMethods version 10.15 and have recently observed that the WSDL thread invocation count remains persistent even after the service completes successfully.

There have been no recent code changes or patch installations. Additionally, this issue is not limited to any specific WSDL - it is occurring across all invoked provider WSDLs.

We would appreciate any insights or suggestions from the experts here to help us identify the root cause and potential resolution.

Thank you in advance for your support.

Best regards,
Sagar ks

Hi Sagar,

Does even after IS restart the Thread Count remains the same?

Say PartnerOrderProcessing has Thread Count as 4 and even after Restart the Thread Count remains as 4.

Also, has this Persistent Thread Count behaviour been from the beginning or it has started happening recently?

Hi All,

We are currently using webMethods version 10.15 and have recently observed that the WSDL thread invocation count remains persistent even after the service completes successfully.

There have been no recent code changes or patch installations. Additionally, this issue is not limited to any specific WSDL - it is occurring across all invoked provider WSDLs.

We would appreciate any insights or suggestions from the experts here to help us identify the root cause and potential resolution.

Thank you in advance for your support.

Best regards,
Sagar ks

Hi Kailash,

After IS restart, the service invocation would not be visible until its invoked.  

Lets assume PartnerOrderProcessing has invoked once & we would see service Count as 1 even after service is completed successfully.

This count would be as (1) until it invoked again- now the count becomes (2) when invoked & would increment every time its invoked.

But the problem is - we always see the invocation count next to the WSDL. This was not happening earlier (prior to 1 month from 25th May)

Not sure if this is a new functionality or a bug. Please let me know if any additional details are required from my end.

Hi Sagar,

Does even after IS restart the Thread Count remains the same?

Say PartnerOrderProcessing has Thread Count as 4 and even after Restart the Thread Count remains as 4.

Also, has this Persistent Thread Count behaviour been from the beginning or it has started happening recently?

Hi All,

We are currently using webMethods version 10.15 and have recently observed that the WSDL thread invocation count remains persistent even after the service completes successfully.

There have been no recent code changes or patch installations. Additionally, this issue is not limited to any specific WSDL - it is occurring across all invoked provider WSDLs.

We would appreciate any insights or suggestions from the experts here to help us identify the root cause and potential resolution.

Thank you in advance for your support.

Best regards,
Sagar ks

Hi Sagar - I ran into the same issue at a customer recently. It's a known issue and should be solved by PIE-95921 due to be included in IS_10.15_CoreFix_20. I was told this is cosmetic in nature and should not have a performance impact. The threads are in fact being returned to the pool successfully. There is a hotfix available if you desire and you can contact support to obtain it. 

Readme for PIE-95921 states: 
After applying a fix that includes PIE-87732: IS Dashboard service invocation counts mismatch, the number of running services includes SOAP services that executed to completion. Now, Integration Server properly decrements the number of running services for SOAP services

Hope that helps!

John Shoup

https://nibl.tech/

Hi Kailash,

After IS restart, the service invocation would not be visible until its invoked.  

Lets assume PartnerOrderProcessing has invoked once & we would see service Count as 1 even after service is completed successfully.

This count would be as (1) until it invoked again- now the count becomes (2) when invoked & would increment every time its invoked.

But the problem is - we always see the invocation count next to the WSDL. This was not happening earlier (prior to 1 month from 25th May)

Not sure if this is a new functionality or a bug. Please let me know if any additional details are required from my end.

Hi Sagar,

Does even after IS restart the Thread Count remains the same?

Say PartnerOrderProcessing has Thread Count as 4 and even after Restart the Thread Count remains as 4.

Also, has this Persistent Thread Count behaviour been from the beginning or it has started happening recently?

Hi All,

We are currently using webMethods version 10.15 and have recently observed that the WSDL thread invocation count remains persistent even after the service completes successfully.

There have been no recent code changes or patch installations. Additionally, this issue is not limited to any specific WSDL - it is occurring across all invoked provider WSDLs.

We would appreciate any insights or suggestions from the experts here to help us identify the root cause and potential resolution.

Thank you in advance for your support.

Best regards,
Sagar ks