Java Managers Do Not Shutdown Cleanly at the End of Custom Workshift
(Doc ID 1331639.1)
Last updated on JANUARY 16, 2024
Applies to:
Oracle Application Object Library - Version 12.1.3 to 12.1.3 [Release 12.1]Information in this document applies to any platform.
Symptoms
=== ODM Issue Clarification ===
Java managers don't work with custom workshift. At the end of workshift, the target process is 0 but Actual is 1 and the process exists at O/S level. This results in concurrent managers not shutting down cleanly when adcmctl.sh is executed. The logfile for java manager associated with custom workshift shows the following error:
UNEXPECTED:[SVC-GSM-WFWSSVC-2028201 :
oracle.apps.fnd.cp.gsc.Processor.run()]:java.lang.NullPointerException
at
oracle.apps.fnd.cp.gsc.SvcComponentContainer.refresh(SvcComponentContainer.ja
va:1180)
at
oracle.apps.fnd.cp.gsm.GSMSvcComponentContainer.refresh(GSMSvcComponentContai
ner.java:346)
at
oracle.apps.fnd.cp.gsc.SvcComponentContainer.handleEvent(SvcComponentContaine
r.java:2055)
at
oracle.apps.fnd.cp.gsm.GSMSvcComponentContainerStateMachine.processEvent(GSMS
vcComponentContainerStateMachine.java:343)
at
oracle.apps.fnd.cp.gsc.StateMachine.handleEvent(StateMachine.java:193)
at
oracle.apps.fnd.cp.gsm.GSMQueueProcessor.process(GSMQueueProcessor.java:151)
at oracle.apps.fnd.cp.gsc.Processor.run(Processor.java:283)
at java.lang.Thread.run(Thread.java:619)
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |