[
https://issues.apache.org/jira/browse/ARTEMIS-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vilius Šumskas updated ARTEMIS-5260:
------------------------------------
Description:
If you try to configure JMX remote management in Artemis broker to be reachable
via NAT (for example a broker behind load balancer), there is a 2 minute 10
seconds delay every time the broker is started. Steps to reproduce:
# Create standard Artemis broker instance.
# Enable remote JMX management in management.xml with `<connector
connector-port="1099" connector-host="0.0.0.0" rmi-registry-port="1100" />`.
# Add -Djava.rmi.server.hostname=8.8.8.8 (or any other IP not under host's
interfaces) to artemis.profile
# Restart the broker and check the delay between
{noformat}
2025-01-14 22:49:38,308 INFO [org.apache.activemq.artemis.core.server]
AMQ221006: Waiting to obtain primary lock{noformat}
and
{code:java}
2025-01-14 22:51:50,703 INFO [org.apache.activemq.artemis.core.server]
AMQ221012: Using AIO Journal{code}
There is no such delay when Artemis' JMX remote management is disabled and the
standard JVM JMX Mbean used instead.
Thread dump during the delay: [https://p.defau.lt/?WV75z6Vajriy_tmBpASMrg]
Thread dump just right after the delay:
[https://p.defau.lt/?_yKMZJpdrGhfAzc2cy_t6A]
was:
If you try to configure JMX remote management in Artemis broker to be reachable
via NAT (for example a broker behind load balancer), there is a 2 minute 10
seconds delay every time the broker is started. Steps to reproduce:
# Create standard Artemis broker instance.
# Enable remote JMX management in management.xml with <connector
connector-port="1099" connector-host="0.0.0.0" rmi-registry-port="1100" />.
# Add -Djava.rmi.server.hostname=8.8.8.8 (or any other IP not under host's
interfaces) to artemis.profile
# Restart the broker and check the delay between
{noformat}
2025-01-14 22:49:38,308 INFO [org.apache.activemq.artemis.core.server]
AMQ221006: Waiting to obtain primary lock{noformat}
and
{code:java}
2025-01-14 22:51:50,703 INFO [org.apache.activemq.artemis.core.server]
AMQ221012: Using AIO Journal{code}
There is no such delay when Artemis' JMX remote management is disabled and the
standard JVM JMX Mbean used instead.
Thread dump during the delay: [https://p.defau.lt/?WV75z6Vajriy_tmBpASMrg]
Thread dump just right after the delay:
[https://p.defau.lt/?_yKMZJpdrGhfAzc2cy_t6A]
> Broker startup delay when using public NAT IP as JMX RMI hostname
> -----------------------------------------------------------------
>
> Key: ARTEMIS-5260
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5260
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Environment: Rocky Linux 9.5
> ActiveMQ Artemis 2.39.0
> Reporter: Vilius Šumskas
> Priority: Minor
>
> If you try to configure JMX remote management in Artemis broker to be
> reachable via NAT (for example a broker behind load balancer), there is a 2
> minute 10 seconds delay every time the broker is started. Steps to reproduce:
> # Create standard Artemis broker instance.
> # Enable remote JMX management in management.xml with `<connector
> connector-port="1099" connector-host="0.0.0.0" rmi-registry-port="1100" />`.
> # Add -Djava.rmi.server.hostname=8.8.8.8 (or any other IP not under host's
> interfaces) to artemis.profile
> # Restart the broker and check the delay between
> {noformat}
> 2025-01-14 22:49:38,308 INFO [org.apache.activemq.artemis.core.server]
> AMQ221006: Waiting to obtain primary lock{noformat}
> and
> {code:java}
> 2025-01-14 22:51:50,703 INFO [org.apache.activemq.artemis.core.server]
> AMQ221012: Using AIO Journal{code}
>
> There is no such delay when Artemis' JMX remote management is disabled and
> the standard JVM JMX Mbean used instead.
> Thread dump during the delay: [https://p.defau.lt/?WV75z6Vajriy_tmBpASMrg]
> Thread dump just right after the delay:
> [https://p.defau.lt/?_yKMZJpdrGhfAzc2cy_t6A]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
