lock on login
-
- Posts: 58
- Joined: Mon Sep 27, 2010 2:46 pm
- OLAP Product: Cognos TM1
- Version: 10_1 10_2
- Excel Version: 2010
- Location: UK, CH, BE
lock on login
Hi,
I checked a bit the forum and I found similar issues but not for 10.2.2.3 and I can't apply the same solutions.
The issue is this. I have a client that experiences locks in the system that are not permitting the users to log in.
This happens periodically.
At the beginning, it was happening during a chore so I thought th chore was containing something like securities updates or similia.
I switched off all the chores and weirdly the lock happened again, this time (and a couple of times after), it locked on a user log in (so the log in of a user was not allowing the other users to log in, not always the same user locked the others).
I noticed also that the system is creating zombie threads, meaning that if I open op console or tm1top (shhh don't tell IBM it still works) I can see idling thread from some users that are idling since days and I cannot kill. I assumed these zombies are generated when a user reaches the timeout but I have no proof for that.
Any ideas? could it be that the old issue of 9.5 of the unregistered changes to views after a timeout is still there in 10.2.2.3?
I checked a bit the forum and I found similar issues but not for 10.2.2.3 and I can't apply the same solutions.
The issue is this. I have a client that experiences locks in the system that are not permitting the users to log in.
This happens periodically.
At the beginning, it was happening during a chore so I thought th chore was containing something like securities updates or similia.
I switched off all the chores and weirdly the lock happened again, this time (and a couple of times after), it locked on a user log in (so the log in of a user was not allowing the other users to log in, not always the same user locked the others).
I noticed also that the system is creating zombie threads, meaning that if I open op console or tm1top (shhh don't tell IBM it still works) I can see idling thread from some users that are idling since days and I cannot kill. I assumed these zombies are generated when a user reaches the timeout but I have no proof for that.
Any ideas? could it be that the old issue of 9.5 of the unregistered changes to views after a timeout is still there in 10.2.2.3?
- qml
- MVP
- Posts: 1094
- Joined: Mon Feb 01, 2010 1:01 pm
- OLAP Product: TM1 / Planning Analytics
- Version: 2.0.9 and all previous
- Excel Version: 2007 - 2016
- Location: London, UK, Europe
Re: lock on login
Wat's your IntegratedSecurityMode?
Have you tried switching on lock exception logging in tm1s-log.properties?
Have you tried the following config parameter? It is meant to prevent locks on logoff, but maybe it could help in your case.
TM1top still works because the API interface for it is also used by the OpsConsole. Nota bene, TM1top is officially back as of 10.2.2 FP4.
Have you tried switching on lock exception logging in tm1s-log.properties?
Code: Select all
log4j.logger.TM1.Lock.Exception=DEBUG
Code: Select all
KeepPrivateSubsetsLoaded=T
Kamil Arendt
-
- Posts: 58
- Joined: Mon Sep 27, 2010 2:46 pm
- OLAP Product: Cognos TM1
- Version: 10_1 10_2
- Excel Version: 2010
- Location: UK, CH, BE
Re: lock on login
qml wrote:Wat's your IntegratedSecurityMode?
integratedsecuritymode 5 integrated login
sadly I cannot stop the system at the moment but I can ask and put it up.qml wrote: Have you tried switching on lock exception logging in tm1s-log.properties?Have you tried the following config parameter? It is meant to prevent locks on logoff, but maybe it could help in your case.Code: Select all
log4j.logger.TM1.Lock.Exception=DEBUG
Code: Select all
KeepPrivateSubsetsLoaded=T
Is the Keepprivatesubsetloaded still a valid parameter in the CFG file for 10.2.2.3?
yep, read that just after I posted this post. it is a really good thing.qml wrote:TM1top still works because the API interface for it is also used by the OpsConsole. Nota bene, TM1top is officially back as of 10.2.2 FP4.
-
- MVP
- Posts: 264
- Joined: Mon Nov 03, 2014 8:23 pm
- OLAP Product: TM1
- Version: 9.5.2 10.1 10.2 PA2
- Excel Version: 2016
Re: lock on login
stingo wrote: sadly I cannot stop the system at the moment but I can ask and put it up.
Is the Keepprivatesubsetloaded still a valid parameter in the CFG file for 10.2.2.3?
The logger update does not require a reboot, but KeepPrivateSubsetsLoaded will. Yes, the parameter is still valid.
- qml
- MVP
- Posts: 1094
- Joined: Mon Feb 01, 2010 1:01 pm
- OLAP Product: TM1 / Planning Analytics
- Version: 2.0.9 and all previous
- Excel Version: 2007 - 2016
- Location: London, UK, Europe
Re: lock on login
That is a very important piece of information. CAM logons seem to cause more locking than native logons, I imagine mostly due to the fact that users' security needs to be updated. The logger should tell you what objects you're getting locks on and we can take it from there.stingo wrote:integratedsecuritymode 5 integrated login
As to your 'zombie threads' it might be due to Cognos not closing the sessions. Check your Ping timeout in seconds and Inactivity timeout in seconds parameter values in Cognos Configuration.
Kamil Arendt
-
- Posts: 58
- Joined: Mon Sep 27, 2010 2:46 pm
- OLAP Product: Cognos TM1
- Version: 10_1 10_2
- Excel Version: 2010
- Location: UK, CH, BE
Re: lock on login
qml wrote:That is a very important piece of information. CAM logons seem to cause more locking than native logons, I imagine mostly due to the fact that users' security needs to be updated. The logger should tell you what objects you're getting locks on and we can take it from there.stingo wrote:integratedsecuritymode 5 integrated login
As to your 'zombie threads' it might be due to Cognos not closing the sessions. Check your Ping timeout in seconds and Inactivity timeout in seconds parameter values in Cognos Configuration.
just a last question before putting the brain at work, will the debug on the log properties degrade the performance a lot?
- qml
- MVP
- Posts: 1094
- Joined: Mon Feb 01, 2010 1:01 pm
- OLAP Product: TM1 / Planning Analytics
- Version: 2.0.9 and all previous
- Excel Version: 2007 - 2016
- Location: London, UK, Europe
Re: lock on login
Not the one I suggested. It should produce very little additional output: basically one line for every encountered lock conflict. If you switch on a bunch of verbose loggers like the API one, you can expect some performance degradation, but log4j.logger.TM1.Lock.Exception is safe in that respect. Personally, I would also set each logger to print out to its own separate file to avoid flooding tm1server.log. Let me know if you need instructions how to do it.stingo wrote:just a last question before putting the brain at work, will the debug on the log properties degrade the performance a lot?
Kamil Arendt
-
- Posts: 58
- Joined: Mon Sep 27, 2010 2:46 pm
- OLAP Product: Cognos TM1
- Version: 10_1 10_2
- Excel Version: 2010
- Location: UK, CH, BE
Re: lock on login
sorry for my ignorance but the server is on many machines... where should it be? in local TM1 or in BI?qml wrote:Not the one I suggested. It should produce very little additional output: basically one line for every encountered lock conflict. If you switch on a bunch of verbose loggers like the API one, you can expect some performance degradation, but log4j.logger.TM1.Lock.Exception is safe in that respect. Personally, I would also set each logger to print out to its own separate file to avoid flooding tm1server.log. Let me know if you need instructions how to do it.stingo wrote:just a last question before putting the brain at work, will the debug on the log properties degrade the performance a lot?
EDIT: I am a loser... I found the way, google is my friend!
EDIT2: still I would like that suggestion in how to declare another log file as per quote as I cannot find it in the documentation.
-
- Posts: 15
- Joined: Wed May 25, 2011 12:39 pm
- OLAP Product: TM1
- Version: 1022-FP*
- Excel Version: 2010-2016
Re: lock on login
From 10.2.2.4 Fix list:qml wrote: log4j.logger.TM1.Lock.Exception is safe in that respect.
PI42411: TM1 SERVER CRASH WITH TM1.LOCK.EXCEPTION ON
-
- Posts: 58
- Joined: Mon Sep 27, 2010 2:46 pm
- OLAP Product: Cognos TM1
- Version: 10_1 10_2
- Excel Version: 2010
- Location: UK, CH, BE
Re: lock on login
ok... maybe I should wait for the patch to be installed then...silw wrote:From 10.2.2.4 Fix list:qml wrote: log4j.logger.TM1.Lock.Exception is safe in that respect.
PI42411: TM1 SERVER CRASH WITH TM1.LOCK.EXCEPTION ON