RMI Connectivity Problems Between Servers Separated by Firewall When JMX is Enabled on Remote JVM (Doc ID 1516030.1)

Last updated on DECEMBER 22, 2016

Applies to:

Oracle ATG Web Commerce Merchandising - Version 2006.3 and later
Oracle ATG Web Commerce - Version 2006.3 and later
Information in this document applies to any platform.

Symptoms

Enabling JMX for remote monitoring of Oracle ATG instances running behind a firewall causes the Publishing or BCC server to fail to connect to the instances due to firewall connection problems.

The Publishing server connects to the remote instances over a random port that is determined at JVM startup instead of using the RMI port configured by the Oracle ATG server instance (in the rmiPort property of the /atg/dynamo/Configuration component).

This document deals only with RMI connectivity problems when JMX is enabled in the JVM. Other types of RMI connectivity issues are described in <Document 1447769.1>.

 

Changes

JMX monitoring is enabled via the com.sun.management.jmxremote or com.sun.management.jmxremote.port JVM arguments. JMX is documented in detail in "Monitoring and Management Using JMX Technology":

http://docs.oracle.com/javase/6/docs/technotes/guides/management/agent.html

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