Configuring MQ For Documaker 12.5
(Doc ID 2254524.1)
Last updated on FEBRUARY 22, 2019
Applies to:
Oracle Documaker - Version 12.5 and laterInformation in this document applies to any platform.
Symptoms
On : 12.5 version, Enterprise Edition
Trying to configure MQ for Documaker 12.5
ERROR
-----------------------
2016-11-02 17:43:31,916-ERROR-[Thread-0]: Problem while creating queue DCM.FC.ASSEMBLER_REQ
2016-11-02 17:43:31,916-ERROR-[Thread-0]: javax.naming.CommunicationException. Root exception is java.net.ConnectException: t3://<servername>.azl.pvt:11001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:143)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
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(NamingManager.java:672)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:250)
at javax.naming.InitialContext.init(InitialContext.java:226)
at javax.naming.InitialContext.(InitialContext.java:202)
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.NativeMeth
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot process transactions.
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 |