Server Version 10.6.1
Geoevent Server successfully federated with ArcGIS Portal in Same VLAN and no port restriction in network. All SSL certificates are network domain authenticated. and using https connection to communicate. Why Geoevent server is giving below error ?
Error MSG :
Failed to create connection cxn-34200 com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile. at com.rabbitmq.client.impl.AMQConnection.start(AMQConnection.java:351) [55:com.esri.ges.framework.messaging.jms-messaging:10.6.1] at com.rabbitmq.client.impl.recovery.RecoveryAwareAMQConnectionFactory.newConnection(RecoveryAwareAMQConnectionFactory.java:64) [55:com.esri.ges.framework.messaging.jms-messaging:10.6.1] at com.rabbitmq.client.impl.recovery.AutorecoveringConnection.init(AutorecoveringConnection.java:99) [55:com.esri.ges.framework.messaging.jms-messaging:10.6.1] at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:948) [55:com.esri.ges.framework.messaging.jms-messaging:10.6.1] at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:907) [55:com.esri.ges.framework.messaging.jms-messaging:10.6.1] at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:823) [55:com.esri.ges.framework.messaging.jms-messaging:10.6.1] at net.jodah.lyra.internal.ConnectionHandler$3.call(ConnectionHandler.java:233) [55:com.esri.ges.framework.messaging.jms-messaging:10.6.1] at net.jodah.lyra.internal.ConnectionHandler$3.call(ConnectionHandler.java:227) [55:com.esri.ges.framework.messaging.jms-messaging:10.6.1] at net.jodah.lyra.internal.RetryableResource.callWithRetries(RetryableResource.java:50) [55:com.esri.ges.framework.messaging.jms-messaging:10.6.1] at net.jodah.lyra.internal.ConnectionHandler.createConnection(ConnectionHandler.java:227) [55:com.esri.ges.framework.messaging.jms-messaging:10.6.1] at net.jodah.lyra.internal.ConnectionHandler.createConnection(ConnectionHandler.java:115) [55:com.esri.ges.framework.messaging.jms-messaging:10.6.1] at net.jodah.lyra.Connections.create(Connections.java:68) [55:com.esri.ges.framework.messaging.jms-messaging:10.6.1] at com.esri.ges.messaging.jms.amqp.AmqpMessagingFactory$ConnectionEstablisher.run(AmqpMessagingFactory.java:1040) [55:com.esri.ges.framework.messaging.jms-messaging:10.6.1] at java.lang.Thread.run(Thread.java:748) [?:?] |
Hi Anjitha,
this is a BUG in ArcGIS Server 10.6.1.
On startup of ArcGIS Server the initialization of RabbitMQ may not work correctly because of some timing issues. In this case ArcGIS Server is not able to Login into RabbitMQ on runtime.
Are you working with stream services?
Best,
Stefan
Thank you very much for the reply . Yes I am working with Geoevent server to stream taxi live data. feeling this server is not stable yet. Is there any patch to correct this issue ?
I am having the same problem working with output to a stream service, is a patch or workaround available?
Hi,
yesterday I got the information that a hotfix has been released that addresses this issue:
BUG-000117633: In 10.6.1 and prior, the message bus platform service may not be initialized correctly in all Environments.
Unfortunately, there is no patch available that fixes this issue yet. I think the official way is to request the hotfix via your local Distributor.
Best,
Stefan
Hi Anjitha,
Try this:
- Navigate to ArcGIS Server Administrator Directory > Home > system > platform services
- Make sure that all the Services like the Synchronization Service, Compute Platform and Message Bus are in STARTED state (it can be checked using the Supported Operations: "status" button), if they are STOPPED, you can manually START it
- Navigate to Windows Services panel (Windows Run > services.msc)
- Stop the ArcGIS Server, ArcGIS GeoEvent Gateway and ArcGIS GeoEvent Server Windows service
- Start of the ArcGIS Server, then wait for around 5 minutes
- Start of the ArcGIS GeoEvent Gateway, then wait for around a minute
- Start of the ArcGIS GeoEvent Server, then wait for around a minute
- Clear the browser cache
- Check the logs again to see if there are any "Failed to create connection cxn…" error messages
Hope this helps!
Regards,
Richardson
Hi, thanks for the tip, I just wanted to say that this worked for me.
Thanks!
Peggy
Hi Richardson,
We are at 10.5 and after a server reboot, we are experiencing a similar error. Is there a process similar to yours listed for 10.5?
Thanks,
-Derek