WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

The application does not start or starts with errors

What kind of error do you see when you start an application?
If none of these errors match the error you see:

If you do not see a problem that resembles yours, or if the information provided does not solve your problem, see Obtaining help from IBM.

java.lang.ClassNotFoundException: classname Bean_AdderServiceHome_04f0e027Bean

An similar exception occurs when you try to start an undeployed application containing enterprise beans, or containing undeployed enterprise bean modules.

Enterprise JavaBeans modules created in an assembly tool intentionally have incomplete configuration information. Deploying these modules completes the configuration by reading the module's deployment descriptor and completing platform- or installation-dependent settings and adding related classes to the Enterprise JavaBeans JAR file.

To avoid this problem, do the following:
  • Use an assembly tool and administrative console to generate deployment code and install the application or Enterprise JavaBeans module onto a server.
    1. Uninstall the application or Enterprise JavaBeans module in the administrative console.
    2. Configure your assembly tool so the target server is a WebSphere Application Server installation such as WebSphere Application Server v6.0. If you do not have access to the target server, you can specify a false location such as c:\temp. Specifying a false location enables you to assemble and generate deployment code for the enterprise bean.
    3. In the Project Explorer view of an assembly tool, right-click the enterprise bean (Enterprise JavaBeans) in the undeployed .ear file containing the Enterprise JavaBeans module or the standalone undeployed Enterprise JavaBeans JAR file, and click Deploy. If your assembly tool can access the WebSphere Application Server target server, deployment code is generated for the Enterprise JavaBeans and the assembly tool attempts to install the application or module onto the target server. If your assembly tool cannot access the WebSphere Application Server target server or the installation fails, use the deployment code that is generated for the next step.
    4. Use the administrative console to install the deployed version created by the assembly tool.
  • If you are using the wsadmin $AdminApp install command, uninstall it and then reinstall using the -EJBDeploy option. Follow the install command with the $AdminConfig save command.

ConnectionFac E J2CA0102E: Invalid EJB component: Cannot use an EJB module with version 1.1 using The Relational Resource Adapter

This error occurs when an enterprise bean developed to the Enterprise JavaBeans 1.1 specification is deployed with a WebSphere Application Server V5 J2C-compliant data source, which is the default data source. By default, persistent enterprise beans created under WebSphere Application Server V4.0's using the Application Assembly Tool fulfill the Enterprise JavaBeans 1.1 specification. To run on WebSphere Application Server V6, these enterprise beans must be associated with a WebSphere Application Server V4.0-type data source.

Either modify the mapping in the application of enterprise beans to associate 1.x container managed persistence (CMP) beans to associate them with a V4.0 data source or delete the existing data source and create a V4.0 data source with the same name.

To modify the mapping in the application of enterprise beans, in the WebSphere Application Server administrative console, select the properties for the problem application and use map resource references to resources or Map data sources for all 1.x CMP beans to switch the data source the enterprise bean uses. Save the configuration and restart the application.

To delete the existing data source and create a V4.0 data source with the same name:
  1. In the administrative console, click Resources>Manage JDBC Providers>JDBC_provider_name>Data sources.
  2. Delete the data source associated with the Enterprise JavaBeans 1.1 module.
  3. Click Resources>Manage JDBC Providers>JDBC_provider_name>Data sources (Version 4).
  4. Create the data source for the Enterprise JavaBeans 1.1 module.
  5. Save the configuration and restart the application.

NMSV0605E: "A Reference object looked up from the context..." error when starting an application

If the full text of the error is similar to:

[7/17/02 15:20:52:093 CDT] 5ae5a5e2 UrlContextHel W NMSV0605E: A Reference object looked up from the context
     "java:" with the name "comp/PM/WebSphereCMPConnectionFactory" was sent to the JNDI Naming Manager
     and an exception resulted. Reference data follows:
     Reference Factory Class Name: com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory
     Reference Factory Class Location URLs:
     Reference Class Name: java.lang.Object
     Type: JndiLookupInfo
     Content: JndiLookupInfo: ; jndiName="eis/jdbc/MyDatasource_CMP"; providerURL=""; initialContextFactory="" 

then the problem might be that the data source intended to support a CMP enterprise bean is not correctly associated with the enterprise bean.

To resolve this problem:
  1. Select the Use this Data Source in container managed persistence (CMP) check box in the data source "General Properties" panel of the administrative console.
  2. Verify that the JNDI Name given in administrative console under Resources-> Manage JDBC Provider > DataSource > JNDI Name for DataSource matches the JNDI Name given for CMP or BMP Resource Bindings at the time of Assembling the application in an assembly tool, or
  3. Check the JNDI Name for CMP or BMP resource bindings specified in the code by J2EE Application Developer. Open the deployed .ear folder in an assembly tool, and look for the JNDI Name for your entity beans under CMP or BMP resource bindings. Verify that the names match.
[Version 6.0.1 and later]

Deployed application that uses Java Native Interface (JNI) code does not start

An application that uses JNI code might not start after deployment. The JNI allows Java code running in a virtual machine to operate with applications and libraries written in other languages, such as C, C++, and assembly. If your J2EE application uses JNI in a 32-bit environment, you must recompile your code in a 64-bit environment. The JNI calls might be different after the compilation because JNI specifications can change from version to version. WebSphere Application Server now supports 64-bit environments.

For a "pure" Java application that does not use JNI code, 32-bit to 64-bit compatibility is not an issue.




Related tasks
Troubleshooting by task
Troubleshooting by component

Reference topic    

Terms of Use | Feedback

Last updated: Mar 17, 2005 4:28:29 AM CST
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rtrb_appstart.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)