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:

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.

To avoid this problem, do one of the following actions:

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 EJB 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 fulfill the EJB 1.1 specification. To run on WebSphere Application Server V5, 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 EJB 1.1 module.
  3. Click Resources>Manage JDBC Providers>JDBC_provider_name>Data sources (Version 4).
  4. Create the data source for the EJB 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's "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 the , 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 the , and look for the JNDI Name for your entity beans under CMP or BMP resource bindings. Verify that the names match.


Related tasks
Troubleshooting by task: What are you trying to do?



Searchable topic ID:   rtrb_appstart
Last updated: Jun 21, 2007 4:12:58 PM CDT    WebSphere Application Server Express, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.exp.doc/info/exp/ae/rtrb_appstart.html

Library | Support | Terms of Use | Feedback