Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MSC-204] Fixing container shutdown freeze if shutdown is intiated during container boot process #64

Merged
merged 3 commits into from
Feb 22, 2018

Conversation

ropalka
Copy link
Contributor

@ropalka ropalka commented Feb 22, 2018

No description provided.

…er have been shutdown.

It is necessary to detect container shutdown during the service
installation phase because container can be shutdown even at its boot phase.

Before this fix it was possible to shutdown the container executor
and still have pending tasks in its queue.

As consequence of this premature executor shutdown it sometimes
happened that last executed tasks might try to submit new tasks
to executor but executor started rejecting them.

When RejectedExecutionException was detected current thread tried
to executed scheduled tasks on its own. Because tasks may result
in creation of new tasks it sometimes happened that Lockable read lock
have been acquired in one task at the beginning of the rejected tasks
execution chain and later in another task on an attempt to acquire
write lock thread started to wait forever on read lock release.
But because current thread acquired that read lock such wait
was on forever. This resulted in container freeze.
@ropalka ropalka merged commit ad06813 into jboss-msc:1.2 Feb 22, 2018
@ropalka ropalka deleted the MSC-204 branch February 22, 2018 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant