During some performance analysis of our WebSphere Portal 5.1 portal, we saw 
some unsettling numbers from the resource analyzer for sessions.  We devised
 a focused test to dig deeper into this.

We have a single page with one struts portlet and two web clipping portlets.
  When a user goes to this page, the the live session count for the server g
oes to 3.  The struts portlet application I know is tapping into the session
, so I expect to see 1.  Bu
t why wouuld the web clipping portlets create sessions?

If we expand the resource analyzer session detail, we can see statictics for
 each *.war file, such as wps.war, our portlet application's *.war file, and
 the Web Portlets containign the web clipping portlets.  It confused us even
 more than both wps.war and
our portlet applications' WAR showed sessions!

Why does wps.war (the portal) and our portlet application (ourportletapp.war
) get a session?  Aren't the portlet sessions just part of the overall HttpS
ession?

And why are the web clipping portlets incurring a session?

[ Post a follow-up to this message ]

There is a difference in between portal and portlet session. There is
one global "portal" session. But apart from that, each application can
have its own "portlet" session. The session for portlets is created when
a portlet requires a session. Therefore, it is possible, that for some
reason the web-clipping portlets create a portlet session. When JSPs are
rendered, it is also possible that a session gets created. If you do not
want this to happen, the JSP has to contain a directive like <%@ page
session=false %>. If the JSP of the portlet does not contain this, a
session would automatically get created when the JSP is rendered.


Oliver

[ Post a follow-up to this message ]

But a portlet session is just an abstraction of namespaces data within the p
ortal session (which is an actual HttpSession).  I'm trying to figure out if
 those abstract portlet sessions are showing up in the Resource Analyzer, or
 if I'm seeing something el
se.

[ Post a follow-up to this message ]