Application deployment problems


 

+

Search Tips   |   Advanced Search

 

  1. General tips
  2. Installed application using wsadmin. App does not display under Applications | Application Types | WebSphere enterprise apps
  3. Unable to save a deployed app
  4. Failed_saving_bytes_to_wor_ERROR_ error
  5. WASX7015E error running $AdminApp installInteractive or $AdminApp install
  6. Cannot install a CMP or BMP entity bean in an EJB 3.0 module
  7. DDL generated by an assembly tool throws SQL error on target platform
  8. ADMA0004E: Validation error when specifying the default datasource for EJB Modules returned
  9. Cannot load resource WEB-INF/ibm-web-bnd.xmi in archive file
  10. Error message No valid target is specified in ObjectName anObject for module module_name from installation
  11. addNode -includeapps option does not appear to upload all apps to the dmgr
  12. "Timeout!!!" error displays when attempting to install an enterprise application
  13. NameNotFoundException message when deploying an application that contains an EJB module
  14. During application installation, the call to EJB deploy causes an exception
  15. I get compilation errors and EJB deploy fails when installing an EJB JAR file generated for V5.x or earlier
  16. While uploading documents, addNode -includeapps fails with an OutOfMemoryError exception
  17. OutOfMemory exception in the dmgr
  18. After installing the application onto a different machine, the application does not run
  19. A single file replaces all application files during application update

 

General tips

Verify the logical name specified to appear on the console for does not contain invalid characters such as: - / \ : * ? " < > |.

If the application was installed using...

wsadmin $AdminApp install -local

...restart the server or rerun the command without the -local flag.

Refer to available online support

See Troubleshooting help from IBM.

 

App installed using wsadmin. App does not display under Applications | Application Types | WebSphere enterprise apps

  1. Verify that the application subdirectory is located under...

    APP_ROOT/installedApps

  2. Verify application is not displayed when running.... 
    ### list_apps.jacl
###
### Usage:
###
###   wsadmin.sh -username username -password password -f list_apps.jacl
###
###

###
### set up globals
### global AdminControl global AdminConfig global AdminApp


###
### Get the apps
###
puts "----------------------------------------------------"
puts "" set apps [$AdminApp list]
puts "Number of applications: [llength $apps]"
puts ""
puts $apps

  3. The application might be installed but we have not saved the configuration. Reinstall the application using wsadmin and run...

    $AdminConfig save

 

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 platforms, we can either...

 

Failed_saving_bytes_to_wor_ERROR_ error

The file path length of the temporary system file might be exceeded.

Check the TEMP and TMP environment variables for your system.

To resolve...

  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 app.

Otherwise, try rebooting and redeploying or reinstalling the app.

 

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

If the full text of the error is similar to...

WASX7015E: Exception running command: "$AdminApp installInteractive C:/IBM/username/MyApp/myapp.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:\IBM\username\MyApps\myapp.ear"

If the full text of the error is similar to...

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

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

 

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

When installing an EJB 3.0 module that contains a CMP or BMP entity bean, the installation fails.

WAS ND v7.0 does not support installation of apps 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:

  1. Package the CMP or BMP entity beans in EJB 2.1 or earlier modules.
  2. Install the application with the EJB 2.1 or earlier modules.

 

DDL generated by an assembly tool throws SQL error on target platform

If we receive SQL errors in attempting to execute DDL statements generated by an assembly tool on a different platform, for example if we are deploying a CMP enterprise bean designed on Windows onto a UNIX operating system server, try the following actions:

If we receive the following error after executing a DDL file created on the Windows operating system or on operating systems such as AIX or Linux, 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:

 

ADMA0004E: Validation error in task Specifying the Default Datasource for EJB Modules returned

If we see the following error when trying to install an application through the admin console or the wsadmin command prompt...

AppDeploymentException: [ADMA0014E: Validation failed. ADMA0004E: Validation error in task Specifying the Default Datasource for EJB Modules JNDI name is not specified for module beannameBean Jar with URI filename.jar,META-INF/ejb-jar.xml.

we 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 V4.0, it was mandatory to have a data source defined for each CMP bean in each JAR. In V5.0 and later releases, we can specify either a data source for a 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 admin 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 we are using wsadmin, use...

$AdminApp installInteractive filename

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.

 

Cannot load resource WEB-INF/ibm-web-bnd.xmi in archive file

The Web application tmp.war installs on WAS Vs 5.0 and 5.1, but fails on a WAS V6.0 or later server. The application fails to install because the WEB-INF/ibm-web-bnd.xmi file contains xmi tags that the underlying WCCM model no longer recognizes.

The following error messages display:

IWAE0007E Could not load resource "WEB-INF/ibm-web-bnd.xmi" in archive "tmp.war"
[2/24/05 14:53:10:297 CST] 000000bc SystemErr R AppDeploymentException: com.ibm.etools.j2ee.commonarchivecore.exception.ResourceLoadException:
IWAE0007E Could not load resource "WEB-INF/ibm-web-bnd.xmi" in archive "tmp.war"
[2/24/05 14:53:10:297 CST] 000000bc SystemErr R com.ibm.etools.j2ee.commonarchivecore.exception.ResourceLoadException:
IWAE0007E Could not load resource "WEB-INF/ibm-web-bnd.xmi" in archive "tmp.war" !Stack_trace_of_nested_exce! com.ibm.etools.j2ee.exception.WrappedRuntimeException: Exception occurred loading WEB-INF/ibm-web-bnd.xmi !Stack_trace_of_nested_exce!

To work around this problem, remove the tag...

xmi:type=EJBLocalRef

...from ibm-web-bnd.xmi. Removing this tag does not affect the application because the tag was previously used for matching the cross document reference type. The application now works for the WAS V5.1 and later releases.

 

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 apps to the dmgr

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

Use the admin console to browse the dmgr configuration and see the apps that are already installed.

 

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

This error can occur if we attempt to install an enterprise application that has not been deployed. To correct this problem:

 

NameNotFoundException message when deploying an application that contains an EJB module

If we specify that the EJB deployment tool be run during application installation and the installation fails with a NameNotFoundException message, verify 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 the 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, we 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.

 

I get compilation errors and EJB deploy fails when installing an EJB JAR file generated for V5.x or earlier

When installing an old application that uses EJB modules that were built to run on WAS V5.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 V5.x or before but, when deployed to a WAS V6.x product, it is compiled using the V6.x runtime JAR files.

To work around this problem, remove all .java files from the application .ear file. After the Java source files are removed, we 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 we are installing apps 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%" %*

 

OutOfMemory exception in the dmgr

If we receive an OutOfMemory exception when trying to install apps with large EAR files, try increasing the maximum heap size of the dmgr.

Check the options you specified on the JVM of the admin console. Increase the maximumHeapSize in the JVM settings of the dmgr. Then, restart the dmgr, and try installing the application again.

If this change does not correct the problem, see Diagnose problems using IBM Support Assistant tooling.

 

After installing the application onto a different machine, the application does not run

If the application uses application level resources, its application level node information must be correct for the application to run as expected.

When you add application level resources to an application and deploy the application onto a machine, verify the application level node information is correct. Otherwise, when you install the application onto a different machine, it is installed to the wrong location and the application does not run as expected.

You can update the application level node information using an assembly tool. Update the nodeName from deploymentTargets of...

META-INF/ibmconfig/deployment.xml

Ensure that binariesURL from deployedObject of deployment.xml has the correct path.

 

A single file replaces all application files during application update

If we select the Replace or add a single file option of the app 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 we 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.


 

Related tasks

Troubleshooting deployment

 

Related information

Install enterprise application files