[jboss-jira] [JBoss JIRA] Reopened: (JBAS-8624) JBoss 5.1.0 sometimes can't undeploy war application
Jason Greene (JIRA)
jira-events at lists.jboss.org
Thu Apr 21 14:26:48 EDT 2011
[ https://issues.jboss.org/browse/JBAS-8624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Greene reopened JBAS-8624:
--------------------------------
Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all unscheduled AS6 issues that are a year or less old. This will make it easier community members to find and work on them.
Future releases beyond 6.1 can be done provided a community member steps up to coordinate them.
> JBoss 5.1.0 sometimes can't undeploy war application
> ----------------------------------------------------
>
> Key: JBAS-8624
> URL: https://issues.jboss.org/browse/JBAS-8624
> Project: Legacy JBoss Application Server 6
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-5.1.0.GA
> Environment: Windows 7 Operating System, Oracle Java 1.6.0_21
> Reporter: Dmitry Geurkov
> Priority: Minor
> Fix For: No Release
>
>
> Sometimes during development web applications stuck and can't be undeployed. manually removing war archive is not possible because system says that file is used by another program.
> But no other programs use archive except jboss process. Trying to remove stucked web application from Admin Console only stops the application but not removes it completely. The following exception is thrown in during the click on remove button in Admin Console
> 14:55:51,376 INFO [DeployHandler] Stop, [vfszip:/D:/jboss-5.1.0.GA/server/default/deploy/docflowweb.war/]
> 14:55:51,376 INFO [DeployHandler] End stop, [vfszip:/D:/jboss-5.1.0.GA/server/default/deploy/docflowweb.war/]
> 14:55:51,381 INFO [DeployHandler] Remove, [vfszip:/D:/jboss-5.1.0.GA/server/default/deploy/docflowweb.war/]
> 14:55:53,385 INFO [DeployHandler] Failed to complete command: [remove] for deployment: names=[vfszip:/D:/jboss-5.1.0.GA/server/default/deploy/docflowweb.war/], copyContent=true
> java.io.IOException: Failed to delete: DelegatingHandler at 15550946[path=docflowweb.war context=file:/D:/jboss-5.1.0.GA/server/default/deploy/ real=file:/D:/jboss-5.1.0.GA/server/default/deploy/docflowweb.war]
> at org.jboss.system.server.profileservice.repository.BasicDeploymentRepository.removeDeployment(BasicDeploymentRepository.java:268)
> at org.jboss.system.server.profileservice.repository.BasicDeploymentRepository.removeDeployment(BasicDeploymentRepository.java:229)
> at org.jboss.profileservice.management.upload.remoting.DeployHandler.removeDeployment(DeployHandler.java:176)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.remove(AbstractDeployHandler.java:333)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:185)
> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
> at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
> at org.jboss.remoting.Client.invoke(Client.java:1724)
> at org.jboss.remoting.Client.invoke(Client.java:629)
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.remove(StreamingDeploymentTarget.java:229)
> at org.jboss.profileservice.management.upload.DeploymentProgressImpl.remove(DeploymentProgressImpl.java:321)
> at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:94)
> at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:120)
> at org.rhq.plugins.jbossas5.StandaloneManagedDeploymentComponent.deleteResource(StandaloneManagedDeploymentComponent.java:326)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> 14:55:53,843 ERROR [StandaloneManagedDeploymentComponent] Failed to remove deployment 'vfszip:/D:/jboss-5.1.0.GA/server/default/deploy/docflowweb.war/'.
> java.lang.RuntimeException: java.io.IOException: Failed to delete: DelegatingHandler at 15550946[path=docflowweb.war context=file:/D:/jboss-5.1.0.GA/server/default/deploy/ real=file:/D:/jboss-5.1.0.GA/server/default/deploy/docflowweb.war]
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:313)
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.remove(StreamingDeploymentTarget.java:229)
> at org.jboss.profileservice.management.upload.DeploymentProgressImpl.remove(DeploymentProgressImpl.java:321)
> at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:94)
> at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:120)
> at org.rhq.plugins.jbossas5.StandaloneManagedDeploymentComponent.deleteResource(StandaloneManagedDeploymentComponent.java:326)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.io.IOException: Failed to delete: DelegatingHandler at 15550946[path=docflowweb.war context=file:/D:/jboss-5.1.0.GA/server/default/deploy/ real=file:/D:/jboss-5.1.0.GA/server/default/deploy/docflowweb.war]
> at org.jboss.system.server.profileservice.repository.BasicDeploymentRepository.removeDeployment(BasicDeploymentRepository.java:268)
> at org.jboss.system.server.profileservice.repository.BasicDeploymentRepository.removeDeployment(BasicDeploymentRepository.java:229)
> at org.jboss.profileservice.management.upload.remoting.DeployHandler.removeDeployment(DeployHandler.java:176)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.remove(AbstractDeployHandler.java:333)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:185)
> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
> at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
> at org.jboss.remoting.Client.invoke(Client.java:1724)
> at org.jboss.remoting.Client.invoke(Client.java:629)
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
> ... 15 more
> 14:55:54,153 WARN [AbstractManagedObjectPopulator] Cannot create String name from non-Simple property: ManagedProperty{JNDIName,JNDIName,metaType=SimpleMetaType:java.lang.String}, value=null
> 14:55:54,159 WARN [AbstractManagedObjectPopulator] Cannot create String name from non-Simple property: ManagedProperty{JNDIName,JNDIName,metaType=SimpleMetaType:java.lang.String}, value=null
> I think some thread in JBoss locks the war archive. something related to new vfs system that was introduced in JBoss 5.
> No such problems occurred in JBoss 4.2.3 or early versions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list