Disconnected received Connect: can't connect to amqp://test@{localhost:5672}:5672

444 views
Skip to first unread message

Liana Napalkova

unread,
Apr 27, 2018, 2:47:48 PM4/27/18
to rabbitmq-users
Hello,

I use the following settings rabbitmq in my code (application.conf):

op-rabbit {

  topic-exchange-name = "rabbitTestQueue"

  channel-dispatcher = "op-rabbit.default-channel-dispatcher"

  default-channel-dispatcher {

    # Dispatcher is the name of the event-based dispatcher

    type = Dispatcher


    # What kind of ExecutionService to use

    executor = "fork-join-executor"


    # Configuration for the fork join pool

    fork-join-executor {

      # Min number of threads to cap factor-based parallelism number to

      parallelism-min = 2


      # Parallelism (threads) ... ceil(available processors * factor)

      parallelism-factor = 2.0


      # Max number of threads to cap factor-based parallelism number to

      parallelism-max = 4

    }

    # Throughput defines the maximum number of messages to be

    # processed per actor before the thread jumps to the next actor.

    # Set to 1 for as fair as possible.

    throughput = 100

  }

  connection {

    virtual-host = "/"

    hosts = ["172.20.61.100"]

    username = "test"

    password = "123"

    port = 5672

    ssl = false

    connection-timeout = 3s

  }



When I execute my code, I get the error:

[ERROR] [04/27/2018 18:43:11.034] [App-akka.actor.default-dispatcher-5] [akka://App/user/$a/connection] akka://App/user/$a/connection in Disconnected received Connect: can't connect to amqp://test@{localhost:5672}:5672//, retrying in 10 seconds

I don't understand why the port 5672 is duplicated test@{172.20.61.100:5672}:5672 ?

This is the Scala code:

val config = com.typesafe.config.ConfigFactory.load()

val rabbitControl = actorSystem.actorOf(Props(new RabbitControl(ConnectionParams.fromConfig(config.getConfig("op-rabbit.connection")))))

implicit val recoveryStrategy = RecoveryStrategy.nack(false)

Michael Klishin

unread,
Apr 27, 2018, 9:10:55 PM4/27/18
to rabbitm...@googlegroups.com
See server logs for queues and take a look at https://www.rabbitmq.com/troubleshooting-networking.html.

There can be all kinds of reasons for unsuccessful connections. Server logs and networking tools will provide
you with data to work with.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
MK

Staff Software Engineer, Pivotal/RabbitMQ
Reply all
Reply to author
Forward
0 new messages