You might encounter problems when deploying, installing, or promoting applications. This topic suggests ways to resolve the problems.
What kind of problem are you having?
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.
Refer to available online support including hints and tips, technotes, and fixes. If the problem has not been identified, see Troubleshooting help from IBM.
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.
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:
If you see this error when attempting to generate deployed code in an assembly tool, 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.
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 EJB deployment tool.
This problem has two possible causes:
WASX7015E: Exception running command: "$AdminApp installInteractive C:/Documents and Settings/ myUserName/Desktop/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"
WASX7015E: Exception running command: "$AdminApp installInteractive Documents and Settings/ myUserName/Desktop/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:\Documents and Settings\myUserName\Desktop\MyApps\myapp.ear"
$AdminApp installInteractive "Documents and Settings/myUserName/Desktop/MyApps/myapp.ear"
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"
WASX7015E: Exception running command: "$AdminApp installInteractive MyApps\myapp.ear "; exception information: com.ibm.ws.scripting.ScriptingException: WASX7115E: Cannot read input file "WebSphere\AppServer\bin\MyAppsmyapp.ear"The application path is incorrectly specified. In this case, you must use "forward-slash" (/) separators in the path.
SQL0104N An unexpected token "CREATE TABLE AGENT (COMM DOUBLE, PERCENT DOUBLE, P" was found following " ". Expected tokens may include: " ". SQLSTATE=42601
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. 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 versions 5.0 and later releases, 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, 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 Installing applications with the wsadmin tool.
The Web application tmp.war installs on WebSphere Application Server versions 5.0 and 5.1, but fails on a WebSphere® Application Server version 6 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 xmi:type=EJBLocalRef tag from the ibm-web-bnd.xmi file. 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 WebSphere Application Server v5.1, v6.0, and later releases.
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.
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.
This error can occur if you attempt to install an enterprise application that has not been deployed.
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.
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.
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 product, it is compiled using the Version 6.x run-time 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.
-Xmxsize
See addNode command and Java virtual machine settings for details.
"%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%" %*
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.