Description:
Description: 
============
When attempting to start an TIBCO IntegrationManager(IM) process having a time channel throws “Java Null Pointer Exception”.

10/07/2010 12:06:10 TIBIM.5.0.2V29-HOTFIX07.IncrementalUpdate.TEST_INCREMENTAL_TOCADOPS_ENGINE Error [IM_CORE] AEIM-200000
java.lang.NullPointerException
    at com.tibco.im.fw.RepoMunger.buildJobCreator(RepoMunger.java:1234)
    at com.tibco.im.fw.RepoMunger.addJobCreators(RepoMunger.java:1048)
    at com.tibco.im.fw.RepoMunger.munge(RepoMunger.java:286)
    at com.tibco.im.server.cfg.RepoConfigService.setConfig(RepoConfigService.java:461)
    at com.tibco.im.server.srv.Service.handleConfigEvent(Service.java:613)
    at com.tibco.im.server.cfg.ConfigService.getConfigParams(ConfigService.java:83)
    at com.tibco.im.server.srv.Service.init(Service.java:114)
    at com.tibco.im.server.cfg.ConfigService.init(ConfigService.java:75)
    at com.tibco.im.server.srv.Service.init(Service.java:84)
    at com.tibco.im.server.cfg.RepoConfigService.<init>(RepoConfigService.java:103)
    at com.tibco.im.IMStandAloneServer.<init>(IMStandAloneServer.java:94)
    at com.tibco.im.IMSe.<init>(IMSe.java:227)
    at com.tibco.im.IMSe.main(IMSe.java:195)

Symptoms:
Symptoms:
========
“Java Null Pointer Exception” in the RepoManager when attempting to start an IM process. This happens both when starting as a stand-alone process and as a service. The following is the error thrown in IM logs or console.

[IM_CORE] AEIM-200000 java.lang.NullPointerException at com.tibco.im.fw.RepoMunger.buildJobCreator(RepoMunger.java:1234).
Cause:
Cause:
=====  
Time channels in IM 4.x do not require the setting of the Start property. It does default to "now" if you are running the same project in IM 5.0.2. Tt throws null-pointer exception in such cases.