Roberto,
We have been load testing 2.1.3 and 2.2, but not necessarily letting
them sit idle. So, I cannot really verify what you are seeing. However,
there are plenty of potential sources of this behavior. One that comes
to mind is the PAM which monitors portlet applications for deployment
changes. There are also background processes to manage internal caches.
However, with these things, its almost always something one would not
initially expect.
I would assume you are seeing real behavior and not something unique.
Further research would be required to know for sure, hence the JIRA issue.
Randy
Roberto Rossi wrote:
I wll do it in the next days... but can you confirm this strange
behaviour or this is a very personal and isolated issue?
Is there a Jetspeed running thread consuming cpu or memory?
ROb.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
