java.lang.ClassNotFoundException Seen In OTM Logs after Migrating to OTM 6.2 (Doc ID 1322753.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Operational Planning - Version: 6.2.1 and later   [Release: 6.2 and later ]
Information in this document applies to any platform.

Symptoms

When viewing the logs after upgrading to 6.2, the following errors are seen on startup in the exception logs:

ERROR
-----------------------
java.lang.ClassNotFoundException:
gtm.server.workflow.lifetime.party.GtmPartyRegistrationCreated
java.lang.ClassNotFoundException:
gtm.server.workflow.lifetime.party.GtmPartyModStatusChange
java.lang.ClassNotFoundException:
gtm.server.workflow.lifetime.party.GtmPartyModRemoved
java.lang.ClassNotFoundException:
gtm.server.workflow.lifetime.party.GtmPartyModAnyChange
java.lang.ClassNotFoundException:
glog.server.agent.business.order.CheckGlobalClassification
java.lang.ClassNotFoundException:
gtm.server.workflow.lifetime.party.GtmPartyCreated
java.lang.ClassNotFoundException:
gtm.server.workflow.lifetime.party.GtmPartyRegistrationModAnyChange
java.lang.ClassNotFoundException:
gtm.server.workflow.lifetime.party.GtmPartyRegistrationModRemoved
java.lang.ClassNotFoundException:
gtm.server.workflow.lifetime.party.GtmPartyRegistrationModStatusChange
java.lang.ClassNotFoundException:
gtm.server.workflow.lifetime.party.GtmPartyActionTopic
java.lang.ClassNotFoundException:
gtm.server.workflow.lifetime.party.GtmPartyRegistrationActionTopic
java.lang.ClassNotFoundException:
glog.server.agent.utility.CheckDeniedParties
java.lang.ClassNotFoundException:
glog.server.agent.business.order.CheckEmbargoedCountry
java.lang.ClassNotFoundException:
glog.server.agent.business.order.CheckExportBan
java.lang.ClassNotFoundException:
glog.server.agent.business.order.CheckExportLicense
java.lang.ClassNotFoundException:
glog.server.agent.business.shipment.SendAesTransmission


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Restart OTM.
2. Monitor the exception logs on the app server and note the errors.

As a note, these errors can be ignored. This does not affect functionality of the application. The fix for this bug will be a script to remove the reference to the classes so the errors will no longer show in the logs.



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms