Errors deploying, installing, or promoting applications

 

1. App installed using wsadmin.sh. App does not display under Applications | Manage Applications.

2. java.lang.RuntimeException: Failed_saving_bytes_to_wor_ERROR_ in the Assembly Toolkit, administrative console or wsadmin tool

3. WASX7015E error running wsadmin.sh AdminApp installInteractive or $AdminApp install..

4. A DDL generated by the Application Assembly tool (AAT) throws an SQL error on the target platform.

5. The error ADMA0004E... Validation error in task Specifying the Default Datasource for EJB 1.x Modules occurs when installing application in administrative console or wsadmin.sh.

6. The error No valid target is specified in ObjectName object for module module occurs from installation.

7. The addNode -includeapps option does not appear to upload all applications to the deployment manager.

8. "Timeout!!!" error displays when attempting to install an enterprise application in the administrative console.

9. During application installation, the call to EJB deploy throws an exception

10. While uploading documents, addNode -includeapps fails with an OutOfMemoryError exception

Check the following first...

• Verify that the logical name that you have specified to appear on the console for your application, enterprise bean module or other resource does not contain invalid characters such as these: - / \ : * ? " < > |.

• If the application was installed using the wsadmin $AdminApp install command with the -local flag, restart the server or rerun the command without the -local flag.

If you do not see a problem that resembles yours, or if the information provided does not solve your problem, check to see if the problem is identified and documented by looking at available online support including hints and tips, technotes, and fixes. If the problem has not been identified, see Obtaining help from IBM.

 

App installed using wsadmin.sh, but the application does not display under Applications-Manage Applications

The application might be installed but you have not saved the configuration...

1. Verify that the application subdirectory is located under the $WAS_HOME/installedApps directory.

2. Run the $AdminApp list command and verify that the application is not among those displayed.

   • In the bin directory, run the wsadmin.bat or wsadmin.sh command.

   • From the wsadmin prompt, enter $AdminApp list and verify that the problem application is not among the items that display.

3. Reinstall your application using wsadmin.sh. Run the $AdminConfigsave command in tje wsadmin.sh before exiting.

 

I get a java.lang.RuntimeException: Failed_saving_bytes_to_wor_ERROR_ error in Application Assembly Tool (AAT)Assembly Toolkit, administrative console or the wsadmin.sh.

If you see this error when attempting to generate deployed code in the Assembly Toolkit, installing an application or module in the administrative console, or using wsadmin.sh to install an application or module, the file path length of the temporary system file might be exceeded. This situation is typically an issue only on Windows platforms.

To verify this problem, check the TEMP and TMP environment variables for your system. Long environment variables add path length to the file names accessed by the EJBDeploy tool.

To resolve the problem...

1. Stop all WAS processes and close all DOS prompts.

2. Set the TMP and TEMP environment variables to something short, for example C:\TMP and C:\TEMP.

3. Reinstall the application.

Otherwise, try rebooting and redeploying or reinstalling the application.

 

WASX7015E error running wsadmin command "$AdminApp installInteractive" or "$AdminApp install"

This problem has two possible causes...

• If the full text of the error is similar to

  WASX7015E: Exception running command: "$AdminApp installInteractive C:/Documents and Settings/ myUserName/Desktop/MyApp/appname.ear"; exception information: com.ibm.bsf.BSFException: error while eval'ing Jacl expression: can't find method "installInteractive" with 3 argument(s) for class "com.ibm.ws.scripting.AdminAppClient"

  The file and path name are incorrectly specified. In this case, since the path included spaces, it was interpreted as multiple parameters by the wsadmin program.

  Enter the path of the .ear file correctly. In this case, by enclosing it in double quotes

  $AdminApp installInteractive "C:\Documents and Settings\myUserName\Desktop\MyApps\appname.ear"

• If the full text of the error is similar to

  WASX7015E: Exception running command: "$AdminApp installInteractive c:\MyApps\appname.ear "; exception information: com.ibm.ws.scripting.ScriptingException: WASX7115E: Cannot read input file "c:\WebSphere\AppServer\bin\MyAppsappname.ear"

  The application path is incorrectly specified. In this case, use UNIX-style "forward-slash" (/) separators in the path.

 

Data definition language (DDL) generated by Application Assembly tool throws SQL error on target platform

If you receive SQL errors in attempting to execute data definition language (DDL) statements generated by the Application Assembly Tool on a different platform... if you are deploying a container-managed persistence (CMP) enterprise bean designed on Windows onto a UNIX operating system server, try the following actions...

• Browse the DDL statements for dependencies on specific user IDs and passwords, and correct as necessary.

• Browse the DDL statements for dependencies on specific server names, and correct as necessary.

