Message Boards

Tomcat manager

Michael Darretta, modified 7 Years ago.

Tomcat manager

New Member Posts: 18 Join Date: 8/5/15 Recent Posts
I'm using tomcat manager to monitor sessions in my liferay portal.
Is there a tool in liferay admin to do this?
What is recommended way to monitor sessions and server resources?

Thank you
thumbnail
Olaf Kock, modified 7 Years ago.

RE: Tomcat manager

Liferay Legend Posts: 6403 Join Date: 9/23/08 Recent Posts
Michael Darretta:
What is recommended way to monitor sessions and server resources?


Can you elaborate on "monitor"? Is the number of sessions enough? Do you want to see individual activity, usernames, number of requests, performance data?

There's a wealth of JMX data available, you can utilize LCS for some data, and it goes up to utilizing Dynatrace or their competitors for deep insight.
Michael Darretta, modified 7 Years ago.

RE: Tomcat manager

New Member Posts: 18 Join Date: 8/5/15 Recent Posts
we need to see what sessions are active and what attributes are set. and we would like to invalidate/destroy sessions.
i'm using Tomcat Manager on my local but if we can do same in liferay then we do not need to deploy Manager on production servers.

i will look into LCS and other tools you suggested.

Thank You
Michael Darretta, modified 7 Years ago.

RE: Tomcat manager

New Member Posts: 18 Join Date: 8/5/15 Recent Posts
is there any problems or concerns with deploying Tomcat Manager with LifeRay?
thumbnail
David H Nebinger, modified 7 Years ago.

RE: Tomcat manager

Liferay Legend Posts: 14918 Join Date: 9/2/06 Recent Posts
Depending upon your version of Liferay, there can be some issues...

In 6.x, plugins are deployed as separate wars, this means that there are actually session details that can be scattered across the application container for the actual real user. In 7.x this problem goes away since everything is in the OSGi container.

But honestly tomcat doesn't know anything about Liferay authentication. If I use "remember me" checkbox, you might log me out but on my next submit I'm back in (albeit at a clean slate). Same thing if you're using some sort of SSO implementation.

Killing sessions at the app container level is pretty hard core, it's akin to "kill -9" on linux. Is there some reason you need to be so harsh?