Lets assume that you have a ColdFusion server that uses a number of J2EE sessions. ColdFusion has a specific way of using the J2EE sessions.
When J2EE sessions are enabled in ColdFusion, the sessions are stored within the tomcat /root context. There is also then a ColdFusion session created that wraps this J2EE session.
By default, ColdFusion sessions will expire based on a worker thread, but the J2EE sessions will expire based on time since last used. So the ColdFusion session can be destroyed by the worker thread, but the J2EE session will remain. So if a user comes back a new ColdFusion session is created, but the same J2EE session will be used.
An example of the Session graph that is created by the ColdFusion server and the way uses the J2EE Sessions might be represented by the screenshot below.
From the screenshot we can observe that there is a big number of Created, Active, Destroyed Sessions. Moreover, on the Tracked Applications space we can see that the /root context contains the most of the Active Sessions.
From all the above, we can assume that is normal to have a large number of Active Sessions under the /root context because that happens from the way ColdFusion server uses the J2EE sessions.
|Last Updated:||12/May/16 10:30 AM|
Comments are closed.