Migration of Jboss 7.2.x to 7.4.x fails
search cancel

Migration of Jboss 7.2.x to 7.4.x fails

book

Article ID: 282624

calendar_today

Updated On: 02-17-2025

Products

CA Identity Manager CA Identity Suite

Issue/Introduction

When migrating JBoss 7.2.x to 7.4.x using Symantec_migration_tool.bat, migration failure error is encountered. 
Errors as seen from the migration.log

2024-03-12 13:34:07,386 INFO  [ServerMigrationTask#1:2:3] Source's standalone configurations found: [iam_im-reference-standalone-full-ha.xml, iam_im-reference-standalone-full.xml, standalone-full-ha.xml, standalone-full.xml, standalone-ha.xml, standalone-load-balancer.xml, standalone-osgi.xml, standalone.xml]
2024-03-12 13:34:07,386 INFO  [ServerMigrationTask#1:2:3:1] Migrating standalone configuration iam_im-reference-standalone-full-ha.xml...
....
....
024-03-12 13:34:10,206 ERROR [controller] WFLYCTL0362: Capabilities required by resource '/subsystem=infinispan/cache-container=web/transport=jgroups' are not available:
    org.wildfly.clustering.jgroups.channel-factory.ee-web; Possible registration points for this capability: 
        /subsystem=jgroups/channel=*
        /subsystem=jgroups/channel=*/fork=*
        /subsystem=jgroups/stack=*
2024-03-12 13:34:10,206 ERROR [controller] WFLYCTL0362: Capabilities required by resource '/subsystem=infinispan/cache-container=server/transport=jgroups' are not available:
    org.wildfly.clustering.jgroups.channel-factory.ee-singleton; Possible registration points for this capability: 
        /subsystem=jgroups/channel=*
        /subsystem=jgroups/channel=*/fork=*
        /subsystem=jgroups/stack=*
2024-03-12 13:34:10,206 ERROR [controller] WFLYCTL0362: Capabilities required by resource '/subsystem=infinispan/cache-container=hibernate/transport=jgroups' are not available:
    org.wildfly.clustering.jgroups.channel-factory.ee-hibernate; Possible registration points for this capability: 
        /subsystem=jgroups/channel=*
        /subsystem=jgroups/channel=*/fork=*
        /subsystem=jgroups/stack=*
2024-03-12 13:34:10,206 ERROR [controller] WFLYCTL0362: Capabilities required by resource '/subsystem=infinispan/cache-container=ejb/transport=jgroups' are not available:
    org.wildfly.clustering.jgroups.channel-factory.ee-ejb; Possible registration points for this capability: 
        /subsystem=jgroups/channel=*
        /subsystem=jgroups/channel=*/fork=*
        /subsystem=jgroups/stack=*

2024-03-12 13:34:10,596 ERROR [controller] WFLYCTL0369: Required capabilities are not available:
    org.wildfly.clustering.jgroups.channel-factory.ee-singleton; Possible registration points for this capability: 
        /subsystem=infinispan/cache-container=*/transport=jgroups
    org.wildfly.clustering.jgroups.channel-factory.ee-hibernate; Possible registration points for this capability: 
        /subsystem=infinispan/cache-container=*/transport=jgroups
    org.wildfly.clustering.jgroups.channel-factory.ee-web; Possible registration points for this capability: 
        /subsystem=infinispan/cache-container=*/transport=jgroups
    org.wildfly.clustering.jgroups.channel-factory.ee-ejb; Possible registration points for this capability: 
        /subsystem=infinispan/cache-container=*/transport=jgroups

Environment

Source: JBoss EAP 7.2.x 
Desitnation: JBoss EAP 7.4.x (7.4.0 GA + update 15 or above)

Cause

Aforementioned issues are observed on JBoss EAP 7.4 update 15 and above. 

Resolution

Reviewing the migration.log, it can be observed that migration was indeed successful. Erros that we see are related to migration of standalone file which is not used (iam_im-reference-standalone-full-ha.xml), for the others including standalone-full.xml, it all looks good.

Please be informed that the migration script has been certified with JBoss 7.4 update 8 which was the latest JBoss update available at the time of certification.

We did some tests on our side and this problem was encountered with 7.4 update 15 & after. JBoss 7.4 update 14 works without issues. 

Recommendations:
1. If this a test/non-prod environment, please test the migration by starting the JBoss with IM and verify if that is working. 
OR
2. Perform a clean migration, by re-deploying a JBoss 7.4 GA + update 14 or lower.

Also make sure there are no extra backup XML files in the \standalone\configuration folder