OBIEE 11g: Error: "javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception" on Install (Doc ID 1467590.1)

Last updated on FEBRUARY 08, 2017

Applies to:

Business Intelligence Server Enterprise Edition - Version 11.1.1.6.0 and later
Business Intelligence Suite Enterprise Edition - Version 11.1.1.6.0 and later
Information in this document applies to any platform.
***Checked for relevance on 22-Nov-2013***

Symptoms

You are performing a simple install of OBIEE 11.1.1.6.0 on Linux 64-bit server.  The step to set up BI Publisher Security fails.  When you review the install<date_time stamp>.out file, you see the following error:

updateBIPJMSSecurity: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
updateBIPJMSSecurity:     java.net.ConnectException: Connection refused; No available router to destination]
updateBIPJMSSecurity:     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
updateBIPJMSSecurity:     at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)
updateBIPJMSSecurity:     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
updateBIPJMSSecurity:     at weblogic.jndi.Environment.getContext(Environment.java:315)
updateBIPJMSSecurity:     at weblogic.jndi.Environment.getContext(Environment.java:285)
updateBIPJMSSecurity:     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
updateBIPJMSSecurity:     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
updateBIPJMSSecurity:     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
updateBIPJMSSecurity:     at javax.naming.InitialContext.init(InitialContext.java:223)
updateBIPJMSSecurity:     at javax.naming.InitialContext.<init>(InitialContext.java:197)

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