Has anyone ever faced issues with an ECL Connector spiking
We have an ecl connection, connecting to a DAM system and it is causing the
TcmServiceHost.exe to spike, and not release resources..
We started with a baseline of
400MB with TcmServiceHost and slowly just browsing through the mountpoint, opening and closing components, we noticed in 15 mins with only a few users grew to >1.5GB and does not stop/re- release resources after the testing was completed, a hour later. Even the CPU does not normalize back to 5-7% from where we started, with no activity at all within the instance.
I can't find much in the logs
ecl.log - even when they are set to
Is this a known issue with External Content Library connector or the implementation of it?
Here are the steps to reproduce:
Testing with only 2 concurrent users:
- Open Media Repository mountpoint
- Browse (drill down) in the media directories
- Open Multimedia Components
- Close MM Components
- Repeat - Iterate same process for ~10-15 minutes
- Observe server usage