[jira] [Comment Edited] (ARTEMIS-3661) Receiving timed out while creating user in artemis 2.18

["Ekta (Jira)" <ji...@apache.org>]

    [ 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, 7:45 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.. 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

 

 


was (Author: ekta-awasthi):
Hello Justin,

 

Just to confirm, the command worked when I changed the url to below, I have validated by listing the user and by checking the roles and users file under /etc. tcp://localhost:5001. 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 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)