Corda 交易在联系公证服务时停滞
Corda Transaction is stalled when contacting notary service
我正在使用 Corda 版本 1。当我在 docker 环境中的 运行 个节点时，交易没有完成。它在这个日志之后卡住了：
Flow logs >> Generating transaction based on new Trade Details.
Flow logs >> Verifying contract constraints.
Flow logs >> Signing transaction with our private key.
Flow logs >> Gathering the counterparty's signature.
Flow logs >> Structural step change in child of Gathering the counterparty's signature.
Flow logs >> Collecting signatures from counter-parties.
Flow logs >> Verifying collected signatures.
Flow logs >> Done
Flow logs >> Obtaining notary signature and recording transaction.
Flow logs >> Structural step change in child of Obtaining notary signature and recording transaction.
Flow logs >> Requesting signature by notary service
Flow logs >> Structural step change in child of Requesting signature by notary service
Flow logs >> Requesting signature by Notary service
我可以在控制器日志中看到这条消息：
[INFO ] 2017-10-27T07:27:57,024Z [Messaging] messaging.NodeMessagingClient.createQueueIfAbsent - Create fresh queue internal.peers.8Kqd4oWdx4KQGHGNkbLbDP3bxDkm43Gy7NpJqGdiL5G2PwRdVu9dngMkJkp bound on same address
[WARN ] 2017-10-27T07:29:57,111Z [Messaging] messaging.NodeMessagingClient.sendWithRetry - Reached the maximum number of retries (3) for message ClientMessageImpl[messageID=0, durable=true, address=internal.peers.8Kqd4oWdx4KQGHGNkbLbDP3bxDkm43Gy7NpJqGdiL5G2PwRdVu9dngMkJkp,userID=null,properties=TypedProperties[platform-version=1,corda-vendor=Corda Open Source,release-version=1.0.0,platform-topic=platform.session,session-id=0,_AMQ_DUPL_ID=0efb502e-15f6-4b0a-bdf9-8296571f228f]] redelivery to internal.peers.8Kqd4oWdx4KQGHGNkbLbDP3bxDkm43Gy7NpJqGdiL5G2PwRdVu9dngMkJkp
我已经通过在创建节点容器时在 p2pAddress 中使用实际主机 IP 地址解决了这个问题。
它在 p2pAddress 中被映射为本地主机，我已经用主机 ip 公开了容器 ip。因此理想情况下这不应该是问题，但是如果我们使用本地主机，它会在签署公证服务时产生问题。非常感谢支持。
我正在使用 Corda 版本 1。当我在 docker 环境中的 运行 个节点时，交易没有完成。它在这个日志之后卡住了：
Flow logs >> Generating transaction based on new Trade Details.
Flow logs >> Verifying contract constraints.
Flow logs >> Signing transaction with our private key.
Flow logs >> Gathering the counterparty's signature.
Flow logs >> Structural step change in child of Gathering the counterparty's signature.
Flow logs >> Collecting signatures from counter-parties.
Flow logs >> Verifying collected signatures.
Flow logs >> Done
Flow logs >> Obtaining notary signature and recording transaction.
Flow logs >> Structural step change in child of Obtaining notary signature and recording transaction.
Flow logs >> Requesting signature by notary service
Flow logs >> Structural step change in child of Requesting signature by notary service
Flow logs >> Requesting signature by Notary service
我可以在控制器日志中看到这条消息：
[INFO ] 2017-10-27T07:27:57,024Z [Messaging] messaging.NodeMessagingClient.createQueueIfAbsent - Create fresh queue internal.peers.8Kqd4oWdx4KQGHGNkbLbDP3bxDkm43Gy7NpJqGdiL5G2PwRdVu9dngMkJkp bound on same address
[WARN ] 2017-10-27T07:29:57,111Z [Messaging] messaging.NodeMessagingClient.sendWithRetry - Reached the maximum number of retries (3) for message ClientMessageImpl[messageID=0, durable=true, address=internal.peers.8Kqd4oWdx4KQGHGNkbLbDP3bxDkm43Gy7NpJqGdiL5G2PwRdVu9dngMkJkp,userID=null,properties=TypedProperties[platform-version=1,corda-vendor=Corda Open Source,release-version=1.0.0,platform-topic=platform.session,session-id=0,_AMQ_DUPL_ID=0efb502e-15f6-4b0a-bdf9-8296571f228f]] redelivery to internal.peers.8Kqd4oWdx4KQGHGNkbLbDP3bxDkm43Gy7NpJqGdiL5G2PwRdVu9dngMkJkp
我已经通过在创建节点容器时在 p2pAddress 中使用实际主机 IP 地址解决了这个问题。
它在 p2pAddress 中被映射为本地主机，我已经用主机 ip 公开了容器 ip。因此理想情况下这不应该是问题，但是如果我们使用本地主机，它会在签署公证服务时产生问题。非常感谢支持。