Justin,
Thanks for your patience and efforts - much appreciated....
Following are both files: Broker.xml and artemis.profile.cmd. both files had
HornetQ at port 5445 and were not commented out initially. I did change the
port in both files to 5999 and retested, then based on your comments I
commented them out and tested again. But in all cases Bind errors occurred for
HornetQ at 5445 as shown below in the Artemis log file.
Artemis.log:
2021-07-08 08:44:16,369 INFO
[org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting
ActiveMQ Artemis Server
2021-07-08 08:44:16,452 INFO [org.apache.activemq.artemis.core.server]
AMQ221000: live Message Broker is starting with configuration Broker
Configuration
(clustered=false,journalDirectory=data/journal,bindingsDirectory=data/bindings,largeMessagesDirectory=data/large-messages,pagingDirectory=data/paging)
2021-07-08 08:44:16,526 INFO [org.apache.activemq.artemis.core.server]
AMQ221013: Using NIO Journal
2021-07-08 08:44:16,672 INFO [org.apache.activemq.artemis.core.server]
AMQ221057: Global Max Size is being adjusted to 1/2 of the JVM max size (-Xmx).
being defined as 536,870,912
2021-07-08 08:44:16,724 INFO [org.apache.activemq.artemis.core.server]
AMQ221043: Protocol module found: [artemis-server]. Adding protocol support
for: CORE
2021-07-08 08:44:16,729 INFO [org.apache.activemq.artemis.core.server]
AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol
support for: AMQP
2021-07-08 08:44:16,731 INFO [org.apache.activemq.artemis.core.server]
AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol
support for: HORNETQ
2021-07-08 08:44:16,733 INFO [org.apache.activemq.artemis.core.server]
AMQ221043: Protocol module found: [artemis-mqtt-protocol]. Adding protocol
support for: MQTT
2021-07-08 08:44:16,735 INFO [org.apache.activemq.artemis.core.server]
AMQ221043: Protocol module found: [artemis-openwire-protocol]. Adding protocol
support for: OPENWIRE
2021-07-08 08:44:16,739 INFO [org.apache.activemq.artemis.core.server]
AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol
support for: STOMP
2021-07-08 08:44:16,835 WARN [org.apache.activemq.artemis.core.server]
AMQ222219: File
d:\Program%20Files\Artemis-MQ\apache-artemis-2.17.0\smmq1\etc\logging.properties
does not exist
2021-07-08 08:44:16,841 INFO [org.apache.activemq.artemis.core.server]
AMQ221034: Waiting indefinitely to obtain live lock
2021-07-08 08:44:16,842 INFO [org.apache.activemq.artemis.core.server]
AMQ221035: Live Server Obtained live lock
2021-07-08 08:44:17,440 INFO [org.apache.activemq.artemis.core.server]
AMQ221080: Deploying address DLQ supporting [ANYCAST]
2021-07-08 08:44:17,455 INFO [org.apache.activemq.artemis.core.server]
AMQ221003: Deploying ANYCAST queue DLQ on address DLQ
2021-07-08 08:44:17,491 INFO [org.apache.activemq.artemis.core.server]
AMQ221080: Deploying address ExpiryQueue supporting [ANYCAST]
2021-07-08 08:44:17,493 INFO [org.apache.activemq.artemis.core.server]
AMQ221003: Deploying ANYCAST queue ExpiryQueue on address ExpiryQueue
2021-07-08 08:44:18,218 INFO [org.apache.activemq.artemis.core.server]
AMQ221020: Started NIO Acceptor at 0.0.0.0:61616 for protocols
[CORE,MQTT,AMQP,STOMP,HORNETQ,OPENWIRE]
2021-07-08 08:44:18,268 ERROR [org.apache.activemq.artemis.core.server]
AMQ224104: Error starting the Acceptor hornetq {scheme=tcp, port=5445,
host=0.0.0.0, protocols=HORNETQ,STOMP, useEpoll=true}
2021-07-08 08:44:18,269 ERROR [org.apache.activemq.artemis.core.server]
AMQ224000: Failure in initialisation: java.lang.IllegalStateException:
AMQ229230: Failed to bind acceptor hornetq to 0.0.0.0:5445
at
org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptor.startServerChannels(NettyAcceptor.java:695)
[artemis-server-2.17.0.jar:2.17.0]
at
org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptor.start(NettyAcceptor.java:458)
[artemis-server-2.17.0.jar:2.17.0]
at
org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl.startAcceptors(RemotingServiceImpl.java:317)
[artemis-server-2.17.0.jar:2.17.0]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.completeActivation(ActiveMQServerImpl.java:3309)
[artemis-server-2.17.0.jar:2.17.0]
at
org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:78)
[artemis-server-2.17.0.jar:2.17.0]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:635)
[artemis-server-2.17.0.jar:2.17.0]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:559)
[artemis-server-2.17.0.jar:2.17.0]
at
org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:64)
[artemis-cli-2.17.0.jar:2.17.0]
at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:115)
[artemis-cli-2.17.0.jar:2.17.0]
at
org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:154)
[artemis-cli-2.17.0.jar:2.17.0]
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:102)
[artemis-cli-2.17.0.jar:2.17.0]
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:129)
[artemis-cli-2.17.0.jar:2.17.0]
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java.base:]
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
[java.base:]
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[java.base:]
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
[java.base:]
at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:134)
[artemis-boot.jar:2.17.0]
at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:50)
[artemis-boot.jar:2.17.0]
Caused by: java.net.BindException: Address already in use: bind
at java.base/sun.nio.ch.Net.bind0(Native Method) [java.base:]
at java.base/sun.nio.ch.Net.bind(Net.java:552) [java.base:]
at
java.base/sun.nio.ch.ServerSocketChannelImpl.netBind(ServerSocketChannelImpl.java:336)
[java.base:]
at
java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:294)
[java.base:]
at
io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:134)
[netty-all-4.1.51.Final.jar:4.1.51.Final]
at
io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:550)
[netty-all-4.1.51.Final.jar:4.1.51.Final]
at
io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1334)
[netty-all-4.1.51.Final.jar:4.1.51.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:506)
[netty-all-4.1.51.Final.jar:4.1.51.Final]
at
io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:491)
[netty-all-4.1.51.Final.jar:4.1.51.Final]
at
io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:973)
[netty-all-4.1.51.Final.jar:4.1.51.Final]
at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:248)
[netty-all-4.1.51.Final.jar:4.1.51.Final]
at
io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:356)
[netty-all-4.1.51.Final.jar:4.1.51.Final]
at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
[netty-all-4.1.51.Final.jar:4.1.51.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
[netty-all-4.1.51.Final.jar:4.1.51.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
[netty-all-4.1.51.Final.jar:4.1.51.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
[netty-all-4.1.51.Final.jar:4.1.51.Final]
at
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
[netty-all-4.1.51.Final.jar:4.1.51.Final]
at
org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
[artemis-commons-2.17.0.jar:2.17.0]
2021-07-08 08:44:18,279 INFO [org.apache.activemq.artemis.core.server]
AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.17.0 [0.0.0.0,
nodeID=3806070b-df32-11eb-a6ae-005056947554]
2021-07-08 08:44:19,076 INFO
[org.apache.activemq.hawtio.branding.PluginContextListener] Initialized
activemq-branding plugin
2021-07-08 08:44:19,257 INFO
[org.apache.activemq.hawtio.plugin.PluginContextListener] Initialized
artemis-plugin plugin
2021-07-08 08:44:20,876 INFO [io.hawt.HawtioContextListener] Initialising
hawtio services
2021-07-08 08:44:20,935 INFO [io.hawt.system.ConfigManager] Configuration will
be discovered via system properties
2021-07-08 08:44:20,942 INFO [io.hawt.jmx.JmxTreeWatcher] Welcome to Hawtio
2.11.0
2021-07-08 08:44:20,960 INFO [io.hawt.web.auth.AuthenticationConfiguration]
Starting hawtio authentication filter, JAAS realm: "activemq" authorized
role(s): "amq" role principal classes:
"org.apache.activemq.artemis.spi.core.security.jaas.RolePrincipal"
2021-07-08 08:44:21,018 INFO [io.hawt.web.proxy.ProxyServlet] Proxy servlet is
disabled
2021-07-08 08:44:21,026 INFO
[io.hawt.web.servlets.JolokiaConfiguredAgentServlet] Jolokia overridden
property: [key=policyLocation,
value=file:/d:/Program%20Files/Artemis-MQ/apache-artemis-2.17.0/smmq1/etc/\jolokia-access.xml]
2021-07-08 08:44:21,250 INFO [org.apache.activemq.artemis] AMQ241001: HTTP
Server started at http://localhost:8161
2021-07-08 08:44:21,252 INFO [org.apache.activemq.artemis] AMQ241002: Artemis
Jolokia REST API available at http://localhost:8161/console/jolokia
2021-07-08 08:44:21,254 INFO [org.apache.activemq.artemis] AMQ241004: Artemis
Console available at http://localhost:8161/console
2021-07-08 08:44:21,436 INFO [io.hawt.web.auth.AuthenticationFilter]
Destroying hawtio authentication filter
2021-07-08 08:44:21,441 INFO [io.hawt.HawtioContextListener] Destroying hawtio
services
2021-07-08 08:44:21,509 INFO
[org.apache.activemq.hawtio.plugin.PluginContextListener] Destroyed
artemis-plugin plugin
2021-07-08 08:44:21,545 INFO
[org.apache.activemq.hawtio.branding.PluginContextListener] Destroyed
activemq-branding plugin
2021-07-08 08:44:21,619 INFO [org.apache.activemq.artemis.core.server]
AMQ221002: Apache ActiveMQ Artemis Message Broker version 2.17.0
[3806070b-df32-11eb-a6ae-005056947554] stopped, uptime 5.192 seconds
Broker.xml:
<?xml version='1.0'?>
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<configuration xmlns="urn:activemq"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xi="http://www.w3.org/2001/XInclude";
xsi:schemaLocation="urn:activemq
/schema/artemis-configuration.xsd">
<core xmlns="urn:activemq:core"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="urn:activemq:core ">
<name>0.0.0.0</name>
<persistence-enabled>true</persistence-enabled>
<!-- this could be ASYNCIO, MAPPED, NIO
ASYNCIO: Linux Libaio
MAPPED: mmap files
NIO: Plain Java Files
-->
<journal-type>NIO</journal-type>
<paging-directory>data/paging</paging-directory>
<bindings-directory>data/bindings</bindings-directory>
<journal-directory>data/journal</journal-directory>
<large-messages-directory>data/large-messages</large-messages-directory>
<journal-datasync>true</journal-datasync>
<journal-min-files>2</journal-min-files>
<journal-pool-files>10</journal-pool-files>
<journal-device-block-size>4096</journal-device-block-size>
<journal-file-size>10M</journal-file-size>
<!--
This value was determined through a calculation.
Your system could perform 0.29 writes per millisecond
on the current journal configuration.
That translates as a sync write every 3440000 nanoseconds.
Note: If you specify 0 the system will perform writes directly to the
disk.
We recommend this to be 0 if you are using journalType=MAPPED and
journal-datasync=false.
-->
<journal-buffer-timeout>3440000</journal-buffer-timeout>
<!--
When using ASYNCIO, this will determine the writing queue depth for
libaio.
-->
<journal-max-io>1</journal-max-io>
<!--
You can verify the network health of a particular NIC by specifying the
<network-check-NIC> element.
<network-check-NIC>theNicName</network-check-NIC>
-->
<!--
Use this to use an HTTP server to validate the network
<network-check-URL-list>http://www.apache.org</network-check-URL-list>
-->
<!-- <network-check-period>10000</network-check-period> -->
<!-- <network-check-timeout>1000</network-check-timeout> -->
<!-- this is a comma separated list, no spaces, just DNS or IPs
it should accept IPV6
Warning: Make sure you understand your network topology as this is
meant to validate if your network is valid.
Using IPs that could eventually disappear or be partially
visible may defeat the purpose.
You can use a list of multiple IPs, and if any successful
ping will make the server OK to continue running -->
<!-- <network-check-list>10.0.0.1</network-check-list> -->
<!-- use this to customize the ping used for ipv4 addresses -->
<!-- <network-check-ping-command>ping -c 1 -t %d
%s</network-check-ping-command> -->
<!-- use this to customize the ping used for ipv6 addresses -->
<!-- <network-check-ping6-command>ping6 -c 1
%2$s</network-check-ping6-command> -->
<!-- how often we are looking for how many bytes are being used on the
disk in ms -->
<disk-scan-period>5000</disk-scan-period>
<!-- once the disk hits this limit the system will block, or close the
connection in certain protocols
that won't support flow control. -->
<max-disk-usage>90</max-disk-usage>
<!-- should the broker detect dead locks and other issues -->
<critical-analyzer>true</critical-analyzer>
<critical-analyzer-timeout>120000</critical-analyzer-timeout>
<critical-analyzer-check-period>60000</critical-analyzer-check-period>
<critical-analyzer-policy>HALT</critical-analyzer-policy>
<page-sync-timeout>3440000</page-sync-timeout>
<!-- the system will enter into page mode once you hit this limit.
This is an estimate in bytes of how much the messages are using in
memory
The system will use half of the available memory (-Xmx) by default
for the global-max-size.
You may specify a different value here if you need to customize it
to your needs.
<global-max-size>100Mb</global-max-size>
-->
<acceptors>
<!-- useEpoll means: it will use Netty epoll if you are on a system
(Linux) that supports it -->
<!-- amqpCredits: The number of credits sent to AMQP producers -->
<!-- amqpLowCredits: The server will send the # credits specified at
amqpCredits at this low mark -->
<!-- amqpDuplicateDetection: If you are not using duplicate detection,
set this to false
as duplicate detection requires
applicationProperties to be parsed on the server. -->
<!-- amqpMinLargeMessageSize: Determines how many bytes are considered
large, so we start using files to hold their data.
default: 102400, -1 would mean to
disable large mesasge control -->
<!-- Note: If an acceptor needs to be compatible with HornetQ and/or
Artemis 1.x clients add
"anycastPrefix=jms.queue.;multicastPrefix=jms.topic." to
the acceptor url.
See https://issues.apache.org/jira/browse/ARTEMIS-1644 for
more information. -->
<!-- Acceptor for every supported protocol -->
<acceptor
name="artemis">tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpDuplicateDetection=true</acceptor>
<!-- AMQP Acceptor. Listens on default AMQP port for AMQP traffic.-->
<acceptor
name="amqp">tcp://0.0.0.0:5672?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpMinLargeMessageSize=102400;amqpDuplicateDetection=true</acceptor>
<!-- STOMP Acceptor. -->
<acceptor
name="stomp">tcp://0.0.0.0:61613?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true</acceptor>
<!-- Disable... HornetQ Compatibility Acceptor. Enables HornetQ Core
and STOMP for legacy HornetQ clients.
<acceptor
name="hornetq">tcp://0.0.0.0:5999?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.;protocols=HORNETQ,STOMP;useEpoll=true
</acceptor>
-->
<!-- MQTT Acceptor -->
<acceptor
name="mqtt">tcp://0.0.0.0:1883?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=MQTT;useEpoll=true</acceptor>
</acceptors>
<security-settings>
<security-setting match="#">
<permission type="createNonDurableQueue" roles="amq"/>
<permission type="deleteNonDurableQueue" roles="amq"/>
<permission type="createDurableQueue" roles="amq"/>
<permission type="deleteDurableQueue" roles="amq"/>
<permission type="createAddress" roles="amq"/>
<permission type="deleteAddress" roles="amq"/>
<permission type="consume" roles="amq"/>
<permission type="browse" roles="amq"/>
<permission type="send" roles="amq"/>
<!-- we need this otherwise ./artemis data imp wouldn't work -->
<permission type="manage" roles="amq"/>
</security-setting>
</security-settings>
<address-settings>
<!-- if you define auto-create on certain queues, management has to be
auto-create -->
<address-setting match="activemq.management#">
<dead-letter-address>DLQ</dead-letter-address>
<expiry-address>ExpiryQueue</expiry-address>
<redelivery-delay>0</redelivery-delay>
<!-- with -1 only the global-max-size is in use for limiting -->
<max-size-bytes>-1</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>PAGE</address-full-policy>
<auto-create-queues>true</auto-create-queues>
<auto-create-addresses>true</auto-create-addresses>
<auto-create-jms-queues>true</auto-create-jms-queues>
<auto-create-jms-topics>true</auto-create-jms-topics>
</address-setting>
<!--default for catch all-->
<address-setting match="#">
<dead-letter-address>DLQ</dead-letter-address>
<expiry-address>ExpiryQueue</expiry-address>
<redelivery-delay>0</redelivery-delay>
<!-- with -1 only the global-max-size is in use for limiting -->
<max-size-bytes>-1</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>PAGE</address-full-policy>
<auto-create-queues>true</auto-create-queues>
<auto-create-addresses>true</auto-create-addresses>
<auto-create-jms-queues>true</auto-create-jms-queues>
<auto-create-jms-topics>true</auto-create-jms-topics>
</address-setting>
</address-settings>
<addresses>
<address name="DLQ">
<anycast>
<queue name="DLQ" />
</anycast>
</address>
<address name="ExpiryQueue">
<anycast>
<queue name="ExpiryQueue" />
</anycast>
</address>
</addresses>
<!-- Uncomment the following if you want to use the Standard
LoggingActiveMQServerPlugin pluging to log in events
<broker-plugins>
<broker-plugin
class-name="org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin">
<property key="LOG_ALL_EVENTS" value="true"/>
<property key="LOG_CONNECTION_EVENTS" value="true"/>
<property key="LOG_SESSION_EVENTS" value="true"/>
<property key="LOG_CONSUMER_EVENTS" value="true"/>
<property key="LOG_DELIVERING_EVENTS" value="true"/>
<property key="LOG_SENDING_EVENTS" value="true"/>
<property key="LOG_INTERNAL_EVENTS" value="true"/>
</broker-plugin>
</broker-plugins>
-->
</core>
</configuration>
Artemis.profile.cmd:
rem @echo off
rem Licensed to the Apache Software Foundation (ASF) under one
rem or more contributor license agreements. See the NOTICE file
rem distributed with this work for additional information
rem regarding copyright ownership. The ASF licenses this file
rem to you under the Apache License, Version 2.0 (the
rem "License"); you may not use this file except in compliance
rem with the License. You may obtain a copy of the License at
rem
rem http://www.apache.org/licenses/LICENSE-2.0
rem
rem Unless required by applicable law or agreed to in writing,
rem software distributed under the License is distributed on an
rem "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
rem KIND, either express or implied. See the License for the
rem specific language governing permissions and limitations
rem under the License.
set ARTEMIS_HOME="D:\Program Files\Artemis-MQ\apache-artemis-2.17.0"
set ARTEMIS_INSTANCE="D:\Program Files\Artemis-MQ\apache-artemis-2.17.0\smmq1"
set ARTEMIS_DATA_DIR="D:\Program
Files\Artemis-MQ\apache-artemis-2.17.0\smmq1\data"
set ARTEMIS_ETC_DIR="D:\Program
Files\Artemis-MQ\apache-artemis-2.17.0\smmq1\etc"
set ARTEMIS_OOME_DUMP="D:\Program
Files\Artemis-MQ\apache-artemis-2.17.0\smmq1\log\oom_dump.hprof"
rem The logging config will need an URI
rem this will be encoded in case you use spaces or special characters
rem on your directory structure
set
ARTEMIS_INSTANCE_URI="file:/d:/Program%%20Files/Artemis-MQ/apache-artemis-2.17.0/smmq1/"
set
ARTEMIS_INSTANCE_ETC_URI="file:/d:/Program%%20Files/Artemis-MQ/apache-artemis-2.17.0/smmq1/etc/"
rem - Removed HornetQ - Cluster Properties: Used to pass arguments to ActiveMQ
Artemis which can be referenced in broker.xml
set ARTEMIS_CLUSTER_PROPS=-Dactivemq.remoting.default.port=61617
-Dactivemq.remoting.amqp.port=5673 -Dactivemq.remoting.stomp.port=61614
rem -Dactivemq.remoting.hornetq.port=5999
rem Java Opts
IF "%JAVA_ARGS%"=="" (set JAVA_ARGS= -XX:+PrintClassHistogram -XX:+UseG1GC
-XX:+UseStringDeduplication -Xms512M -Xmx1024M
-Xbootclasspath/a:%ARTEMIS_HOME%\lib\jboss-logmanager-2.1.10.Final.jar;%ARTEMIS_HOME%\lib\wildfly-common-1.5.2.Final.jar
-Djava.security.auth.login.config=%ARTEMIS_ETC_DIR%\login.config
-Dhawtio.disableProxy=true -Dhawtio.offline=true -Dhawtio.realm=activemq
-Dhawtio.role=amq
-Dhawtio.rolePrincipalClasses=org.apache.activemq.artemis.spi.core.security.jaas.RolePrincipal
-Djolokia.policyLocation=%ARTEMIS_INSTANCE_ETC_URI%\jolokia-access.xml
-Dartemis.instance=%ARTEMIS_INSTANCE%)
rem Logs Safepoints JVM pauses: Uncomment to enable them
rem In addition to the traditional GC logs you could enable some JVM flags to
know any meaningful and "hidden" pause that could
rem affect the latencies of the services delivered by the broker, including
those that are not reported by the classic GC logs
rem and dependent by JVM background work (eg method deoptimizations, lock
unbiasing, JNI, counted loops and obviously GC activity).
rem Replace "all_pauses.log" with the file name you want to log to.
rem set JAVA_ARGS=%JAVA_ARGS% -XX:+PrintSafepointStatistics
-XX:PrintSafepointStatisticsCount=1 -XX:+PrintGCApplicationStoppedTime
-XX:+PrintGCApplicationConcurrentTime -XX:+LogVMOutput
-XX:LogFile=all_pauses.log
rem Enables the dumping of the java heap when a java.lang.OutOfMemoryError
exception is thrown.
rem set JAVA_ARGS=%JAVA_ARGS% -XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=%ARTEMIS_OOME_DUMP%
rem Debug args: Uncomment to enable debug
rem set
DEBUG_ARGS=-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005
Anthony Seckel | Sr. Engineer Process Automation Level 2, OT Steelmaking
AM/NS Calvert
A joint venture between ArcelorMittal and Nippon Steel & Sumitomo Metal
Corporation
Hot Strip Mill | PO Box 456, Calvert, AL 36513
T +1 251 289 4296 | M +1 251 786 2645
www.arcelormittal.com
-----Original Message-----
From: Justin Bertram <jbert...@apache.org>
Sent: Thursday, July 08, 2021 11:46 AM
To: users@activemq.apache.org
Subject: Re: HornetQ Bind - 5445 Already Used
**This Message originated from a Non-ArcelorMittal source**
The line in etc/artemis.profile which refers to the HornetQ port is commented
out by default so unless you had already enabled this line it shouldn't be an
issue. Furthermore, this line refers to 5446 rather than
5445 by default.
It's not clear why you're still having issues with the binding to port 5445
given you've removed the hornetq acceptor. Could you cut/paste your
bootstrap.xml & broker.xml?
Justin
On Thu, Jul 8, 2021 at 11:27 AM Seckel, Anthony <
anthony.sec...@arcelormittal.com> wrote:
> Justin,
>
> Thanks Justin. I removed HornetQ from ..\etc\broker.xml. There was
> also a reference in artemix.profile.xml to HornetQ and its Port #,
> which I commented out. However, it seems that HornetQ is being 'remembered'
> somewhere as MQ startup still attempts Hornet connection and stops,
> despite being removed from both xml documents.... Our created MQ is
> being is being ran "artemis run" from a dos command console at this
> time for evaluation and testing. The dos console is being terminated
> and re-started for each attempt to run.
>
> Thanks for your comments...
>
> Anthony Seckel | Sr. Engineer Process Automation Level 2, OT
> Steelmaking AM/NS Calvert A joint venture between ArcelorMittal and
> Nippon Steel & Sumitomo Metal Corporation
>
> Hot Strip Mill | PO Box 456, Calvert, AL 36513
>
> T +1 251 289 4296 | M +1 251 786 2645
> www.arcelormittal.com
>
> -----Original Message-----
> From: Justin Bertram <jbert...@apache.org>
> Sent: Wednesday, July 07, 2021 10:01 PM
> To: users@activemq.apache.org
> Subject: Re: HornetQ Bind - 5445 Already Used
>
> **This Message originated from a Non-ArcelorMittal source**
>
>
> The acceptor named "hornetq" is defined in etc/broker.xml. It's there
> for convenience for users who have legacy HornetQ clients. If you
> don't have legacy HornetQ clients you can just remove this acceptor
> from your broker.xml.
>
>
> Justin
>
> On Wed, Jul 7, 2021 at 8:45 PM Seckel, Anthony <
> anthony.sec...@arcelormittal.com> wrote:
>
> > Artemis 2.17.0 startup Bind error for HornetQ acceptor on Windows 10.
> > Changed to random port # in several files in \etc, but rerun still
> > logs
> > 5445 being attempted. Running from console. No other RUN errors
> >
> > Anthony Seckel | Sr. Engineer Process Automation Level 2, OT
> > Steelmaking AM/NS Calvert A joint venture between ArcelorMittal and
> > Nippon Steel & Sumitomo Metal Corporation
> >
> > Hot Strip Mill | PO Box 456, Calvert, AL 36513
> >
> > T +1 251 289 4296 | M +1 251 786 2645
> > www.arcelormittal.com<http://www.arcelormittal.com/>
> >
> >
>
