|
Problem(Abstract) |
ClassNotFoundException displayed when starting an
application that is not yet completely deployed. |
|
Symptom |
This problem can occur with different products that are
installed and started automatically by 3rd party tools. One such case was
with TFIM product where they installed their runtime component/application
and it was started automatically using their script. The TFIM script
asynchronously kicks off the start of the application prematurely while
the application being deployed is not completely installed. The problem
does not occur if the script waited a minute before starting the
application.
In the above case the following errors are seen:
[1/10/06 11:03:31:415 EST] 0000003c ServletWrappe E SRVE0026E:
[Servlet
Error]-[com.tivoli.am.fim.rte.config.servlet.ITFIMRuntimeServlet]:
java.lang.ClassNotFoundException:
com.tivoli.am.fim.rte.config.servlet.ITFIMRuntimeServlet
at
com.ibm.ws.classloader.CompoundClassLoader.findClass(CompoundClassLoader
.java:517)
at
com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader
.java:414)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
Other errors also seen are:
[1/10/06 9:35:55:313 EST] 00000042 ComponentImpl A WSVR0400W: Unable
to register the ITFIMRuntime MBean
com.ibm.websphere.management.exception.AdminException: ADMN0005E: The
service is unable to activate MBean: type J2EEApplication, collaborator
com.ibm.ws.runtime.component.collaborator.J2EEApplication@1db2f81,
configuration ID
cells/sthep61Cell01/applications/ITFIMRuntime.ear/deployments/ITFIMRunti
me/deployment.xml#ApplicationDeployment_1136903732065, descriptor null.
at
com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.ja
va:632) |
|
Cause |
Premature start of the application before it is completely
finished with the installation. This is purely a timing issue between
deploy of the application and starting of the application. |
|
Resolving the
problem |
Do not start the application until it has been completely
installed. |
|