Process's On DocFactory Server Are Not Coming Up
(Doc ID 2732216.1)
Last updated on DECEMBER 08, 2023
Applies to:
Oracle Documaker - Version 12.6.1 and laterInformation in this document applies to any platform.
Symptoms
After changed the service account password, the Docfactoy Processes will not come up. Only the Supervisor is running.
Found the errors below:
2020-11-17 19:53:32,721- INFO-[Thread-0]: Initialization Completed.
2020-11-17 19:53:32,722- INFO-[Thread-0]: Started Configuring Environemnt
2020-11-17 19:53:32,736- INFO-[Thread-0]: Configuring: JNDI for Factory Assembly Line Database.
2020-11-17 19:53:33,380- INFO-[Thread-0]: Configuring: JNDI for Factory Assembly Line Database Completed
2020-11-17 19:53:33,380- INFO-[Thread-0]: Configuring: JNDI for Factory Administrator Database.
2020-11-17 19:53:33,426- INFO-[Thread-0]: Configuring: JNDI for Factory Administrator Database Completed.
2020-11-17 19:53:34,317- INFO-[Thread-0]: Testing : Database connection
2020-11-17 19:53:34,333- INFO-[Thread-0]: Database Connected.
2020-11-17 19:53:34,333- INFO-[Thread-0]: Testing : JMS Queues.
2020-11-17 19:53:37,449-ERROR-[Thread-0]: Problem while creating queue jms.al1.assemblerreq
2020-11-17 19:53:37,449-ERROR-[Thread-0]: javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: User failed to be authenticated.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:42)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:682)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at oracle.documaker.processmonitor.dbqueuetest.StartupDBQueueTest.checkQueue(StartupDBQueueTest.java:352)
at oracle.documaker.processmonitor.dbqueuetest.StartupDBQueueTest.isQueueAvailable(StartupDBQueueTest.java:318)
at oracle.documaker.processmonitor.ProcessMonitor.main(ProcessMonitor.java:799)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at oracle.documaker.process.Startup.main(Startup.java:211)
Caused by: java.lang.SecurityException: User failed to be authenticated.
at weblogic.utils.StackTraceDisabled.unknownMethod()
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 |
Cause |
Solution |