WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Troubleshooting version-to-version migration

Review this page for troubleshooting tips if you encounter problems while migrating from an older version of WebSphere® ESB

The following sections describe specific errors and exceptions that may occur in a version-to-version migration and provide steps you can follow to understand and resolve these problems.

Application installation error

If you select the option for the migration process to install the enterprise applications that exist in the version 6.0.x or 6.1.x configuration into the new version 6.2 configuration, you might encounter some error messages during the application-installation phase of migration.

The applications that exist in the version 6.0.x or 6.1.x configuration might have incorrect deployment information—usually, incorrect XML documents that were not validated sufficiently in previous WebSphere ESB runtimes. The runtime now has an improved application-installation validation process and will fail to install these malformed EAR files. This results in a failure during the application-installation phase of WBIPostUpgrade and produces an "E:" error message.

If the application installation fails in this way during migration, you can do one of the following:
  • Fix the problems in the version 6.0.x or 6.1.x applications, and then remigrate.
  • Proceed with the migration and ignore these errors.

    In this case, the migration process does not install the failing applications but does complete all of the other migration steps.

    Later, you can fix the problems in the applications and then manually install them in the new version 6.2 configuration using the administrative console or an install script.

Application server error

After you migrate a managed node to version 6.2, the application server might not start.

When you try to start the application server, you might see errors similar to those in the following example:
[5/11/06 15:41:23:190 CDT] 0000000a SystemErr  R  
    com.ibm.ws.exception.RuntimeError:
com.ibm.ws.exception.RuntimeError:  org.omg.CORBA.INTERNAL: 
   CREATE_LISTENER_FAILED_4
vmcid: 0x49421000  minor code: 56  completed: No
[5/11/06 15:41:23:196 CDT] 0000000a SystemErr  R  at
com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:198)
[5/11/06 15:41:23:196 CDT] 0000000a SystemErr  R  at
com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:139)
[5/11/06 15:41:23:196 CDT] 0000000a SystemErr  R  at  
com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:460)
[5/11/06 15:41:23:196 CDT] 0000000a SystemErr  R  at  
com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
[5/11/06 15:41:23:196 CDT] 0000000a SystemErr  R  at  
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[5/11/06 15:41:23:196 CDT] 0000000a SystemErr  R  at  
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
[5/11/06 15:41:23:197 CDT] 0000000a SystemErr  R  at  
sun.reflect.DelegatingMethodAccessorImpl.invoke
    (DelegatingMethodAccessorImpl.java:43)
Change the port number at which the managed node's server is listening. If the deployment manager is listening at port 9101 for ORB_LISTENER_ADDRESS, for example, the server of the managed node should not be listening at port 9101 for its ORB_LISTENER_ADDRESS. To resolve the problem in this example, perform the following steps:
  1. On the administrative console, click Application servers > server_name > Ports > ORB_LISTENER_ADDRESS.
  2. Change the ORB_LISTENER_ADDRESS port number to one that is not used.

Exceptions: database connectivity, loading, or missing class

Never change any WebSphere Application Server variables that are configured as a part of profile creation.

If you modify these values incorrectly in old profile, you might get database connectivity, loading, or other missing class exceptions, such as:

10/25/08 13:22:39:650 GMT+08:00] 0000002e J2CUtilityCla E J2CA0036E: An exception occurred while invoking method setDataSourceProperties on com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jdbc/com.ibm.ws.sib/ewps6101.Messaging-BPC.cwfpcCell01.Bus : com.ibm.ws.exception.WsException: DSRA0023E: The DataSource implementation class "com.ibm.db2.jcc.DB2XADataSource" could not be found.DB2,

Derby, and SQL Embedded JDBC drivers are bundled with the WebSphere ESB product installation. If you need to change these drivers to any higher version, you must copy drivers on same location where they exists in the product installation, as follows:
  • Derby: %was.install.root%\derby\lib
  • DB2: %was.install.root%/universalDriver_wbi/lib
  • SQL: %was.install.root%lib
If you need a new JDBC provider and datasource for your application, you can create these resources by selecting a valid jdbcclasspath and setting the WebSphere Application Server variable accordingly. For example, if you need DB2 at cell level which doesn't exist earlier in your installation, you could use the following procedure.
  1. In the administrative console, navigate to: Resources > JDBC > JDBC Providers > DB2 Universal JDBC Driver Provider (XA).
  2. In the Class path box, set the following paths:
    • DB2UNIVERSAL_JDBC_DRIVER_PATH =%was.install.root%/universalDriver_wbi/lib
    • DB2UNIVERSAL_JDBC_DRIVER_NATIVEPATH=""
    If you need your own drivers, set the following path: DB2UNIVERSAL_JDBC_DRIVER_PATH=%myDriverLocation%

Out of memory error

