You might encounter problems while migrating from an older version of WebSphere Application Server.
CWSIC1002E: An internal error occurred. An object of class JsMessage cannot be created because of exception MessageDecodeFailedException
com.ibm.ws.sib.mfp.MessageDecodeFailedException: com.ibm.ws.sib.mfp.jmf.JMFSchemaViolationException: messageType not compatible with null... CWSIC1003E: An internal error occurred. An object of class JsMessage cannot be created because of exception MessageDecodeFailedException" with a stack trace that contains the com.ibm.ws.sib.mfp.MessageDecodeFailedException exception
This problem can occur if you are trying to run the WASPostUpgrade tool or the WASPreUpgrade tool from a directory other than app_server_root\bin. Verify that the WASPostUpgrade or WASPreUpgrade scripts reside in the app_server_root\bin directory, and launch either file from that location.
The administrative console no longer displays deprecated JDBC provider names. The new JDBC provider names used in the administrative console are more descriptive and less confusing. The new providers will differ only by name from the deprecated ones.
The deprecated names will continue to exist in the jdbc-resource-provider-templates.xml file for migration reasons (for example, for existing JACL scripts); however, you are encouraged to use the new JDBC provider names in your JACL scripts.
The WASPreUpgrade tool saves selected files from WebSphere Application Server Version 4.x and Version 5.x bin directories. It also exports the existing application server configuration from the repository.
If you are migrating from WebSphere Application Server Version 4.0.x Advanced Edition, the WASPreUpgrade command calls the XMLConfig command to export the existing application server configuration from the repository. If errors occur during this part of the WASPreUpgrade command, you might have to apply fixes to the installation to successfully complete the export step. Contact IBM Support for the latest applicable fixes.
This problem can occur if you are trying to run the WASPostUpgrade tool or the WASPreUpgrade tool from a directory other than app_server_root\bin. Verify that the WASPostUpgrade or WASPreUpgrade scripts reside in the app_server_root\bin directory, and launch either file from that location.
The most likely cause of this error is that Version 4.0.x or 5.x of the WebSphere Application Server is installed, and the WASPostUpgrade tool was not run from the bin directory of the WebSphere Application Server Version 6.0.x installation root.
MIGR0002I: java com.ibm.websphere.migration.postupgrade.WASPostUpgrade backup_directory_name -adminNodeName primary_node_name [-nameServiceHost host_name [ -nameServicePort port_number]] [-substitute "key1=value1[;key2=value2;[...]]"] In input xml file, the key(s) should appear as $key$ for substitution.") [-import xml data file] [-traceString trace specification [-traceFile filename]]}"
To correct this problem, run the WASPostUpgrade command from the bin directory of the WebSphere Application Server Version 6.0.x installation root.
Manually install the applications using wsadmin after WASPostUpgrade has completed.
If you did not find your problem listed, contact IBM support.
In this information ...Subtopics
| IBM Redbooks, demos, education, and more(Index) Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |