Solutions
ForgeRock Identity Platform
Does not apply to Identity Cloud

ERROR: CTS Async: Task Processor Error: interrupt detected when shutting down AM (All versions)

Last updated Apr 13, 2021

The purpose of this article is to provide assistance if you encounter an "ERROR: CTS Async: Task Processor Error: interrupt detected" when shutting down the AM server.


2 readers recommend this article

Symptoms

The following error is shown in the Session debug log when shutting down AM:

amCoreTokenService:11/09/2016 03:19:01:018 PM UTC: Thread[CTSWorkerPool-4,5,main]: TransactionId[393810d1-634a-45e0-b105-a3e040775526-0] ERROR: CTS Async: Task Processor Error: interrupt detected java.lang.InterruptedException at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2014) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2048) at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) at org.forgerock.openam.sm.datalayer.impl.SeriesTaskExecutorThread.run(SeriesTaskExecutorThread.java:91) at org.forgerock.openam.audit.context.AuditRequestContextPropagatingRunnable.run(AuditRequestContextPropagatingRunnable.java:42)

Recent Changes

Restarted or shut down the AM server.

Causes

This error occurs when AM is shutdown while debug mode is enabled. It implies that the operation was canceled or the AM server was shutting down whilst processing requests. It can occur even if you are not using CTS.

Solution

This is a harmless error that can be ignored as it only occurs during shut down.

See Also

N/A

Related Training

N/A

Related Issue Tracker IDs

OPENAM-8219 (After restarting an OpenAM it is necessary to login again with an user when is used external CTS and Site contains only one server)


Copyright and Trademarks Copyright © 2021 ForgeRock, all rights reserved.