JBoss EAP 7 jboss-server-migration tool failing with WARNING JBOSS_HOME may be pointing to a different installation

Solution Verified - Updated -

Issue

We are trying to run the jboss-server-migration tool and it is failing with the error below:

Beginning migrating from EAP 7.2 to 7.3 for instance 'myconfig'.
   [Ensure that JBoss JVM for 'myconfig' is NOT running on peer host(s)]
...
Executing Migation script as follows:
...
WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.

Failed to invoke setter setFileName with value /home/jboss7/jboss-eap-7.3/migration/logs/migration.log
.java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.jboss.logmanager.config.AbstractPropertyConfiguration$1.applyPostCreate(AbstractPropertyConfiguration.java:217)
        at org.jboss.logmanager.config.AbstractPropertyConfiguration$1.applyPostCreate(AbstractPropertyConfiguration.java:197)
        at org.jboss.logmanager.config.LogContextConfigurationImpl.doApplyPostCreate(LogContextConfigurationImpl.java:313)
        at org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:345)
        at org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:289)
        at org.jboss.logmanager.config.LogContextConfigurationImpl.commit(LogContextConfigurationImpl.java:298)
        at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:546)
        at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97)
        at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:170)
        at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:132)
        at java.util.logging.LogManager$3.run(LogManager.java:399)
        at java.util.logging.LogManager$3.run(LogManager.java:396)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396)
        at java.util.logging.LogManager.access$800(LogManager.java:145)
        at java.util.logging.LogManager$2.run(LogManager.java:345)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338)
        at java.util.logging.LogManager.getLogManager(LogManager.java:378)
        at org.jboss.modules.Main.main(Main.java:523)
Caused by: java.io.FileNotFoundException: /home/jboss7/jboss-eap-7.3/migration/logs/migration.log (No such file or directory)
        at java.io.FileOutputStream.open0(Native Method)
        at java.io.FileOutputStream.open(FileOutputStream.java:270)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
        at org.jboss.logmanager.handlers.FileHandler.setFile(FileHandler.java:151)
        at org.jboss.logmanager.handlers.FileHandler.setFileName(FileHandler.java:189)
        ... 24 more
16:38:38,265 INFO  [logger] SOURCE server name: JBoss EAP, version: 7.2.7.GA.
16:38:38,286 INFO  [logger] TARGET server name: JBoss EAP, version: 7.3.0.GA.

----------------------------------------------------------
----------------------------------------------------------

Server migration starting...

16:38:38,349 INFO  [ServerMigrationTask#1:1] --- Migrating modules requested by environment...
16:38:38,349 INFO  [ServerMigrationTask#1:1] No modules to migrate.
16:38:38,351 INFO  [ServerMigrationTask#1:2] --- Migrating standalone server...
16:38:38,999 INFO  [ServerMigrationTask#1:2:1] Target's standalone dirs initialized.
16:38:39,007 INFO  [ServerMigrationTask#1:2:3] Source's standalone configurations found: [standalone-full-ha.xml]
16:38:39,008 INFO  [ServerMigrationTask#1:2:3:1] Migrating standalone configuration standalone-full-ha.xml...
...
16:38:43,795 INFO  [security] ELY00001: WildFly Elytron version 1.10.4.Final-redhat-00001
16:38:47,860 ERROR [logger] Migration failed: org.jboss.migration.core.ServerMigrationFailureException: org.jboss.migration.wfly10.config.management.ManagementOperationException: WFLYCTL0369: Required capabilities are not available:
    org.wildlfy.microprofile.config; There are no known registration points which can provide this capability.
        at org.jboss.migration.core.task.TaskExecutionImpl.run(TaskExecutionImpl.java:174) [jboss-server-migration-core-1.7.1.Final-redhat-00003.jar:1.7.1.Final-redhat-00003]
        at org.jboss.migration.core.task.TaskExecutionImpl.execute(TaskExecutionImpl.java:159) [jboss-server-migration-core-1.7.1.Final-redhat-00003.jar:1.7.1.Final-redhat-00003]
...
Caused by: org.jboss.migration.wfly10.config.management.ManagementOperationException: WFLYCTL0369: Required capabilities are not available:
    org.wildlfy.microprofile.config; There are no known registration points which can provide this capability.
        at org.jboss.migration.wfly10.config.management.impl.AbstractManageableServerConfiguration.processResult(AbstractManageableServerConfiguration.java:103) [jboss-server-migration-wildfly10.0-1.7.1.Final-redhat-00003.jar:1.7.1.Final-redhat-00003]
        at org.jboss.migration.wfly10.config.management.impl.AbstractManageableServerConfiguration.executeManagementOperation(AbstractManageableServerConfiguration.java:116) [jboss-server-migration-wildfly10.0-1.7.1.Final-redhat-00003.jar:1.7.1.Final-redhat-00003]

Environment

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

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In