WildFly: Removing a Failed Deployment with JBoss CLI

Published September 5, 2016

Humorous illustration of a server mascot panicking while removing a failed deployment with JBoss CLI, with error messages flying around.

I was having trouble working out how to remove the WAR file of a failed deployment from WildFly using the JBoss CLI. I found that I could not simply type undeploy <WAR name> to remove a failed deployment from WildFly using the JBoss CLI. However, I did find that the following command let me remove a failed deployment and it’s WAR file.

/deployment=<WAR name>:remove

After running this command I checked that the failed deployment and it’s WAR file had been removed by running deployment-into and then by looking in the WildFly deployment’s folder on the disc. This command had successfully removed the deployment and it’s WAR file.

Responsible AI Coding: What I’ve Learned So Far

May 9, 2025

Computing

A whole new way of coding. When JetBrains offered me a trial of Junie, an AI assistant built into IntelliJ, I had to give it a go. I soon saw the potential, it’s kind of like an AI coding partner (albeit a little dumb at times), but that’s okay, if used responsibly. So here’s what I’ve learned about coding responsibly with AI—so far.

WildFly: Removing a Failed Deployment with JBoss CLI

Latest Posts

Configure Terraform Cloud to Assume an AWS IAM Role via OIDC

Responsible AI Coding: What I’ve Learned So Far

Notes on Successfully Running Ubuntu in VirtualBox