Tight Loop In Hula_dance() When Authentication Server Exits (Doc ID 2340628.1)

Last updated on JULY 18, 2019

Applies to:

Symptoms

Process threads spinning in tight loops
Shutting down authentication server whilst it is being heavily accessed by messaging sever processes.
Threads being tied up, consuming cpu, filling log partitions with errors

Authentication server has been implemented based on the example framework provided with the messaging product (found in /examples/tpauthsdk).
It has been noticed that when the authentication server shuts down, it sometimes leaves the processes that are communicating with it - such as AService, imapd - in a state that results in a tight loop printing log messages after receiving a connection error. This state never clears and can easily fill up log partitions if it goes unnoticed. The spinning processes do not even necessarily shut down with a regular restart of the messaging server and have to be killed with a SIGKILL.

Changes

 Authentication server has been implemented based on the example framework provided with the messaging product (found in /examples/tpauthsdk).

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.