[#MB-741] Extraneous port created for management context specification

FUSE Message Broker

Extraneous port created for management context specification

Created: 30/Sep/10 07:24 PM Updated: 01/Oct/10 02:27 PM

Component/s:

broker

Affects Version/s:

5.3.1-fuse-02-01

Fix Version/s:

None

File Attachments:	1. activemq_1.xml (6 kB) 2. activemq_2.xml (6 kB) 3. activemq_no_JMX.bat (4 kB)
Environment:	Running either windows or linux

Description

« Hide

If connector port is set in managementContext element, it is allocated but also port 1099 is always allocated.

Log shows:

C:\apache-activemq-5.3.2\example>netstat -ao | grep 4020
TCP nbrbonnea:1099 nbrbonnea.americas.progress.com:0 LISTENING 4020 <<<<<<<<<
TCP nbrbonnea:8161 nbrbonnea.americas.progress.com:0 LISTENING 4020
TCP nbrbonnea:11099 nbrbonnea.americas.progress.com:0 LISTENING 4020
TCP nbrbonnea:11119 nbrbonnea.americas.progress.com:0 LISTENING 4020
TCP nbrbonnea:61613 nbrbonnea.americas.progress.com:0 LISTENING 4020
TCP nbrbonnea:61616 nbrbonnea.americas.progress.com:0 LISTENING 4020

NOTE: This behavior is observed IF/WHEN you disable the setting of any value for SUNJMX in the
startup script on either LINUX or Windows. If you leave SUNJMX as in the unaltered startup script,
get errors in startup, 1099 is allocated as well as two random ports while the specified JMX and RMI ports
are allocated as specified. See log below in that case:

C:\apache-activemq-5.3.2\example>netstat -ao | grep 7300
TCP nbrbonnea:1099 nbrbonnea.americas.progress.com:0 LISTENING 7300 <<<<<<<
TCP nbrbonnea:4635 nbrbonnea.americas.progress.com:0 LISTENING 7300 <<<<<<<
TCP nbrbonnea:4636 nbrbonnea.americas.progress.com:0 LISTENING 7300 <<<<<<<
TCP nbrbonnea:8161 nbrbonnea.americas.progress.com:0 LISTENING 7300
TCP nbrbonnea:11099 nbrbonnea.americas.progress.com:0 LISTENING 7300
TCP nbrbonnea:11119 nbrbonnea.americas.progress.com:0 LISTENING 7300
TCP nbrbonnea:61613 nbrbonnea.americas.progress.com:0 LISTENING 7300
TCP nbrbonnea:61616 nbrbonnea.americas.progress.com:0 LISTENING 7300

I am attaching the configuration file used as well as the modified startup script.

Description

If connector port is set in managementContext element, it is allocated but also port 1099 is always allocated. <managementContext createConnector="true" connectorPort="11099" rmiServerPort="11119"/> Log shows: C:\apache-activemq-5.3.2\example>netstat -ao | grep 4020 TCP nbrbonnea:1099 nbrbonnea.americas.progress.com:0 LISTENING 4020 <<<<<<<<< TCP nbrbonnea:8161 nbrbonnea.americas.progress.com:0 LISTENING 4020 TCP nbrbonnea:11099 nbrbonnea.americas.progress.com:0 LISTENING 4020 TCP nbrbonnea:11119 nbrbonnea.americas.progress.com:0 LISTENING 4020 TCP nbrbonnea:61613 nbrbonnea.americas.progress.com:0 LISTENING 4020 TCP nbrbonnea:61616 nbrbonnea.americas.progress.com:0 LISTENING 4020 NOTE: This behavior is observed IF/WHEN you disable the setting of any value for SUNJMX in the startup script on either LINUX or Windows. If you leave SUNJMX as in the unaltered startup script, get errors in startup, 1099 is allocated as well as two random ports while the specified JMX and RMI ports are allocated as specified. See log below in that case: C:\apache-activemq-5.3.2\example>netstat -ao | grep 7300 TCP nbrbonnea:1099 nbrbonnea.americas.progress.com:0 LISTENING 7300 <<<<<<< TCP nbrbonnea:4635 nbrbonnea.americas.progress.com:0 LISTENING 7300 <<<<<<< TCP nbrbonnea:4636 nbrbonnea.americas.progress.com:0 LISTENING 7300 <<<<<<< TCP nbrbonnea:8161 nbrbonnea.americas.progress.com:0 LISTENING 7300 TCP nbrbonnea:11099 nbrbonnea.americas.progress.com:0 LISTENING 7300 TCP nbrbonnea:11119 nbrbonnea.americas.progress.com:0 LISTENING 7300 TCP nbrbonnea:61613 nbrbonnea.americas.progress.com:0 LISTENING 7300 TCP nbrbonnea:61616 nbrbonnea.americas.progress.com:0 LISTENING 7300 I am attaching the configuration file used as well as the modified startup script.

Show »

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Rich Bonneau added a comment - 01/Oct/10 01:19 AM

Log file displays updated to show observed behaviors of port 1099 and the random
ports.

[ Permlink | « Hide ]

Rich Bonneau added a comment - 01/Oct/10 02:27 PM

Additional attached config file activemq_2.xml does NOT exhibit the observed behavior. It differs only in the absence of a network connector element!