Hi,
We have recently patched our SAP BI 4.0 platform from SP6 to SP8. Since then we have noticed that old sessions are not being released and they continued to appear in the sessions section (we noticed it because this was causing that number of connections exceeded our concurrent limit license which makes connection to be refused). Sessions remains for days/weeks and can only be removed by restarting SIA or killing manually using SDK (see note 18354664).
In our installation we have applied all steps commonly described in TN to be applied to avoid this kind of issue (we were applying there since initial 4.0 SP4 deployment)
- 1668750 - Sessions not being released in SAP Business Intelligence Platform 4.0
- 1837122 - How to increase session timeout value for BI Launchpad and CMC in BI 4.0
but for some reason, after installing SP8 sessions remains in the CMC even applying these steps.
After a bit of search I have noticed that several people was claiming to suffer similar situations using SAP BI 4.0 with previous SP (see thread Old/Dead Sessions does not fall down on Business Objcets XI 4) but as far as I know this was not our case.
We have also tried to implement the session cleanup mentioned in several threads (as the previuos one) detailed at following TN
1204040 - How to kill extra sessions without restarting the server
but despite that some people claim to have used it on BI 4.0 error retrieved when starting tomacat after adding changes in web.xml file (see below) makes me thing that this class does not longer exists in SAP BI 4.0
18-Feb-2014 10:52:16 org.apache.catalina.core.StandardContext listenerStart
SEVERE: Error configuring application listener of class com.businessobjects.sdk.ceutils.SessionCleanupListener
java.lang.ClassNotFoundException: com.businessobjects.sdk.ceutils.SessionCleanupListener
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4149)
I'm going to open a technical support case but I haven't too much hope on having a quick fix on that. So first of all I would confirm with someone else that I am not forgetting something trivial that was causing this problem to appear unexpectedly.
Thanks in advance,