Previous Topic: Cookies with Potentially Harmful Characters (43201)

Next Topic: Agent Logged Local Time Incorrectly (44204)

LLAWP Process Did Not Restart (44020)

Symptom:

When the Web Agent entered a state where the LLAWP process shut down, the LLAWP could not be restarted. If the Web server worker process existed, but no LLAWP process was running to service requests, Agent management events and log messages were blocked. The Web server worker process failed to roll keys and entered a deadlock.

Note: This issue occurred by a LLAWP failure in the IIS 6.0 and Apache 2.0 Agents.

Solution:

The LLAWP process is now restarting as expected.