Troubleshooting JBoss Server Migration Tool in JBoss EAP

Solution Verified - Updated

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7
  • JBoss Server Migration Tool

Issue

jboss-server-migration.sh failing to migrate with this error: 

ERROR [logger] Migration failed: org.jboss.migration.core.ServerMigrationFailureException: org.jboss.migration.wfly10.config.management.ManagementOperationException: org.wildfly.core.embedded.EmbeddedProcessStartException: WFLYEMB0021: Cannot start embedded process
	at org.jboss.migration.cli@1.10.0.Final-redhat-00023//org.jboss.migration.core.task.TaskExecutionImpl.run(TaskExecutionImpl.java:174)
        ...
Caused by: org.jboss.migration.wfly10.config.management.ManagementOperationException: org.wildfly.core.embedded.EmbeddedProcessStartException: WFLYEMB0021: Cannot start embedded process
	at org.jboss.migration.cli@1.10.0.Final-redhat-00023//org.jboss.migration.wfly10.config.management.impl.EmbeddedStandaloneServerConfiguration.startConfiguration(EmbeddedStandaloneServerConfiguration.java:91)
        ...
Caused by: org.wildfly.core.embedded.EmbeddedProcessStartException: WFLYEMB0021: Cannot start embedded process
	at org.wildfly.embedded@15.0.22.Final-redhat-00001//org.wildfly.core.embedded.EmbeddedStandaloneServerFactory$StandaloneServerImpl.start(EmbeddedStandaloneServerFactory.java:324)
        ...
Caused by: java.util.concurrent.ExecutionException: JBTHR00005: Operation failed
	at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:253)
        ...
Caused by: java.lang.Exception: WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
	at org.jboss.as.server@15.0.22.Final-redhat-00001//org.jboss.as.server.BootstrapListener.bootFailure(BootstrapListener.java:87)
...

Resolution

See the main solution How to use JBoss Server Migration Tool to upgrade from one version of JBoss EAP 7.x to another version of JBoss EAP 7.x about details on the tool usage and see Diagnostic Steps for specific troubleshooting steps.

Related Solutions:

Diagnostic Steps

  • Apply the latest Update to both the source and target EAP server installations before running the jboss-server-migration.sh.
  • Check the $JBOSS_HOME/migration/logs/migration.log in the $JBOSS_HOME of the target server, it will show the the logging from when the embedded process tried to start.
  • Make sure the source server actually starts with the given configuration, as the migration tool cannot migrate configuration if the configuration in the source server is invalid (this is what will cause the embedded process to fail to start).
  • Open a This content is not included.support case and provide the:
    • $JBOSS_HOME/migration/logs/migration.log from the target server
    • The configuration from the source server that is failing to migrate
SBR
Product(s)
Components
Category
Tags

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.