Contributor.. boochi Contributor..
Contributor..
798 views

Getting Session Expired after logging to HP OO Central

Hi Folks,

When ever i am login using internal user to Central getting "your session got expired.please login again" message.

and sometimes it is showing blank page after giving username and password.

here are my environment details:

HP OO Version: 10.50

Browser: tried all (chrome,IE and Mozilla)

user type: Internal (No LDAP integration)

Lodbalancer: yes

Installed on : Windows 2012 servers

Could you please help me to avoid this error?

thanks in advance.

Regards,

boochi.

Labels (2)
0 Likes
3 Replies
GalM Absent Member.
Absent Member.

Re: Getting Session Expired after logging to HP OO Central

Hello boochi, 

How long does it take to this message to appear after login? 

The default value of the Central server timeout can be changed in by editing the Tomcat's web.xml file.

From the documentation (Administration Guide, page 8): 

Changing the Timeout Limit for the OO Web Interface You can change the default session timeout (30 minutes) of the Central server by configuring the tomcat web.xml file.

1. Open the /central/tomcat/conf/web.xml file with any XML editor.

2. Search for the following:

<!-- ==================== Default Session Configuration ================= -->
<!-- You can set the default session timeout (in minutes) for all newly -->
<!-- created sessions by modifying the value below. -->

<session-config>
<session-timeout>30</session-timeout>
</session-config>

Hope that helps

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Getting Session Expired after logging to HP OO Central

Hi,

Regarding the blank page  problem after loging in that is somewhat to be expected (depending on the time the page stays blank). After loging in it can take up to 2-3 minutes (perhaps slightly more based on the network speed between the browser's host and the db host) where OO fetches all the data required to be displayed. This is a one time (post login) gap and after this it should not occur until the next login.

Now moving on to the session has expired part.  If this hapens imediately after login  only when using the load balancer url then the problem is that after modifying the server.xml to add the jvmRoute parameter the central node wasn't restarted. A restart on all nodes should clear this problem. 

 

Now if the blank screen  takes longer (basically OO doesn't ever load) maybe there is a problem with the jvmRoute configuration. Check that all nodes point to the same path given to the loadbalancer (ex: central node 1 has jvmRoute=node1, then in the loadbalancer configuration the host of that central should have the path set to node1) then restart all central nodes.

Hope this helps,

Vlad

 

0 Likes
Contributor.. boochi Contributor..
Contributor..

Re: Getting Session Expired after logging to HP OO Central

Hi GalM,

thanks for your response.

Here is my web.ml configurations for session timeout in all central nodes.

<!-- ==================== Default Session Configuration ================= -->
<!-- You can set the default session timeout (in minutes) for all newly -->
<!-- created sessions by modifying the value below. -->

<session-config>
<session-timeout>120</session-timeout>
</session-config>

 Regards,

Boochi.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.