EE Managed Executor Service does not shut down correctly upon 'stop' command with zero timeout

Solution Verified - Updated -

Issue

EAP's EE-Concurrency Managed Executor Service is expected to skip the tasks that are pending in its execution queue upon server shutdown as documented here
This is necessary to cope with scenario where a polling-type task is re-scheduling a new instance of itself just before exiting (so that there is always one task polling - pattern used e.g. by Spring message listeners

Triggering a shutdown of the EE managed executor service, with a timeout value of 0 (zero - or no timeout at all, which defaults to zero) does not work. The service continues to scheduling new tasks even though the log files
The following commands CLI commands do not work

/host=master/server-config=server-one:stop
/host=master/server-config=server-one:stop(timeout=0)

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.1.2, 7.1.1, 7.1.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content