[jboss-jira] [JBoss JIRA] (AS7-4620) ServerSetupObserver should not assume a Deploy has happened before a UnDeploy is called

Aslak Knutsen (JIRA) jira-events at lists.jboss.org
Wed Apr 25 06:43:18 EDT 2012


     [ https://issues.jboss.org/browse/AS7-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aslak Knutsen updated AS7-4620:
-------------------------------

    Summary: ServerSetupObserver should not assume a Deploy has happened before a UnDeploy is called  (was: ServerSetupObserver should not assume a Deployment has happened before a Undeployment is called)

    
> ServerSetupObserver should not assume a Deploy has happened before a UnDeploy is called
> ---------------------------------------------------------------------------------------
>
>                 Key: AS7-4620
>                 URL: https://issues.jboss.org/browse/AS7-4620
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 7.1.1.Final
>            Reporter: Aslak Knutsen
>            Assignee: Stuart Douglas
>
> Both in a context of the Arquillian Maven extension and the Arquillian JRebel extension, UnDeploy operations can be called on a container without a Deploy operation call within the same JVM run.
> Initialization of the deployed Map happens when a Deploy occurred:
> https://github.com/jbossas/jboss-as/blob/master/arquillian/common/src/main/java/org/jboss/as/arquillian/container/ServerSetupObserver.java#L40
> Which trigger a NullPointerException if a Undeploy is called without a Deploy:
> https://github.com/jbossas/jboss-as/blob/master/arquillian/common/src/main/java/org/jboss/as/arquillian/container/ServerSetupObserver.java#L126
> {code}
> java.lang.NullPointerException
> 	at org.jboss.as.arquillian.container.ServerSetupObserver.handleAfterUndeploy(ServerSetupObserver.java:119)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:616)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> 	at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> 	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:226)
> 	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185)
> 	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
> 	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list