[jboss-jira] [JBoss JIRA] (AS7-3474) JSR88 undeployment does not work

[Wolfgang Knauf (JIRA)]

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

Wolfgang Knauf reopened AS7-3474:
---------------------------------



I still see the problem in today's snapshot (from http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-7.0.x/)

The testcase deploy/undeploy code works for me, too: in my sample, when I add in the attached "JSR88Deployer.main" a call to "JSR88Undeployer.jsr88Undeploy(modules, dm);" directly after deployment, then undeployment works fine.

But if deploy and undeploy are two different java processes, it does not seem to work.


The client side log tells me on undeploy that everything is fine:
     [java] Progress.getState == COMPLETED: JBAS016155: Operation Stop completed
     [java] Progress.getState == COMPLETED: JBAS016155: Operation Undeploy completed

But there is no server output besides "JBREM000200: Remote connection failed: java.io.IOException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen".


I hope it is no silly error on my side ;-)
                
> JSR88 undeployment does not work
> --------------------------------
>
>                 Key: AS7-3474
>                 URL: https://issues.jboss.org/browse/AS7-3474
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JSR88
>    Affects Versions: 7.1.0.CR1b
>            Reporter: Wolfgang Knauf
>            Assignee: Thomas Diesler
>         Attachments: JSR88Test.zip
>
>
> This is a followup of some mailing list discussion, tested against 7.1.0CR1 and 7.1.0 snapshot from 2012-01-13.
>  
> It seems that JSR88 undeployment is not working under certain circumstances. Attached is a full sample.
> ======================
> It works, when doing this:
> After deploy, I get a TargetModuleID from the ProgressObject.
> TargetModuleID[] modules = myProgressObject.getResultTargetModuleIDs();
> If i perform an undeploy directly after deploying *using this TargetModuleID array*, it works.
> This is an array with one item. The output of "toString" for this items is this:
> [target=http://org.jboss.as.ee.deployment/jsr88?targetType=as7&serverHost=localhost&serverPort=9999,parent=null,type=ear,id=file:/C:/DOCUME~1/Knuffi/LOCALS~1/Temp/Stateless.ear]
> ======================
> But in my undeploy job, I call "DeploymentManager.getAvailableModules" and search a file matching my name.
> So I find this module ("toString" output):
> [target=http://org.jboss.as.ee.deployment/jsr88?targetType=as7&serverHost=localhost&serverPort=9999,parent=null,type=ear,id=file:/C:/DOCUME~1/Knuffi/LOCALS~1/Temp/Stateless.ear]
> It seems to be identical to the above output, but undeploying a TargetModule array with this one item does not work: there is no status output on the server, though the client side seems to complete successfully.
> ======================
> Attached ("JSR88Test.zip") is my deployer code as a self running sample, including the EAR file for deployment.
> To run it:
> 1) Import project in Eclipse.
> 2) Update build paths.
> 3) Compile (ignore my two warnings - they are just markers for myself)
> 4) edit "build.xml" and modify the property "serverRootDirectory" to point to your JBoss installation
> 5) open "build.xml" using Eclipse and run the target "deploy.j2ee.ear". The archive "Stateless.ear" (included in project root directory) should be deployed.
> 6) run the target "undeploy.j2ee.ear" => EAR should be undeployed, but this does not work.
> If you add an undeploy call directly after deployment in step 6 using the deployed TargetModuleID, it works. But it does not work when undeploying later (which should probably be the standard use case ;-))

--
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