[
https://issues.apache.org/jira/browse/ARTEMIS-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484074#comment-17484074
]
Ekta edited comment on ARTEMIS-3661 at 1/29/22, 8:01 PM:
---------------------------------------------------------
Hello Justin,
Just to confirm, the command worked when I changed the url to
tcp://localhost:5001, I have validated by running the ./artemis user list
command and by checking the artemis-roles and artemis-users file under /etc..
It looks when I run the below command without specifying the properties, by
default it picks up Connection brokerURL = tcp://localhost:61618. Below is the
example snippet.
[test@localhost bin]$ ./artemis user add
2022-01-29T14:45:53,712-0500 [25361 1] com.newrelic INFO: New Relic Agent:
Loading configuration file "/app/newrelic/./newrelic.yml"
2022-01-29T14:45:53,816-0500 [25361 1] com.newrelic INFO: Using default
collector host: collector.newrelic.com
2022-01-29T14:45:53,816-0500 [25361 1] com.newrelic INFO: Using default metric
ingest URI: https://metric-api.newrelic.com/metric/v1
2022-01-29T14:45:53,817-0500 [25361 1] com.newrelic INFO: Using default event
ingest URI: https://insights-collector.newrelic.com/v1/accounts/events
2022-01-29T14:45:53,923-0500 [25361 1] com.newrelic INFO: New Relic Agent:
Writing to log file: /app/newrelic/logs/newrelic_agent.log
Connection brokerURL = tcp://localhost:61618
--user-command-user: is a mandatory property!
Please provide the username to use for the chosen user command:
I was referring to my broker.xml where Connection brokerURL =
tcp://localhost:61618 could be getting picked from. Below are my connectors
from broker.xml and I can see that cluster communication happens over port 5001
where master communication happens on 61618.
connectors:
<!-- Acceptor for every supported protocol -->
<acceptor
name="artemis">tcp://master: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://master:5001?protocols=CORE;tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;useEpoll=true</acceptor>undefined</acceptors>undefined<connectors>
<connector
name="broker1-master-connector">tcp://master:5001?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;useEpoll=true</connector>
<connector
name="broker1-slave-connector">tcp://slave:5001?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;useEpoll=true</connector>undefined</connectors>
Please confirm, This user is suppose to be created at the cluster level.
Also, in previous versions we did not have to specify the --url property. It
looks to be mandatory in 2.18..
Thanks
was (Author: ekta-awasthi):
Hello Justin,
Just to confirm, the command worked when I changed the url to
tcp://localhost:5001, I have validated by running the ./artemis user list
command and by checking the artemis-roles and artemis-users file under /etc..
Not sure why it was picking up tcp://localhost:61618 by default.
I was referring to my broker.xml where I have the connectors setup in file is
as below and I can see that cluster communication happens over port 5001 where
master communication happens on 61618.
Please confirm, This user is suppose to be created at the cluster level.
Also, in previous versions we did not have to specify the --url property. It
looks to be mandatory in 2.18..
Thanks
> Receiving timed out while creating user in artemis 2.18
> --------------------------------------------------------
>
> Key: ARTEMIS-3661
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3661
> Project: ActiveMQ Artemis
> Issue Type: Task
> Components: Broker
> Affects Versions: 2.18.0
> Reporter: Ekta
> Priority: Major
>
> I am facing time out issues while I am running the below command from my
> broker which is currently running on 2.18. I have made some changes to the
> command since the old command does not work on newer version.
> Is there anything I am doing wrong here. My broker is up and running while I
> am executing the below command. This command use to work just fine in old
> versions.
> Command:
> {noformat}
> ./artemis user add --user-command-user test --user-command-password test1234
> --role test --url tcp://localhost:61618{noformat}
> Error:
> {noformat}
> Exception in thread "main"
> ActiveMQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT
> message=AMQ219013: Timed out waiting to receive cluster topology. Group:null]
> at
> org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:743)
> at
> org.apache.activemq.artemis.cli.commands.AbstractAction.performCoreManagement(AbstractAction.java:35)
> at
> org.apache.activemq.artemis.cli.commands.user.AddUser.add(AddUser.java:52)
> at
> org.apache.activemq.artemis.cli.commands.user.AddUser.execute(AddUser.java:42)
> at org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:155)
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:103)
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:130)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:134)
> at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:50){noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
