Applying update fails when JBoss EAP 8.0.x installation directory (JBOSS_HOME) is symbolic link

Solution Unverified - Updated -

Issue

When specified JBoss EAP 8.x installation directory (JBOSS_HOME) is a symbolic link, applying update fails with the following ERROR:

ERROR: java.nio.file.FileAlreadyExistsException: <specified-symbolic-link-of-JBOSS_HOME-directory>".

It looks failed at the last part of applying updates (copying jboss-modules.jar) and other files (jar files under modules directory) are appearantly updated before the ERROR message. So, even if applying update stopped with the ERROR message and not completed correctly, the version information output of ./bin/standalone.sh --verion shows newer versions (like JBoss EAP 8.0.2).

As $JBOSS_HOME/jboss-modules.jar is not updated, so the following ERROR can happen when starting "embed-server" in JBoss-CLI in JBoss EAP 8.0.2. Because the org.jboss.modules.ModuleLoggerFinder only exists in newer versions of jboss-modules.jar included in JBoss EAP 8.0.2+ and some modules (like "embed-server") depends on it.

$ ./bin/jboss-cli.sh 
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] embed-server 
org/jboss/modules/ModuleLoggerFinder: org.jboss.modules.ModuleLoggerFinder from [Module "org.wildfly.embedded" version 21.0.9.Final-redhat-00001 fr
om local module loader @3a1a3f52 (finder: local module finder @7177ab38 (roots: /opt/jboss8/modules,/opt/jboss8/modules/system/layers/base))]

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 8.0.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content