How to check the JBoss EAP 6/7/8 version?

Environment

• Red Hat JBoss Enterprise Application Platform (EAP)
  • 8.x
  • 7.x
  • 6.x

Issue

• How to check the JBoss EAP 8 Update version ?
• What options exist to find out the JBoss EAP version?
• How do we verify that we are using JBoss EAP provided by Red Hat (and not the community release)?
• How do I check the JBoss EAP version?
• What version of JBoss EAP am I using?
• I need to get a list of machines running a community version of JBoss EAP and those running the supported version. How do I do this?
• What is the easiest way of detecting which version of JBoss EAP I am running?
• How can I tell whether I am running a community or support the JBoss EAP release?
• Is there a way to find out the JBoss EAP version number with the patch level from the Windows command line or a PowerShell command to do the same? Is there a way via the CLI?

Resolution

Table of Contents

• Using the standalone.sh or domain.sh
• Using the JBoss CLI on a local server (embedded)
• Using the JBoss CLI on a remote server
• When connected with the JBoss CLI
• Domain Mode
• Using the Web Management Console
• Using the version.txt
• Using the server.log
• Using OQL with a heap dump
• Using channel versions

Using the standalone.sh (or domain.sh) with --version (or -v or -V) option. It will print version and exit.

/eap/8.x/8.0.4.1/bin $ ./standalone.sh --version
(...)
17:23:59,523 INFO  [org.jboss.modules] (main) JBoss Modules version 2.1.4.Final-redhat-00001
JBoss EAP 8.0 Update 4.1 (WildFly Core 21.0.11.Final-redhat-00001)


/eap/7.x/7.4/7.4.19/bin $ ./standalone.sh -v
(...)
16:21:35,423 INFO  [org.jboss.modules] (main) JBoss Modules version 1.12.3.Final-redhat-00001
JBoss EAP 7.4.19.GA (WildFly Core 15.0.39.Final-redhat-00001)


/eap/6.x/6.4/6.4.24/bin $ ./standalone.sh --version
(...)
08:15:34,862 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.11.Final-redhat-1
JBoss EAP 6.4.24.GA (AS 7.5.24.Final-redhat-00001)

Using the JBoss CLI on a local server (embedded).

/eap/8.x/8.0.4.1/bin $ ./jboss-cli.sh  --output-json --commands="embed-server,:read-attribute(name=product-version),stop-embedded-server"
{
    "outcome" => "success",
    "result" => "8.0 Update 4.1"
}


/eap/7.x/7.4/7.4.19/bin $ ./jboss-cli.sh  --output-json --commands="embed-server,:read-attribute(name=product-version),stop-embedded-server"
{
    "outcome" : "success",
    "result" : "7.4.19.GA"
}

NOTE: The embed-server CLI command was added in EAP 7.0 and later.

Using the JBoss CLI on a remote server

Standalone Mode

/eap/8.x/8.0.4.1/bin $ ./jboss-cli.sh  -c --command=":read-attribute(name=product-version)"
{
    "outcome" => "success",
    "result" => "8.0 Update 4.1"
}


/eap/7.x/7.4/7.4.19/bin $ ./jboss-cli.sh  -c --command=":read-attribute(name=product-version)"
{
   "outcome" => "success",
   "result" => "7.4.19.GA"
}


/eap/6.x/6.4/6.4.24/bin $ ./jboss-cli.sh  -c --command=":read-attribute(name=product-version)"
{
    "outcome" => "success",
    "result" => "6.4.24.GA"
}

Or when connected with the JBoss CLI

/eap/8.x/8.0.4.1/bin $ ./jboss-cli.sh -c
[standalone@localhost:9990 /] :read-attribute(name=product-version)
{
    "outcome" => "success",
    "result" => "8.0 Update 4.1"
}


/eap/7.x/7.4/7.4.19/bin $ ./jboss-cli.sh -c
[standalone@localhost:9990 /] :read-attribute(name=product-version)
{
    "outcome" => "success",
    "result" => "7.4.19.GA"
}


/eap/6.x/6.4/6.4.24/bin $ ./jboss-cli.sh -c
[standalone@localhost:9999 /] :read-attribute(name=product-version)
{
    "outcome" => "success",
    "result" => "6.4.24.GA"
}

Domain Mode

In domain mode, the domain controller and host controllers can be at different versions.