If either the WBIPreUpgrade or WBIPostUpgrade command-line utility fail due to Out of Memory problems, you can increase the heap size to a number that takes into consideration the size and scope of the environment being migrated, as well as what the machine will allow.

For instructions on how to increase the heap size, use the procedure described in Solution 4 of the following technote: Handling certain Out of Memory conditions when migrating an earlier version of WebSphere Application Server to V6.0.2, V6.1, or 7.0.

Profile creation error

While you are using the version 6.2 migration wizard to create a profile when migrating a configuration, you might see the following profile-creation error messages.

profileName: profileName cannot be empty
profilePath: Insufficient disk space

These error messages might be displayed if you enter a profile name that contains an incorrect character such as a space. Rerun the migration wizard, and verify that there are no incorrect characters in the profile name such as a space, quotes, or any other special characters.

Profile migration error

When you use the migration wizard to migrate a profile from WebSphere ESB version 6.0.x or 6.1.x to version 6.2 on a Solaris x64 processor-based system, the migration might fail during the WBIPostUpgrade step.

You might see messages similar to the following in profile_root/logs/WASPostUpgrade.time_stamp.log:
MIGR0327E: A failure occurred with stopNode.
MIGR0272E: The migration function cannot complete the command.

WebSphere ESB version 6.0.x or 6.1.x uses a Java™ virtual machine (JVM) in 32-bit mode. The migration wizard for WebSphere ESB version 6.2 calls the WBIPostUpgrade.sh script, which attempts to run the JVM for version 6.0.x or 6.1.x in the 64-bit mode when the server stops the version 6.0.x or 6.1.x node.

Complete the following actions to remove the incomplete profile and enable WebSphere ESB to correctly migrate the version 6.0.x or 6.1.x profile:
  1. On a command line, change to the install_root/bin directory.
    For example, type the following command:
    cd /opt/IBM/WebSphere/ESB/bin
  2. Locate the WBIPostUpgrade.sh script in the install_root/bin directory, and make a backup copy.
  3. Open the WBIPostUpgrade.sh or WBIPostUpgrade.bat file in an editor, and perform the following actions:
    1. Locate the following line of code:
      For UNIX operating systemFor Linux operating system
      "$binDir" /setupCmdLine.sh
      For Windows operating system
      call "%~dp0setupCmdLine.bat" %*
    2. Insert the following line of code after the code that was identified in the previous step:
      JVM_EXTRA_CMD_ARGS=""
    3. Save the changes.
  4. Repeat steps 2 through 4 with theWASPostUpgrade.sh or the WASPostUpgrade.bat file.
  5. Delete the incomplete version 6.2 profile that was created during the migration process. Use the following procedure.
    1. Open a command prompt and run one of the following commands, based on your operating system:
      • For i5/OS operating system On i5/OS® platforms: manageprofiles -delete -profileName profile_name
      • For Linux operating systemFor UNIX operating system On Linux® and UNIX® platforms: manageprofiles.sh -delete -profileName profile_name
      • For Windows operating system On Windows® platforms: manageprofiles.bat -delete -profileName profile_name

      The variable profile_name represents the name of the profile that you want to delete.

    2. Confirm that the profile deletion has completed by checking the following log file:
      • For i5/OS operating system On i5/OS platforms: user_data_root/profileRegistry/logs/manageprofiles/profile_name_delete.log
      • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms: install_root/logs/manageprofiles/profile_name_delete.log
      • For Windows operating system On Windows platforms: install_root\logs\manageprofiles\profile_name_delete.log
  6. Delete the profile_root directory of the version 6.2 profile that was removed in the previous step.
  7. Rerun the migration wizard.

Synchronization error

If synchronization fails when you migrate a managed node to version 6.2, the server might not start.

You might receive messages similar to the following when you migrate a managed node to version 6.2:
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0111E: Program exiting with error:
           com.ibm.websphere.management.exception.AdminException: ADMU0005E:
           Error synchronizing repositories
ADMU0211I: Error details may be seen in the file:
           /opt/WebSphere/62AppServer/profiles/AppSrv02/logs/syncNode.log
MIGR0350W: Synchronization with the deployment manager using the SOAP protocol 
 failed.
MIGR0307I: The restoration of the previous WebSphere Application Server 
 environment is complete.
MIGR0271W: Migration completed successfully, with one or more warnings.
These messages indicate the following:
  • Your deployment manager is at a version 6.2 configuration level.
  • The managed node that you are trying to migrate is at a version 6.2 configuration level on the deployment manager's repository (including applications).
  • The managed node itself is not quite complete given that you did not complete the syncNode operation.
Perform the following actions to resolve this issue:
  1. Rerun the syncNode command on the node to synchronize it with the deployment manager.

    See the syncNode command .

  2. Run the GenPluginCfg command.

    See the GenPluginCfg command .


reference Reference topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tmig_vtv_troublesht.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).