Infoview Logoff button is not logging off the session?

server administration XI Server Discussion
1

Hi,

We have XI r2 using Tomcat. When we open the CMC and view the CMS server properties we can see when a new user has logged on in the CMS properties tab. However when a user logs off by clicking on the Logoff button in Infoview, the CMS stats show that their session is still logged on. I have also noted that if you simply close the browser, the javascript popup appears and this method DOES log you off. Please can a few of you try this on your copies of XI r2 and let me know if you have the same issue? I raised a case with BO Tech support but they say they cannot replicate the problem on their servers - so we are stuck. This problem only appears to happen on Tomcat. (IIS logoff button works fine)

This is a potential issue for us as will soon have thousands of users, and if their sessions are not being logged off properly we will rapidly run out of licences (Named user licence mode) - and it may prevent new uses from logging in.

Thanks

Rod

rodallen :uk: (BOB member since 2006-02-10)

2

That’s true! Just log in cmc and see a user has 5 sessions and another 2 (and they’re not log in at the moment).
But when i log with one of these user account, the number of session increase, and when i logoff, it decrease normally. And it decreases also when i shut done the broswer and logoff through the pop-up.
I don’t know how to reproduce the problem.

jerryf :fr: (BOB member since 2006-02-13)

3

Thanks for trying on your system. I have found something interesting through - I think its something to do with Performance Management. I uninstalled Performance Management and the CMS stats started updating correctly. So I repeat my original request with an addition - does anyone have XI r2 and Performance Management installed? If so can you please try this :-

  1. Log into the CMC and click on Servers and then your CMS server
  2. Make a note of the total number of logged in sessions
  3. Open a new browser and log in through InfoView
  4. refresh the number of sessions in the CMS properties tab
  5. Click log off on your Infoview browser
  6. refresh your CMS properties tab

On my system - with PM installed that number does NOT go down immediately, although the sessions do disappear after a while… I think…
:shock:

Regards

Rod

rodallen :uk: (BOB member since 2006-02-10)

4

I still have a user with 5 sessions and another with 2. Maybe this happen when they don’t logoff correcty, when system doesn’t responding and they close webi with a awful method. I’ll see what happen when i restart the CMS.
I don’t have PM installed.

jerryf :fr: (BOB member since 2006-02-13)

5

i’ve the same case and i will send to bo support

my operating system is sun solaris 9 with tomcat

i stop xi then tomcat server
then i wait 3 minutes
there still active process in unix environment

the better way??? kill -9 !!!
it’s a joke

if anyone have idea for this problem ??

tbcnfpt :fr: (BOB member since 2004-12-15)

6

I have spoken to BO Tech support and they have logged a bug on this issue - please note that this only affects users who also have Performance Management installed.

thanks

Rod

rodallen :uk: (BOB member since 2006-02-10)

7

Hi rodallen,

I do experienced the same problem and i had a ticket with BO working but nothing happened much. We did reinstall the software and for some reason the user logoff used to happen immediately. Atleast after some minutes. I didnt run into issue of no of user license becuase we have unlimited concurrent license. If this is bug that will be addressed then that is well and good so that i can have that updated in our environment.

Thanks

Dinesh

dinesh2005 :india: (BOB member since 2005-09-12)

8

Try reading the “readme” for the recent SP2 BO released. Becareful it’s 176 pages :). It seems to fix the session count problems for me. Unfortunately it broke URL reporting with .NET. The SP2 release also throws errors when installing. I’ve tried it on a few systems and all have behaved the same. BO support hasn’t been helpful at all with this. I’m hoping URL reporting will work using the Java side of things.

colganc (BOB member since 2006-05-10)

9

Hi,

I cant find any reference to an SP2 for XI r2. I thought the official release was still the Bundled SP1. Are you sure you mean XI release 2 SP2? If so - please can you supply the link so we can check it out

:?:

Thanks

Rod

rodallen :uk: (BOB member since 2006-02-10)

10

Oops. I glazed over the R2 mentions :?

colganc (BOB member since 2006-05-10)

11

One other thing I forgot to mention - if you close your browser - the client-side javascript pop-up does actually log you off - and if you check in the CMC the session count does reflect it.

So it would seem that this bug crept in with the addition of the PM desktop.war. Can any java developers out there figure out which line of code is being correctly executed by that close window function - but which is not being called correctly by the logoff button itself?

Or is this code compiled and therefore inaccessable to us? I noticed that without PM installed there is no …\scripts\doLogout.jsp so I am still stuck trying to figure out exactly where the logoff code is?? :shock:

Thanks

Rod

rodallen :uk: (BOB member since 2006-02-10)

12

We are using XIR2, Tomcat, with PM installed and we are experiencing this issue.

We looked in the file headerPlus.jsp which is the header page of Infoview with the logout button. The following code is executed when you click logout:

function onBtnLogoffClick()
{
	<c_rt:choose>
	<c_rt:when test="<%= CEClientConstants.isAFInstalled(application, CE_Session.getSession()) %>">
	    parent.document.location.href = "../../scripts/doLogout.jsp";
	</c_rt:when>
	<c_rt:otherwise>
        parent.document.location.href = "../logon/logoff.do";
	</c_rt:otherwise>
	</c_rt:choose>
}

