When an application is not starting or starting with errors, the problem could be from one of various sources.
If you do not see a problem that resembles yours, or if the information provided does not solve your problem, see Troubleshooting help from IBM.
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.
For information on using an assembly tool, refer to Assembling applications.
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 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.
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:
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.
If you are using double-byte characters in the profile name, you receive a parsing error when running an application that uses the JavaServer Faces™ (JSF) configuration. The problem is related to the JSF configuration that is part of the jsf-ibm.jar, which is included when building JSF applications in Rational® Application Developer. The configuration files are referencing entities from inside the main faces-config.xml file.
Avoid using double-byte characters when you create a profile.
The following exception can occur during the runtime of an application using Java Server Faces (JSF) running on WebSphere Application Server 6.0.2 on Red Hat Enterprise Linux 4.0 for 64-bit Linux on zSeries. The message regarding the JSF component not found is application specific; however, the contents of the stacktrace is the same.
0000004a ServletWrappe E SRVE0068E: Could not invoke the service() method on servlet /TestScores.jsp. Exception thrown : javax.servlet.ServletException: Component Not Found for identifier: text16'. at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:638) at com.ibm._jsp._TestScores._jspService(_TestScores.java:99) at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1282) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:673) at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117) at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:178) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:265) at com.ibm.faces.context.MultipartExternalContextImpl.dispatch(MultipartExternalContextImpl.java:320) at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:254) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:201) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1282) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:673) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2905) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:220) at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:204) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1829) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:84) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:469) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:408) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:101) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952) at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1455)
export JITC_COMPILEOPT=NQCOMMONING_PUT{javax/faces/component/UIComponentBase}{getFacetsAndChildren}
If an application is updated while it is running, WebSphere® Application Server automatically stops the application or only its changed components, updates the application logic, and restarts the stopped application or its components. For more information on the restarting of updated applications, refer to Fine-grained recycle behavior in IBM WebSphere Developer Technical Journal: System management for WebSphere Application Server V6 -- Part 5 Flexible options for updating deployed applications.
A Page Not Found, Array Index Out of Bounds, or other error might occur during restarting.
To minimize the occurrence of such errors, update applications in a test environment before updating the applications in a production environment. Do not put changes directly into a production environment.