We have upgraded not too long ago (yesterday :-P) from V3.0.5 to V3.0.8 of ICN.

Everything went well, well, except for the timeout. On V3.0.5 we have defined in WAS a session timeout of 720 minutes, and it was working pretty well. We did the same for the Filenet.

Now since we upgraded to ICN V3.0.8, we have a timeout of something like 5 minutes, and I have no clue where to look.

Does someone has an idea where I can look at in order to correct the timeout session of Content Navigator?

Thanks!

Regards,

Alessandro

Hi Alessandro,

I don't think upgrade ICN will change the session timeout value since we don't set this value in web.xml file. It always be set on WAS.

1. Have you checked ICN web.xml file and see if there is any session configs there?
2. Have you checked your WAS session timeout value? We always set the seesion timeout setting here: WAS console->Servers->Server Types->Websphere application servers->servername->Session management-Set timeout.
3. Are you using SSO environment? If that is the case, you will need to check the IDP server setting.

Thanks,

Jason​

Hi Jason,

Thank you for the answer. Then this is quite strange...

1. We never changed the web.xml, it is the original from Content Navigator installation. The only change between the previous version and the new one is the "firewall" part, that I needed to include. I've choose the "standard" configuration, and not the custom. To be honest I have no idea how to configure that (yet), so I decided for the "standard" config
2. Yes, I have checked and it is set to 720 minutes
3. We are not in a SSO environment, therefore we do not use any IDP servers.

Regards,

Alessandro

Hi Alessandro,

You can open an official support case to our support enginer. Attach the ICN server debug log and your deployed web.xml file in WAS.

Thanks,

Jason

Hi Jason,

that's what I did. Sometimes the support tells me to open a question in the forum :-) so this time, I did both at the same time :-D

Cheers,

Alessandro

Hi Alessandro,

I checked the timeout In icn 3.0.8 and it works perfectly fine based on websphere timeout setting, which in my case is 30 minutes.

Check if you are using any plugin which might be causing the timeout. You could create a new desktop and remove all plugins for that desktop and observe the timeout.

Or else, You might be using 2 applications simultaneously which might be using same sessionid. Try to change icn sessionid in this case.

Hi Amit,

Well, as I said just before the upgrade from V3.0.5 everything was working since a year (we did install this version with this exact setup 13 month ago).

And after the upgrade to V3.0.8, with the same timeout setting and the same plugins, we have a timeout problem. And I might even add, that in our test environment, with the same upgrade to V3.0.8, it works.

So I don't think the problem is related to plugin or the timeout settings, something else is off.

I am now with the IBM Support to investigate it, and at the end, I will share what we have found, in case it might help someone.

Well, here is what I have found with the support guy. (by the way, very helpful and nice :-) )

In WebSphere you have level of timeout, which will overwrite the previous level:

• Server Level
• Enterprise Application Level
• Web Application Level
• web.xml level
• programming code

The timeout I am changing was always the server level, and everyone told me to use that one (IBM and forums). I have the 720 minutes there.

But after discussing with the IBM Support guy, I looked at the Enterprise Application Level and Web Level, and both were set to 30 minutes.

I didn't have any timeout in the web.xml, and I strongly suspect that in ICN, the developers didn't do anything like that.

So I changed the "Enterprise Application Level" and the "Web Application Level" both to 720 minutes... and after a restart, I finally have my timeout of 720 minutes!!!!!

Now, why on earth the "Enterprise Application Level" and "Web Application Level" timeout was set to 30 minutes during the upgrade from V3.0.5 to V3.0.8.... that's another question.... I have no idea, and it's quite annoying.

Now everything is good :-D

(Here is the tech note about the level of overwriting of the timeout setting: https://www.ibm.com/support/pages/http-session-time-out-settings-and-overwrite-precedence-rules )

Cheers,

Alessandro