Hono和Ditto已成功连接。但是，当我尝试从Hono发送数据时，我会收到503-服务不可用消息。
但是当我检查Ditto日志时。我超出了以下AMQP限制。
connectivity_1 | 2019-10-14 16:34:38,294 INFO [] o.e.d.s.c.m.ConnectionActor akka://ditto-
cluster/system/sharding/connection/6/hono-sandbox-connection-123/pa - Starting ClientActor for
connection <hono-sandbox-connection-123> with <1> clients.
connectivity_1 | 2019-10-14 16:34:38,308 INFO [] a.a.RepointableActorRef akka://ditto-
cluster/system/distributedPubSubMediator - Message
[org.eclipse.ditto.signals.events.connectivity.ConnectionCreated] from Actor[akka://ditto-
cluster/system/sharding/connection/6/hono-sandbox-connection-123/pa#233633004] to Actor[akka://ditto-
cluster/system/distributedPubSubMediator#-301178072] was not delivered. [9] dead letters encountered.
If this is not an expected behavior, then [Actor[akka://ditto-
cluster/system/distributedPubSubMediator#-301178072]] may have terminated unexpectedly, This logging
can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-
letters-during-shutdown'.
connectivity_1 | 2019-10-14 16:34:38,441 INFO [] o.a.q.j.s.SaslMechanismFinder - Best match for
SASL auth was: SASL-PLAIN
connectivity_1 | 2019-10-14 16:34:38,721 INFO [] o.a.q.j.s.SaslMechanismFinder - Best match for
SASL auth was: SASL-PLAIN
connectivity_1 | 2019-10-14 16:34:39,128 INFO [] o.a.q.j.s.SaslMechanismFinder - Best match for
SASL auth was: SASL-PLAIN
connectivity_1 | 2019-10-14 16:34:39,781 INFO [] o.a.q.j.s.SaslMechanismFinder - Best match for
SASL auth was: SASL-PLAIN
connectivity_1 | 2019-10-14 16:34:40,962 INFO [] o.a.q.j.s.SaslMechanismFinder - Best match for
SASL auth was: SASL-PLAIN
connectivity_1 | 2019-10-14 16:34:41,020 WARN [] o.e.d.s.c.m.a.JMSConnectionHandlingActor
akka://ditto-cluster/system/sharding/connection/6/hono-sandbox-connection-
123/pa/$a/c1/jmsConnectionHandling-hono-sandbox-connection-123-connect1 - Failed to connect JMS
client:connection disallowed by local policy [condition = amqp:resource-limit-exceeded]
我不确定AMQP：资源限制超出错误的含义是什么？这是否阻止我从河野派往同上？
如果我将所有这些都放到Ditto Mongo服务器的dbs下面，并再次创建新的东西和Connections，它会起作用吗？
> show dbs
admin 0.000GB
concierge 0.000GB
config 0.000GB
connectivity 0.000GB
local 0.000GB
policies 0.002GB
searchDB 0.001GB
things 0.337GB
编辑：我试图在出现错误的同一台服务器上再次连接Eclipse Hono和Eclipse Ditto。
执行curl commnad时，我收到状态201（已创建连接）消息。但是当我同时检查日志时，收到以下消息。
connectivity_1_ad306c4c315b | 2019-10-15T15:46:36.233449988Z 2019-10-15 17:46:36,233 WARN [] o.e.d.s.c.m.ConnectionActor akka://ditto-cluster/system/sharding/connection/12/test_co_nn_id_12/pa - Operation <connect> on connection <test_co_nn_id_12> failed due to ConnectionFailedException: Failed to connect JMS client:connection disallowed by local policy [condition = amqp:resource-limit-exceeded].
注意：，当我在本地计算机或其他服务器中尝试此操作时，它完全可以正常工作。
答案 0 :(得分：0)
我使用
移除了堆栈并完全清除了MongoDB。docker-compose down
然后重新安装Ditto。建立Hono和Ditto连接，并尝试更早地发送数据。一切都按预期进行。