TOKEN_MON hung due to BusinessObjects outage when calling 'stopsession'
Bryan Baca
started a topic
about 3 years ago
BusinessObjects becomes unresponsive after InfoBurst makes a 'stopsession' request. This scenario can cause the InfoBurst system thread responsible for monitoring active user sessions (TOKEN_MON) to hang and prevent further logins.
Bryan Baca
BusinessObjects becomes unresponsive after InfoBurst makes a 'stopsession' request. This scenario can cause the InfoBurst system thread responsible for monitoring active user sessions (TOKEN_MON) to hang and prevent further logins.
This issue is under investigation.
IBE-5821