java.net.ConnectException: Connection refused Errors When Using RMI for ACC or BCC Through Firewall
(Doc ID 1447769.1)
Last updated on DECEMBER 22, 2016
Applies to:Oracle ATG Web Commerce - Version 2006.3 and later
Information in this document applies to any platform.
The following error may be reported:
The problem can occur when the Content Administration (CA) BCC server is connecting to a remote agent instance or when the ACC client is connecting to an Oracle ATG server behind a firewall.
If the host IP or hostname in the exception is not correct (i.e. it is a name or IP on an internal network), refer to Document 1037986.1 "Fix CA server RMI connection problem to remote agent" for further information.
If JMX was recently enabled on the RMI server, refer to Document 1516030.1 "RMI Connectivity Problems Between Servers Separated by Firewall When JMX is Enabled on Remote JVM" for further information.
This document discusses a problem where the RMI endpoint port on the Oracle ATG server changes dynamically each time the server is restarted. This prevents the communication between the RMI server and RMI client from working through the firewall. The table below details which components are RMI client and RMI server.
|RMI Client||RMI Server|
|ACC||Server instance that the ACC is connecting to|
Server running the PublishingAgent module
PublishingWebAgent running on remote web server
For versions of the PublishingWebAgent prior to 10.0, refer to Document 1503152.1 "Content Administration BCC Server Fails to Connect To PublishingWebAgent Behind Firewall" for additional information.
A firewall is configured between the RMI client and RMI server with a static list of open ports for well known port numbers (e.g. RMI and application server HTTP listen port) but does not allow communication on dynamic listen ports.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!