We have deployed our service at a customer site.  The service uses Interplay Web Services to query Interplay and retreive details of assets stored in Interplay.  The customer has reported that when our service is running, the Media Indexer shows a thread count alarm with a count of over 100,000. When the service is not running, the thread count drops below 1,000.  Even when the thread count is high, no adverse effects (other than the alarm) are observed.  Is there a way to mitigate this?  Is there anything we should be doing in the configuration of Web Services or our use of the API to reduce thread usage?  Is there any other information I could provide that would be helpful?

Thanks!

Colin,

I spoke to our support engineer here. We would like to get some more information, like what versions are running at the customer site:

• Interplay Production
• IP Web Services