Troubleshooting WebSphere Application Server problems

If you receive the following errors when configuring WebSphere Application Server (WAS), review the suggested solutions.
WAS installation or execution error Explanation and solution
You receive the following error:
Error: ADMG0004E: The system failed to save document cells/cell/security.xml

One of the possible causes for this error is that your system is not reading the encrypted password in your environment file properly.

To resolve this issue, make sure that you are using master password encryption and that your master.pwd file is in the WAS_ROOT\nexj directory.
You receive the following error:
Caused by: nexj.core.meta.MetadataException: err.meta.clusterKeystore
To resolve this issue, replace the following files with policy files of the same strength as the ones used for generating the master password file:
  • WAS_ROOT\java\jre\lib\security\local_policy.jar
  • WAS_ROOT\java\jre\lib\security\US_export_policy.jar
Managed nodes fail to synchronize before starting the application.

To resolve this issue, complete the following steps.

  1. Stop the deployment manager.
  2. In the deployment manager profile, delete the contents of the following directories:
    • wstemp
    • temp
    • config/temp
  3. Start the deployment manager.
  4. Stop the node or server. From the WAS_HOME/profile/bin directory, issue the stopNode command or the stopServer command.
  5. Manually synchronize the node. From the WAS_HOME/profile/bin directory, issue the syncNode.sh command. Since security is enabled, issue the command as follows:
    syncNode.sh DMgr_hostName DMgr_SOAPPort -username adminUser -password adminPassword

For more information about this issue, see the Managed node fails to synchronize technote on the IBM web site.
You receive an SSL certificate error.

To resolve this issue, you need to import the certificate from the WAS installation on the machine on which the deployment is done to the NexJ Studio host machine.

Run the following command on the NexJ Studio host machine:

WAS_ROOT\profiles\profile\bin\retrieveSigners ClientDefaultKeyStore ClientDefaultTrustStore -host adminHost -port adminPort -username adminUser -password adminPassword

When prompted, add the signer to the trust store.

To help with troubleshooting, review the system log files located in the WAS_HOME/profiles/profile/logs directory.

Tip: When configuring logging and tracing properties for your WAS installation, you may need to increase the default values for log file size and maximum number of log files. This prevents log files from being replaced too frequently. For example, set the maximum size to 50MB and set the maximum number of historical log files to 50.