Unable To Connect To Discoverer Plus on Second Managed Server (Doc ID 1382317.1)

Last updated on SEPTEMBER 27, 2016

Applies to:

Oracle Discoverer - Version: 11.1.1.2.0 and later   [Release: 11g and later ]
Information in this document applies to any platform.

Symptoms

After expanding a cluster to create a second WLS_DISCO Managed Server, users are unable to connect to Discoverer Plus on the new Managed Server.

Connection Error:

Unable to connect to the Discoverer server:

Attempt 1. RMI protocol over JRMP transport: Incorrect response from servlet
at https://server.domain:port/discoverer/plus.

Attempt 2. RMI protocol over http transport : No response from Web Server
at: http://server.domain.

Attempt 3. RMI protocol over https transport : Incorrect response from servlet
at https://server.domain:port/discoverer/plus.

Java Console:

SessionConnectionExceptionSessionConnectionExceptionSessionConnectionExceptionSessionConnectionException:

Attempt 1. RMI protocol over JRMP transport: Incorrect response from servlet at https://server.domain:port/discoverer/plus.

Attempt 2. RMI protocol over http transport : No response from Web Server at: http://server.domain.

Attempt 3. RMI protocol over https transport : Incorrect response from servlet at https://server.domain:port/discoverer/plus.

Hint: An administrator can further diagnose connection problems by running the "checkdiscoverer" script under <ORACLE_INSTANCE>/Discoverer/<DISCOVERER_COMPONENT_NAME>/util..
at oracle.disco.model.corbaserver.connection.ConnectionManager._createSession(Unknown Source)
at oracle.disco.model.corbaserver.connection.ConnectionManager.establishConnection(Unknown Source)
at oracle.disco.model.corbaserver.ServerImpl.init(Unknown Source)
at oracle.disco.model.corbaserver.execengine.SessionControllerImpl._appServerConnect(Unknown Source)
at oracle.disco.model.corbaserver.execengine.SessionControllerImpl.<init>(Unknown Source)
at oracle.disco.model.corbaserver.ModelFactoryImpl.appServerConnect(Unknown Source)
at oracle.disco.model.corbaserver.ModelFactoryImpl.appServerConnect(Unknown Source)
at oracle.disco.worker.MiscellaneousWorker.runDiscoWorker(Unknown Source)
at oracle.disco.worker.DiscoWorker.runWorker(Unknown Source)
at oracle.bali.ewt.worker.AbstractWorker.run(Unknown Source)
at oracle.bali.ewt.worker.AbstractWorkerQueue._runWorker(Unknown Source)
at oracle.bali.ewt.worker.AbstractWorkerQueue.access$100(Unknown Source)
at oracle.bali.ewt.worker.AbstractWorkerQueue$WorkerContext._run(Unknown Source)
at oracle.bali.ewt.worker.AbstractWorkerQueue$WorkerContext._runMaybeBlocked(Unknown Source)
at oracle.bali.ewt.worker.AbstractWorkerQueue$WorkerContext.run(Unknown Source)
at oracle.bali.ewt.worker.ThreadWorkerQueue$TaskAdapter.runTask(Unknown Source)
at oracle.bali.share.thread.TaskScheduler.runTask(Unknown Source)
at oracle.bali.share.thread.TaskScheduler.processTask(Unknown Source)
at oracle.bali.share.thread.TaskScheduler$TaskQueue.run(Unknown Source)
at oracle.bali.share.thread.Timer.doRun(Unknown Source)
at oracle.bali.share.thread.Timer.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Changes

A second WLS_DISCO Managed Server was created by expanding the cluster.

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