[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: NPE in DeployersImpl

[adrian@jboss.org]

This is really this issue:
https://jira.jboss.org/jira/browse/JBAS-5326

A simple fix for the current case is to just check the DeploymentControllerContext
is not null, i.e. some other thread already won the race and undeployed it.

What is really required (as discussed with Ales in Slovenia)
is that there is a lock where we don't try to (un)deploy
when somebody else is already doing stuff
(with a timeout on the lock to trap broken/deadlocked deployment code).

This code already exists within the MC controller, but there's no timeout
which would mean shutdown would wait forever in the case that some
deployment/undeployment callback does not return.

Similar issues exist in JBoss-4.x so there's nothing new in this problem,
it just remains unresolved in JBoss5 at the moment (but at least in JBoss5
it is fixable since the deployers, jmx and pojo all share the same controller model).

It also needs testing/extending for this feature:
https://jira.jboss.org/jira/browse/JBMICROCONT-327
e.g. allowing groups of unrelated dependencies to run in parallel

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176765#4176765

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176765