D
dbeavon
Guest
Hi Irfan, thanks for your input. I think you may have it backwards. The tomcat instance knows which webapp the session is connected to, and is able to associate the HTTP session with a related *webapp*. This information is available in the tomcat "manager" webapp. But when the OEM console tries to enumerate the sessions based on the ABL application, then the underlying tomcat instance will not directly help to produce that list, hence the misinformation that is shown in the OEM console. If you view the sessions, in the OEM console (within an ABL application) they are not limited to any single ABL application nor any single webapp. Please see that KB for more explanation. In our configuration we have only one webapp for each ABL application. But the outer PASOE instance has multiple of these webapp/ABL-app pairs. The sessions that are listed in the OEM console are *never* specific to a single webapp, nor a single ABL application. The sessions are a combination of *all* the sessions across the entire tomcat instance. You might want to set up this configuration to see for yourself. I'd also suggest connecting from a large number of long-lived state-free client sessions, so that the problem is accentuated. In order to manage our sessions, I'll probably continue to rely on the "manager" webapp in tomcat. Thanks, David
Continue reading...
Continue reading...