AF stands for Application Foundation which is the old name for Performance Manager. Basically this code means that if Performance Manager is installed (isAFInstalled) redirect the user to doLogout.jsp, otherwise redirect to logoff.do. As a test we changed this code to redirect the user to logoff.do every time and our sessions in the CMS were being closed correctly. We were not sure, but from the looks of it logoff.do calls the page clientSessionEnd.jsp. This page has mostly the same code as doLogout.jsp with the exception of the following code:

// logoff the enterprise session
CrystalIdentity ident = (CrystalIdentity)request.getSession().getAttribute(CEConstants.SESSION_EN_SESSION);
if(ident != null) {
	try {
		ident.releaseLogonTokens();
	} catch (Exception e) {}
    try {
		ident.getSession().logoff();
	} catch (Exception e) {}
}

As the comment suggests, this code logs the user off the enterprise session. As far as we can tell Business Objects must have forgotten to put this code into doLogout.jsp.

So we added:

com.crystaldecisions.ePortfolio.framework.common.CrystalIdentity,
com.crystaldecisions.webapp.CEConstants,

to the page import statement at the top of doLogout.jsp. We added the enterprise session logoff code (as above) just after the code that closes the report engine (it appears in this location in clientSessionEnd.jsp) and all works well.

camurphy (BOB member since 2006-05-18)

13

I just spotted an interesting commented block of code in :-

…\Tomcat\webapps\businessobjects\enterprise115\desktoplaunch\WEB-INF\web.xml

It looks like this :-

<!-- In Tomcat 5.0.27, if you are experiencing problem that the license count on your CMS doesn't drop even
     after the application server has been idled for a long time and all the http sessions should have
     expired, comment in the following lines.
-->


I have uncommented that listener block - and now sessions are being logged off properly from the logoff button, without having to hack the doLogout.jsp. I am wondering if this has always been there and why it isn’t documented more clearly in the Knowledgebase/install guides, as it clearly affects all BOE + PM users who install the default Tomcat product?

Anyway - feel free to try this if you have PM.

Regards

Rod

rodallen :uk: (BOB member since 2006-02-10)

14

Rod, thanks for this :wink:
Nice to learn.

Sheshachala5 :india: (BOB member since 2004-01-09)

15

We also have this issue in CEXI R1. Thanks for the upstairs people. At least, we got the right direction. :arrow_forward:

However, I still have a problem. :hb:

I checked the file ‘headerPlus.jsp’ that has two ways to process logout request: doLogout.jsp and logoff.do. Neither of them is in the folder of ‘HOME/webapps/businessobjects/enterprise11/desktoplaunch/InfoView/logon’. There is a related file named ‘smlogoff.jsp’.

So, in order to terminate sessions correctly,

  1. Should we create file ‘logoff.do’ with closing session process?
  2. Where can I find the appropriate template for this file?
  3. Can we redirect users to this file every time?
  4. Can we add codes to terminate sessions when users directly close the window instead of clicking the logoff button? How do we do it?

Thanks. :slight_smile:

becky :canada: (BOB member since 2006-10-12)

16

this is very good to know…thanks all…hopefully i won’t run into this.

youngi (BOB member since 2006-10-09)

17

Hi,

I only have a copy of BOE XI Release 2 so I am not sure which files are common with Release 1. It might be worth looking under …\Infoview\main to see if you have a headerPlus.jsp to see if there is a logoff function in there which redirects to logoff.do. If you can find the bit that redirects to logoff.do, you can change that to redirect to your own custom logoff page - like the doLogout.jsp. What I have discovered since my last post is that the SessionCleanupListener does not work when you have a Webi session (i.e. if you do anything after logging in!), so you still need to hack the extra session logoff code into the doLogout.jsp page. I add this just after closing the report engine :-

    // logoff the enterprise session 
    CrystalIdentity ident = (CrystalIdentity)request.getSession().getAttribute(CEConstants.SESSION_EN_SESSION); 
    if(ident != null) { 
        ident.releaseLogonTokens(); 
        ident.getSession().logoff(); 
    }

Regards

Rod

rodallen :uk: (BOB member since 2006-02-10)

18

Since I have to uninstall r1 to install r2, I cannot confirm whether the code is there in r1 or not. But r1 has the problem of closing user sessions and it is fixed in r2. Therefore, that piece of code might be new in r2.

Just curious. Why are you still in r1? Are you not qualified for the free upgrade to r2? Release 1 is so buggy that you should get out of it as soon as you can (it reminds me of the 6.1.a … :blue: )

substring :us: (BOB member since 2004-01-16)

19

Thanks for your reply.

The recent update is we got the responsce from BO online support. They suggested us to apply a patch: beXIwin_chf.zip. The related articles in their Knowledge Base are #c2019040 and #c2018124.

We installed the patch and redeployed the war files as those two articles said. However, the problem is still there. :reallymad:

I think the primary issue is we do NOT have either of “doLogout.jsp” and “logoff.do” in the entire directory of “Program file/Business Objects”. The “headerPlus.jsp” redirects logoff to the two files, but none of them exists. :blue:

Do you think we should create a file with the name of “doLogout.jsp” or “logoff.do”? I’m not a Java developer. :nonod:

becky :canada: (BOB member since 2006-10-12)

20

We are using Crystal Report Server XI R1.

I don’t know what’s the difference between CR and BO XI. It seems all the same to me.

However, the sales guys in Business Objects told us the Crystal Report XI R2 is still in the testing and it has not been published yet! I just totally confused… :crazy_face:

becky :canada: (BOB member since 2006-10-12)