Migration Troubleshooting

Resolve the migration errors that you may come across after migrating to TIBCO MDM.

Issue Description Solution
TIBCO MDM server start-up failure after migration After migration from the previous version to 9.0 version, the following exception may occur at the server startup:
INF-7508: Total of all limits for distributed and near caches should not exceed 100 (percent).
Manually update the CacheConfig.xml file. Perform any one of the following changes:
  • Adjust limits of the DISTRIBUTED and NEAR cache types. Ensure the sum of these limits should be less than or is equal to (<=) 100.
  • Replace the <Limit> cache attribute with the <ListSize> cache attribute. Specify the appropriate value for the <ListSize> cache attribute.
TIBCO MDM server start-up failure after WildFly Application Server migration When you migrate from the WildFly Application Server 14.0.0 to 16.0.0 version, the javax.ejb.NoSuchEJBException: EJBCLIENT000079 exception occurs in the error.log file for loading of the FileWatcher and PreloadManager classes.
  1. Log in to Configurator.
  2. Remove the following values from the existing configuration property [Static Receiver Initialization List (com.tibco.cim.initialize.receiver.static)] and add them to the new configuration property [Static Receiver Lazy Initialization List (com.tibco.cim.initialize.receiver.static.lazy)]:
    • FileWatcher:com.tibco.cim.init.FileWatcher
    • PreloadManager: com.tibco.cim.init.PreLoadManager
    Moving these values to the Static Receiver Lazy Initialization List configuration property ensures lazy loading of the PreloadManager and FileWatcher classes, that is, the classes are loaded after starting the WildFly Application Server.