How to remove exploded war in JBoss without stopping the server?

Question

I can delete everything except lib folder(JBoss says application is undeployed, but he wont release the jars).

I tied jboss-maven-plugin and hard-undeploy, however it says that file(doc says it also support dirs) is undeployed, however it does not undeploy application.

Im using jboss-4.2.1.GA. I bet it can be undeployed through jmx-console, but i weren't able to find out how.

Hotdeployment (undeployment) is should not be used in productive environments. — Christian Kuetbach, Dec 08 '10 at 10:22
I disagree, I think its more productive to not re-deploy a webapp :) I think you mean production environments. — IAdapter, Dec 08 '10 at 20:28

score 1 · Accepted Answer · answered Dec 08 '10 at 10:31

The way Seam performs an undeploy an exploded application is

<target name="unexplode" description="Undeploy the exploded archive">
        <delete failonerror="no">
            <fileset dir="${ear.deploy.dir}">
                <exclude name="**/*.jar"/>
            </fileset>
        </delete>
        <delete file="${deploy.dir}/${project.name}-ds.xml" failonerror="no"/>
        <delete dir="${ear.deploy.dir}" failonerror="no"/>
</target>

this usually works good, sometimes I need to restart (by touching a file which is observerd by the deployer)

<target name="restart-exploded">
    <antcall target="explode"/>
    <touch file="${ear.deploy.dir}/META-INF/application.xml"/>
</target>

score 0 · Answer 2 · answered Dec 08 '10 at 10:12

0

Remove your application manually under from work and tmp folders under your jboss installation. Stop JBoss before and start it after. This will help.

answered Dec 08 '10 at 10:12

AlexR

114,158
16
130
208

The Libs aren't unloaded completely from the Classloader. The JVM holds a filehandle and especially windows can't delete the files. – Christian Kuetbach Dec 08 '10 at 10:22
After I stop the server I just need to delete exploded dir, but Id like to be able to undeploy without stopping the server. – IAdapter Dec 08 '10 at 19:02

score 0 · Answer 3 · answered Dec 08 '10 at 10:24

I think what is happens is:

The WAR file is deployed and exploded.
When your application starts, its classloader opens the JAR files and locks them to prevent them from being removed or overwritten.
You then stop and undeploy the application.
Unfortunately the classloader still exists, and the locks it still holds prevent removal of the JAR files.

The classloader could still exist for two reasons:

It could be unreachable, but the GC hasn't run.
It could have been leaked, so it won't removed even if the GC does run.

The only sure solution is to shutdown and restart JBoss.

How to remove exploded war in JBoss without stopping the server?

3 Answers3