When running the command below, the version returned is that of the domain controller.

/eap/8.x/8.0.4.1/bin $ ./jboss-cli.sh -c
[domain@localhost:9990 /] :read-attribute(name=product-version)
{
    "outcome" => "success",
    "result" => "8.0 Update 4.1"
}


/eap/7.x/7.4/7.4.19/bin $ ./jboss-cli.sh -c
[domain@localhost:9990 /] :read-attribute(name=product-version)
{
    "outcome" => "success",
    "result" => "7.4.19.GA"
}


/eap/6.x/6.4/6.4.24/bin $ ./jboss-cli.sh -c
[domain@localhost:9999 /] :read-attribute(name=product-version)
{
    "outcome" => "success",
    "result" => "6.4.24.GA"
}

To check the version of a host controller that is connected to the domain controller, use the command shown below where primary, master or any other name is the host controller that user want to check.

/eap/8.x/8.0.4.1/bin $ ./jboss-cli.sh -c
[domain@localhost:9990 /] /host=primary:read-attribute(name=product-version)
{
    "outcome" => "success",
    "result" => "8.0 Update 4.1"
}


/eap/7.x/7.4/7.4.19/bin $ ./jboss-cli.sh -c
[domain@localhost:9990 /] /host=master:read-attribute(name=product-version)
{
    "outcome" => "success",
    "result" => "7.4.19.GA"
}


/eap/6.x/6.4/6.4.24/bin $ ./jboss-cli.sh -c
[domain@localhost:9999 /] /host=master:read-attribute(name=product-version)
{
    "outcome" => "success",
    "result" => "6.4.24.GA"
}

NOTE: There have been changes in the documentation from EAP 8.x onwards regarding Inclusive language and label changes.

Using the Web Management Console

Click on the HAL version in the bottom right of the Web Management Console

and it will display: Product Version: 8.0 Update ...

Using the version.txt

/eap/8.x/8.0.4.1 $ cat version.txt
Red Hat JBoss Enterprise Application Platform - Version 8.0 Update 4.1


/eap/7.x/7.4/7.4.19 $ cat version.txt
Red Hat JBoss Enterprise Application Platform - Version 7.4.19.GA


/eap/6.x/6.4/6.4.24 $ cat version.txt
Red Hat JBoss Enterprise Application Platform - Version 6.4.24.GA

NOTE: There is a fix This content is not included.JBEAP-26750 in 8.0 Update 4 that include the version of the update in the version.txt.

Using the server.log

A JBoss EAP server instance (standalone or domain) will log the version when starting and stopping for example:

/eap/8.x/8.0.4.1/standalone/log $ grep "WFLYSRV0049\|WFLYSRV0050" server.log | tail -2
2024-12-09 17:31:33,065 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: JBoss EAP 8.0 Update 4.1 (WildFly Core 21.0.11.Final-redhat-00001) starting
2024-12-09 17:31:33,661 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: JBoss EAP 8.0 Update 4.1 (WildFly Core 21.0.11.Final-redhat-00001) stopped in 3ms


/eap/7.x/7.4/7.4.19/standalone/log $ grep "WFLYSRV0049\|WFLYSRV0050" server.log | tail -2
2024-12-09 17:55:40,588 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: JBoss EAP 7.4.19.GA (WildFly Core 15.0.39.Final-redhat-00001) starting
2024-12-09 18:02:24,579 INFO  [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: JBoss EAP 7.4.19.GA (WildFly Core 15.0.39.Final-redhat-00001) stopped in 130ms


/eap/6.x/6.4/6.4.24/standalone/log $ grep "JBAS015899\|JBAS015950" server.log | tail -2
08:22:06,333 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.4.24.GA (AS 7.5.24.Final-redhat-00001) starting
08:22:12,544 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015950: JBoss EAP 6.4.24.GA (AS 7.5.24.Final-redhat-00001) stopped in 22ms

Using OQL with a heap dump

If user have a heap dump, they can use the following OQL to identify the JBoss EAP version:

SELECT startTime, prettyVersion.value.toString() FROM org.jboss.as.server.BootstrapListener 

Using channel versions

After This content is not included.EAP 8 Update 2, this command also list it:

/eap/8.x/8.1.GA/bin $ ./jboss-eap-installation-manager.sh channel versions
Installed server components:
  * EAP 8.1 GA

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.