random jmx communication port

i have a setup with 2 node agents and 1 DAS behind a firewall.

from what i understand, in order for the node agents to communicate with the DAS, a communication channel is created on a random port via JMX.

the problem here is with the random port having to operate over a firewall. Is there any way to assign a fixed port for JMX communication?

[363 byte] By [kahyonga] at [2007-11-27 10:22:43]
# 1

I have the same issue. My client has disabled all ports on each of the 2 machines which we have deployed, and only allowing us to enable ports that are essential for App Svr to work.

http://docs.sun.com/app/docs/doc/819-4733/6n6s6u1b6?a=view#ablci

I think you are referring to the above document.

"JMX 8686 Another port is used by the JMX connector to communicate with the DAS."

My thinking is:

1. there is a port ("8686") for connection/establishment purpose for the JMX client to reach the JMX server

2. after initial connection, there is "another port" used for communication purpose

Am I correct? Anyone care to comment?

justCheeChonga at 2007-7-28 17:17:42 > top of Java-index,Application & Integration Servers,Application Servers...
# 2

8686 is the initial communication port for JMX,

do an "grep jmx-connector" on server.xml, you can see 3 ports as a result. Open those ports in your firewall and try.

One will be 8686 which will be for DAS-SERVER

<admin-service system-jmx-connector-name="system" type="das-and-server">

another with variable JMX_SYSTEM_CONNECTOR_PORT, which you can see from admin console. This is for Server

<admin-service system-jmx-connector-name="system" type="server">

another some random port number after nodeagent definition for JMX

<node-agent name="node agent name" start-servers-in-startup="true" system-jmx-connector-name="system">

Regards

Activexpert

activexperta at 2007-7-28 17:17:42 > top of Java-index,Application & Integration Servers,Application Servers...