Troubleshoot: application deployment issues

Application does not display

Application installed using the wsadmin tool, but the application does not display under Applications > Application Types > WebSphere Enterprise Applications.

The application might be installed but you have not saved the configuration:
1. Verify that the application subdirectory is located under the app_server_root/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 $AdminConfig save command in the wsadmin tool before exiting.


Unable to save a deployed application

If you are unable to save a deployed application, the problem might be that too many files are opened, exceeding the limit of the operating system.

On the SuSE9 or other Linux platform, you can either increase the number of files that can be opened to resolve the problem or you can modify the application to close files with disciplines. To increase the number of files that you can open at the same time, run the following command in the shell before invoking the process that needs to open a number of files:

ulimit -n number_of_files

Only root has authority to adjust the maximum number of files for each process. Complete the following steps to modify the application to close files with disciplines:

1. After you open a file and complete your work, call the close method of the file to release the file handle back to the operating system.
2. Using the java.io.FileInputStream and the FileOutputStream classes as examples, you can invoke their close method to release any system resources that are associated with the stream.
 

Cannot install a CMP or BMP entity bean in an EJB 3.0 module

When installing an EJB 3.0 module that contains a container-managed persistence (CMP) or bean-managed persistence (BMP) entity bean, the installation fails.

The product does not support installation of applications that have a CMP or BMP entity bean packaged in an EJB 3.0 module. You must package CMP or BMP entity beans in an EJB 2.1 or earlier module.

To resolve this problem:
Package the CMP or BMP entity beans in EJB 2.1 or earlier modules.
Try installing your application with the EJB 2.1 or earlier modules.
 

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.

NameNotFoundException message when deploying an application that contains an EJB module

If you specify that the EJB deployment tool be run during application installation and the installation fails with a NameNotFoundException message, ensure that the input JAR or EAR file does not contain source files. If there are source files in the input JAR or EAR file, the EJB deployment tools runs a rebuild before generating the deployment code.

To work around this problem, either remove the source files or include all dependent classes and resource files on the class path. Otherwise, the source files or the lack of access to dependent classes and resource files might cause problems during rebuilding of your application on the server.


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

When you specify that the EJB deployment tool 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.

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.


Compilation errors and EJB deploy fails when installing an EJB JAR file generated for Version 5.x or earlier

When installing an old application that uses EJB modules that were built to run on WebSphere Application Server Version 5.x or earlier, compilation errors result and EJB deploy fails. The EJB JAR file contains Java source for the old generated code. The old Java source was generated for Version 5.x or before but, when deployed to a WebSphere Application Server Version 6.x or later product, it is compiled using the Version 6.0 or later runtime JAR files.

To work around this problem, remove all .java files from the application EAR file. After the Java source files are removed, you can deploy the application onto a server successfully.


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 Java virtual machine settings of the deployment manager, then restart the deployment manager.

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

 

OutOfMemory exception in the deployment manager

If you receive an OutOfMemory exception when trying to install applications with large EAR files, try increasing the maximum heap size of the deployment manager.

Check the options you specified on the Java virtual machine page of the administrative console. Increase the maximumHeapSize in the Java virtual machine settings of the deployment manager.

Then, restart the deployment manager, and try installing the application again.


A single file replaces all application files during application update

If you select the Replace or add a single file option of the application update wizard and the currently deployed application consists of several files, specify the full path name of the file to be replaced or added for Specify the path beginning with the installed application archive file to the file to be replaced or added.

A full path name usually has the structure directory_path/file_name and resembles the following:

PriceChangeSession.jar/priceChangeSession/priceChangeSessionBean.class

Do not specify less than the full path name for Specify the path beginning with the installed application archive file to the file to be replaced or added. For example, do not specify only a directory path:

PriceChangeSession.jar/priceChangeSession

If you specify less than a full path name, all files in the directory of the currently deployed application might be replaced by the single new file that was specified under Specify the path to the file.