I'm wondering if someone can help me in figuring out why the above service stops indexing VM's @ a certain point until the service is restarted. Seems to affect the hardware status tab too, but don't hear much about that.
The service continuously runs w/ no problems that seems evident in the Windows app/sys logs. I've also looked @ the tomcat logs, but nothing really jumps out to me as causing this issue. Any ideas out there? Seen this issue?
I think I've figured out my own issue. Seems I may be lacking memory allocation for my tomcat service, which is odd since I chose the medium option when upgrading to vSphere 4.1. Details can be found here in case anyone else sees a similar issue.