• Refer to the message reference of the vendor for causes and suggested actions regarding specific SQL errors. For IBM DB2, you can view the message references online at http://www.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/index.d2w/report .

If you receive the following error after executing a DDL file created on Windows operating system on a UNIX platform, the problem might come from a difference in file formats

SQL0104N An unexpected token "CREATE TABLE AGENT (COMM DOUBLE, PERCENT DOUBLE, P" was found following " ". Expected tokens may include: " ". SQLSTATE=42601

To resolve this problem...

• For UNIX platforms other than Linux, edit the DDL in the vi editor, removing the Ctl-M character at the beginning of each line.

• For Linux systems, regenerate the deployment code for the application EAR file on a Linux platform.

 

Error message ADMA0004E: Validation error in task Specifying the Default Datasource for EJB 1.x Modules returned when installing application using the administrative console or the wsadmin tool

If you see the following error when trying to install an application or wsadmin.sh prompt

AppDeploymentException: [ADMA0014E: Validation failed.

ADMA0004E: Validation error in task Specifying the Default Datasource for EJB 1.x Modules JNDI name is not specified for module beannameBean Jar with URI filename.jar,META-INF/ejb-jar.xml. You have not specified the data source for each CMP bean belonging to this module. Either specify the data source for each CMP beans or specify the default data source for the entire module.]

one possible cause is that in WAS Version 4.0, it was mandatory to have a data source defined for each CMP bean in each JAR. In Version 5, you can specify either a data source for a container-managed persistence (CMP) bean or a default data source for all CMP beans in the JAR file. Thus during installation interaction, such as the installation wizard in the administrative console, the data source fields are optional, but the validation performed at the end of the installation checks to see that at least one data source is specified.

To correct this problem, step through the installation again, and specify either a default data source or a data source for each CMP-type enterprise bean. If you are using wsadmin.sh, either...

• Use the $AdminApp installInteractive filename command to receive prompts for data sources during installation, or to provide them in a response file.

• Specify data sources as an option to the $AdminApp install command. For details on the syntax, see Install applications using wsadmin.sh.

 

Error message No valid target is specified in ObjectName anObject for module module_name from installation

This error can occur in a clustered environment if the target cell, node, server or cluster into which the application is to be installed is incorrectly specified. For example, it can occur if the target is misspelled.

To correct this problem, check the target names against the actual WAS topology and reenter them with corrections.

 

addNode -includeapps option does not appear to upload all applications to the Deployment Manager

This error can occur when some or all applications on the target node are already uploaded to the deployment manager. The addNode program detects which applications are already installed and does not upload them again.

Use the administrative console to browse the deployment manager configuration and see the applications that are already installed.

 

"Timeout!!!" error displays when attempting to install an enterprise application in the administrative console

This error can occur if you attempt to install an enterprise application that has not been deployed.

To correct this problem...

• Open the ear file file_name.ear in the Assembly Toolkit and then click File ->Generate code for deployment.... This action creates a file with a name like Deployed_file_name.ear.

• In the administrative console, install the deployed ear file.

 

During application installation, the call to EJB deploy throws an exception

When you specify that EJB deploy be run during application installation and if installation fails with the error command line too long, the problem is that the deployment command generated during installation exceeds the character limit for a command line on the Windows platform. This problem occurs only on Windows platforms.

To work around this problem, you can reduce the length of the EAR file name, reduce the length of the JAR file name within the EAR file, reduce the class path or other options specified for deployment, or change the %TEMP% location of the Windows system to make its path shorter.

 

While uploading documents, addNode -includeapps fails with an OutOfMemoryError exception

This error can occur when you use addNode -includeapps while you are installing applications with large EAR files. To correct this problem...

• If you are using addNode to add a node from the base server, modify the addNode script to include the following parameter

  -Xmxsize

• If you are adding a node from the administrative console, increase the maximumHeapSize in the JVM settings of the Deployment Manager, then restart the Deployment Manager. See Java virtual machine settings for details.

For example, the addNode.bat file that follows sets a maximum heap size of 512 MB on a Windows platform

"%JAVA_HOME%\bin\java" -Xmx512m %DEBUG% %WAS_TRACE% %CONSOLE_ENCODING% "%CLIENTSOAP%" "%CLIENTSAS%" "-classpath" "%WAS_CLASSPATH%" "-Dws.ext.dirs=%WAS_EXT_DIRS%" %USER_INSTALL_PROP% -Dwas.install.root=%WAS_HOME%" "com.ibm.ws.bootstrap.WSLauncher" "com.ibm.ws.management.tools.NodeFederationUtility" "%CONFIG_ROOT%" "%WAS_CELL%" "%WAS_NODE%" %*

 

See Also

Troubleshooting by component: What is not working?
Troubleshooting code deployment and installation problems

 

---