User connection to srmmdm catalogue fails each Monday morning

[Former Member]

Hi folks

I recently installed SRM with srmmdm catalogue. SRM 7.02 is on NW 731, accessed by nwbc; a standalone Java WAS (NW7.3) hosts the srmmdm catalogue UI; the MDM 7.1 sp10 catalogue repository is set up as a Master with two slaves.  I have a fair bit of Basis behind me but no previous experience of MDM or the srmmdm catalogue app. Every Sunday, I see the following message in the MDM console logs:

- Sent MDSAdmin notification "SessionExpired" to session subscribers.

After this, the next user who connects to each slave repository generates the following error in the Java server0 application log for the srmmdm catalogue WAS

- The session is not valid; it may have expired. Create a new session and try the operation again. (0xffabd005)#

This is what the user actually sees:

Subsequent connections are typically OK,

From my reading, I thought the catalogue UI created a new login for each user connection, using the user defined in the call structure. Can anyone shed any light on this ?

[former_member216093 · Accepted solution]

Hi,

Can you please check if there is some offline backup done at scheduled time for these systems which either crosses the time when people start using the catalogue or it expires user session and need some services to restart?

I would surely review system backup timings and services.

Regards,

Ravi Pachauri

[Former Member]

We made no other changes the change to session timeout minutes was enough to solve the problem.

Kind regards

Mike Fletcher

[Former Member]

Thanks for your quick reply.

Regards

Ganesh Kotti

[Former Member]

Update to original post.

We actually set the timeout value to 0 (i.e. never time out)

Session timeout Minutes = 0

I did not want to make this a public recommendation since my understanding of this is limited, and I am struggling to understand the pupose of this timeout. If it is set to anything other than zero, it just seems to be a guaranteed way to periodically break your system.
(maybe someone else will explain it)

Since this is purely a server side process to process connection I can't see any problem with setting this parameter to zero. Making this change resolved the problem for us, and has never caused us any problems at all.

[Former Member]

Hello Ward,

Thanks for your reply.

Did you change any other parameters like "Inactive Client Timeout Minutes" or you just changed Session Timeout in Minutes. Please let us know.

Your answer will be very helpful to solve our issue.

Regards

Ganesh Kotti

[Former Member]

Thanks for responding. I have checked the backup schedule and only online backups are performed over the weekend.

I have found an inactivity timeout parameter (Session Timeout Minutes) in MDS.ini which has a default of 24 hours. This fits with the problem symptoms. I will test it and update this post.

[Former Member]

Hi Ward,

Please let me know the Session Timeout Minutes you put it in the MDS.ini file. We also facing the similar issue. 

Inactive Client Timeout Minutes=15

Session Timeout Minutes=480 .

Please let us know whether to increase or Decrease.

Thanks

Ganesh Kotti