[
https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491230#comment-17491230
]
Justin Bertram commented on ARTEMIS-3683:
-----------------------------------------
bq. ...even restarting isn't helping in one of the server though in the other
server re-starting the server helped.
In that case I would suggest inspecting the node to ensure nothing else is
using port {{5001}}. The fact that it's working on one node and not other is
further indication that the problem is environmental. If this was a bug in the
broker which consistently caused this issue then we'd have lots of users
reporting this problem.
bq. Does below error mean anything to you?...AMQ224000: Failure in
initialisation: java.lang.IllegalStateException: AMQ229230: Failed to bind
acceptor cluster to master2.odazprivatecloud.com:5001
Yes. The error means exactly what it says. The broker failed to initialize
properly because it couldn't bind the "cluster" {{acceptor}} to
{{master2.odazprivatecloud.com:5001}}. This is a normal operation for networked
servers. In order to accept remote connections they have to bind a server
socket to a particular interface and port. In your case this operation failed.
The underlying reason for this failure is still unclear.
bq. I am not sure if something on broker is triggering when I am trying to
create a user using below command. As this command is failing 70% of the time
and working 30% of the time even when the broker is up and running. Is there a
reason for this?
Most of the CLI commands (e.g. {{user add}}) will connect to a broker using a
network connection. Therefore, the broker has to be running and listening for
network connections. In your case the broker isn't even getting to the point
where it can listen for network connections.
You haven't provided any specific details about why the {{user add}} command is
failing so I can't really comment on that. I recommend you follow up regarding
this issue on the [ActiveMQ users mailing
list|https://activemq.apache.org/contact]. For what it's worth, I would
strongly recommend _against_ using a broker-managed security repository (e.g.
properties files) in a production use-case, especially one that that uses
clustering.
> Failed to bind acceptor cluster to
> ----------------------------------
>
> Key: ARTEMIS-3683
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3683
> Project: ActiveMQ Artemis
> Issue Type: Task
> Components: Broker
> Affects Versions: 2.18.0
> Environment: Nonprod
> Reporter: Ekta
> Priority: Major
> Attachments: artemis.log
>
>
> I am facing below issue when I am trying to start up the broker using 2.18.
> It looks it is complaining about the {{acceptor}} "cluster" in
> {{broker.xml}}. My other server was facing the same issue while starting the
> server the first time, but when I re-tried starting the server again it
> worked. Both server are configured the exact same way.
> {{broker.xml}} (networking {{acceptor}} block attached for reference):
> {code:xml}
> <!--
> ###########################################
> ### Networking and cluster settings ###
> ###########################################
> -->
> <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 -->
> <!-- 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://master2.odazprivatecloud.com:61618?protocols=AMQP,CORE,OPENWIRE;tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;useEpoll=true;sslEnabled=true;keyStorePath=${SSL_KEYSTORE_PATH};keyStorePassword=${SSL_KEYSTORE_PASSWORD};enabledProtocols=${TLS_VERSION};amqpCredits=1000;amqpLowCredits=300</acceptor>
> <!-- Acceptor for cluster coordination -->
> <acceptor
> name="cluster">tcp://master2.odazprivatecloud.com:5001?protocols=CORE;tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;useEpoll=true</acceptor>
> </acceptors>
> <connectors>
> <connector
> name="broker2-master-connector">tcp://master2.odazprivatecloud.com:5001?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;useEpoll=true</connector>
> <connector
> name="broker2-slave-connector">tcp://slave2.odazprivatecloud.com:5001?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;useEpoll=true</connector>
> </connectors>
> <cluster-user>${ARTEMIS_CLUSTER_USER}</cluster-user>
> <cluster-password>${ARTEMIS_CLUSTER_PASSWORD}</cluster-password>{code}
> Error:
> {noformat}
> 2022-02-11 14:13:32,989 ERROR [org.apache.activemq.artemis.core.server]
> AMQ224000: Failure in initialisation: java.lang.IllegalStateException:
> AMQ229230: Failed to bind acceptor cluster to
> master2.odazprivatecloud.com:5001
> at
> org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptor.startServerChannels(NettyAcceptor.java:741)
> [artemis-server-2.18.0.jar:2.18.0]
> at
> org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptor.start(NettyAcceptor.java:522)
> [artemis-server-2.18.0.jar:2.18.0]
> at
> org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl.startAcceptors(RemotingServiceImpl.java:318)
> [artemis-server-2.18.0.jar:2.18.0]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.completeActivation(ActiveMQServerImpl.java:3347)
> [artemis-server-2.18.0.jar:2.18.0]
> at
> org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation.run(SharedNothingLiveActivation.java:120)
> [artemis-server-2.18.0.jar:2.18.0]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:642)
> [artemis-server-2.18.0.jar:2.18.0]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:561)
> [artemis-server-2.18.0.jar:2.18.0]
> at
> org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:64)
> [artemis-cli-2.18.0.jar:2.18.0]
> at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:115)
> [artemis-cli-2.18.0.jar:2.18.0]
> at
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:155)
> [artemis-cli-2.18.0.jar:2.18.0]
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:103)
> [artemis-cli-2.18.0.jar:2.18.0]
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:130)
> [artemis-cli-2.18.0.jar:2.18.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [rt.jar:1.8.0_322]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [rt.jar:1.8.0_322]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [rt.jar:1.8.0_322]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_322]
> at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:134)
> [artemis-boot.jar:2.18.0]
> at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:50)
> [artemis-boot.jar:2.18.0]
> Caused by: io.netty.channel.unix.Errors$NativeIoException: bind(..) failed:
> Cannot assign requested address{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
