Errors or problems deploying, installing, or promoting applications

What kind of problem are you having?

Check the following first:

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.

I installed my application using the wsadmin tool, 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 install_dir/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 the wsadmin tool. Run the $AdminConfigsave command in tje wsadmin tool before exiting.

I get a java.lang.RuntimeException: Failed_saving_bytes_to_wor_ERROR_ error in the assembly tool, administrative console or the wsadmin tool.

If you see this error when attempting to generate deployed code in the Application Assembly Tool (AAT), installing an application or module in the administrative console, or using the wsadmin tool 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 WebSphere Application Server 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:

Data definition language (DDL) generated by Application Assembly Tool (AAT) 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 (AAT) on a different platform, for example if you are deploying a container-managed persistence (CMP) enterprise bean designed on Windows onto a UNIX operating system server, try the following actions:

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:

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 through the administrative console or the wsadmin command 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 WebSphere Application Server Version 4.0, it was mandatory to have a data source defined for each CMP bean in each JAR. In V5, 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 the wsadmin tool, either:

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 WebSphere Application Server 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:

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:

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%" %*

Application installation fails with MaxLengthExceededException error if application is more than 250 MB

By default, you cannot install applications larger than 250 MB onto a server in a WebSphere Application Server product. The application size restriction was imposed to avoid security threats on the administrative console. An application installation fails with a MaxLengthExceededException error if the application is more than 250 MB. A message such as the following is displayed:

Problem while reading request: 
   The maximum length of 262144000 bytes has been exceeded

To enable installation of an application larger than 250 MB, do the following:

  1. Open an editor on the web.xml file in the directory: 

    install_root/config/cells/cell/applications/adminconsole.ear
/deployments/adminconsole/adminconsole.war/WEB-INF

  2. Add an init parameter to the action servlet.

    1. Search for the action servlet in web.xml, which has tagging such as the following: 

      <servlet id="Servlet_1037062312313">
<servet-name>action</servlet-name>
<servlet-class>org.apache.struts.tiles.ActionComponentServlet</servlet-class>

    2. Add the init parameter entry maxFileSize and set it to a value that enables installation of your large application. The tagging resembles-- 

      <init-param id="InitParam_1037062312313">
<param-name>maxFileSize</param-name>
<param-value>500M</param-value>
</init-param>

      The value of maxFileSize can be represented in bytes by not appending any characters to the end. To represent kilobytes, append K after the number. For megabytes, append M. For gigabytes, append G.

    3. Save the file.

  3. Restart the server.
Related tasks
Troubleshooting by task: What are you trying to do?
Troubleshooting by component: What is not working?
Related reference
Troubleshooting code deployment and installation problems