Last updated on SEPTEMBER 27, 2016
Applies to:Oracle Discoverer - Version 10.1.2.55.26 to 126.96.36.199.0
Information in this document applies to any platform.
*** Checked for relevance on 12-May-2016 ***
Discoverer Plus 10.1.2 and 11g connections that occur internally (inside the firewall) are working.
If a Discoverer Plus connection attempt is made from outside the firewall, it fails with error:
Attempt 1. RMI protocol over JRMP transport: Connection refused to host <hostname>; nested exception is:
java.net.ConnectException: Connection refused: connect
According to Oracle Business Intelligence Discoverer Configuration Guide
- 14.6.3 About Discoverer Plus security and communication protocols
The Discoverer Plus communication protocol is set to default.
The behavior is unexpected based on the Oracle Discoverer Configuration Guide.
Here it describes Oracle Discoverer communication protocol behavior when set to "Default:"
|Using Application Server Control, you can specify which communication protocol the
Discoverer Plus applet (i.e. the Discoverer client) and the Discoverer servlet (i.e. on the
Discoverer middle tier) use to communicate. The three communication protocol
Specify this option if you want the Discoverer Plus applet to attempt to use JRMP
and if this fails, to use HTTP or HTTPS (depending on the URL) to communicate
with the Discoverer servlet.
However, Discoverer Plus does not automatically switch over to HTTP after JRMP connection has failed. Hence, users outside firewall can not connect, and receive the error listed above.
Oracle Application Server Enterprise Manager Console (ASC) is used to set Discoverer Plus Communication Protocol to 'Default'.
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