Patching WildFly application server

User Rating: 4 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Inactive
 

The final version of WildFly 8.1.0 has been released and it contains also the first patch to apply for updating the installation from 8.0.0 Final to 8.1.0. This tutorial shows how to do it.

 


The first obvious thing you need is downloading the patch which is available at www.wildfly.org:
wildfly patch wildfly patch
Download the "Update Existing 8.0.0.Final Install" which is a zipped 110 MB archive. Yes pretty big, as the amount of changes in libraries are quite a lot. Future patches of the application server should be quite smaller. So what are the advantages of applying a patch to the application server ? I can see two main benefits:

 

  • First of all patches can be applied both offline and online, so they don't require a full stop of your server farm
  • The Patch can be rolled back so it's much more conveniente than making another installation of WildFly and backing up the distribution.

In order to apply the 8.1.0 patch just unzip the patch bundle in a folder of your like let's say c:\patch8.1. Now we will show how to apply it to in offline mode. Launch the CLI when WildFly is shut down 

jboss-cli.bat	

from disconnected mode execute the following command:

 

[disconnected /] patch apply c:\patch8.1\wildfly-8.1.0.Final.patch --override-all
{
"outcome" : "success",
"result" : {}
}

Please notice that the patch installation might find some conflicts which prevent the installation. In this case review the conflicts. If you find them not critical (might be for example the README.txt file in the deployments folder!) just choose the --override-all in order to solve any conflicts:

patch apply c:\patch8.1\wildfly-8.1.0.Final.patch --override-all

You can follow the same guidelines for installing the patch in online mode, just you will be warned that the server needs a restart:
{
"outcome" : "success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
When the server is restarted, check that the new 8.1.0 version has been correclty installed:
21:33:45,857 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
21:33:45,858 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.1.0.Final "Kenny" started in 512ms - Started 207 of 251 services (86 services are lazy, passive or on-demand)


Patch rollback can be executed in either online or offline modes as specified above. The steps are the same as applying a patch, although instead a rollback command is used instead of the apply command:

[standalone@localhost:9990 /] patch rollback --reset-configuration=true
{
"outcome" : "success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}

 

Related articles available on mastertheboss.com

Wildfly 8 introduction

JBoss AS has a new name: as you probably know future versions of

Configuring Eclipse to use WildFly

This tutorial shows how to install JBoss Tools 4.3.1 plugin 

Maven configuration for Java EE 7 projects on WildFly

In this tutorial we will learn how to configure Maven Project Obj

Running WildFly with JDK 8

The JDK 1.8 early access is available for download at Oracle's si

Configuring WildFly Batch Job Repository

WildFly ships with a subsystem named batch which is the administr

Monitoring WildFly using VisualVM

This short tutorial shows how you can connect to WildFly 8 using

Follow us on Twitter