The task container application fails to start

Startup bean named ejb/htm/TaskContainerStartUpBean forced the application to stop.

Symptom

The following errors are written to the SystemOut.log file:
WSVR0037I: Starting EJB jar: taskejb.jar
NMSV0605W: A Reference object looked up from the context "java:" 
with the name "comp/env/scheduler/DefaultUserCalendarHome" 
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="com/ibm/websphere/scheduler/calendar/DefaultUserCalendarHome"; 
providerURL=""; initialContextFactory=""
:
StartBeanInfo E STUP0005E: Startup bean named ejb/htm/TaskContainerStartUpBean 
forced application to stop.
ApplicationMg W WSVR0101W: An error occurred starting, TaskContainer_utxtlb10Node01_server1
ApplicationMg A WSVR0217I: Stopping application: TaskContainer_utxtlb10Node01_server1
EJBContainerI I WSVR0041I: Stopping EJB jar: taskejb.jar

Reason

You get this error if the SchedulerCalendars application is not available when the TaskContainer application starts.

Resolution

Either install the SchedulerCalendars application manually, or if it is already installed, add a new target mapping for it.

In a default profile, the SchedulerCalendars application is available automatically as a WebSphere system application. However, in a custom profile it is not available automatically.

The bpeconfig.jacl script tries to install the SchedulerCalendars application, but this is not always possible.

If you use the administrative console install wizard to configure Business Process Choreographer in an ND environment, you must install the SchedulerCalendars application manually.


(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)