jgersic64
Active Member
Recently, we have been experiencing intermittent problems with the
security server becoming non-responsive. When I go into SAW, I can see that
the average process time for a number of the security kernels are really
high (30 seconds), this causes the users to get a timeout and the 'failed to
locate security server' error. Since we are in the middle of quarter close,
I cannot bounce the services without major disruption, nor can I turn on the
logging due to the performance hit, so my tools are pretty limited at the
time. For the moment, what I have been doing is just issuing a kill command
to those process id's that become non- responsive, and then JDE starts
another after it has detected that it died (was killed). Once the new
process starts up, users are ok to log in again...
There hasn't been any changes to the server, so the only thing I can
really think of is that there are jobs that are running and a bending or
something, although I haven't seen any consistency things of the system when
gets into trouble. Has anyone else had a problem similar to ours?
John
NT, XP/SP14.2, SQL7/SP3, WTS/Metaframe 1.8
----------------------------------------------------------------
John Gersic
Financial Systems DBA
703.744-6057
1861 International Drive
McLean, Virginia 22102
MicroStrategy-Best in Business Intelligence
http:/www.microstrategy.com/ <http:/www.microstrategy.com/>
-----------------------------------------------------------------
security server becoming non-responsive. When I go into SAW, I can see that
the average process time for a number of the security kernels are really
high (30 seconds), this causes the users to get a timeout and the 'failed to
locate security server' error. Since we are in the middle of quarter close,
I cannot bounce the services without major disruption, nor can I turn on the
logging due to the performance hit, so my tools are pretty limited at the
time. For the moment, what I have been doing is just issuing a kill command
to those process id's that become non- responsive, and then JDE starts
another after it has detected that it died (was killed). Once the new
process starts up, users are ok to log in again...
There hasn't been any changes to the server, so the only thing I can
really think of is that there are jobs that are running and a bending or
something, although I haven't seen any consistency things of the system when
gets into trouble. Has anyone else had a problem similar to ours?
John
NT, XP/SP14.2, SQL7/SP3, WTS/Metaframe 1.8
----------------------------------------------------------------
John Gersic
Financial Systems DBA
703.744-6057
1861 International Drive
McLean, Virginia 22102
MicroStrategy-Best in Business Intelligence
http:/www.microstrategy.com/ <http:/www.microstrategy.com/>
-----------------------------------------------------------------
