在Hyperledger Fabric v1.3中实例化Java链码的问题-无法调用链码名称:"lscc". [英] Problem about instantiating Java chaincode in Hyperledger Fabric v1.3 - Failed to invoke chaincode name:"lscc"

查看:740
本文介绍了在Hyperledger Fabric v1.3中实例化Java链码的问题-无法调用链码名称:"lscc".的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在Hyperledger Fabric v1.3中实例化Chaincode时遇到问题.

I have a problem while instantiating the Chaincode in Hyperledger Fabric v1.3.

在Hyperledger Fabric官方网站上的教程建立您的第一个网络"中,成功地实例化了Java链代码,没有任何问题.

In the tutorial 'Building your first network' on the official website of Hyperledger Fabric, the java chaincode was successfully instantiated without any problems.

但是,当我创建自己制作的链码时,会发生以下lscc错误:

However, When I created a chaincode that I made myself, the following lscc error is occurring:

异常堆栈跟踪的屏幕截图

错误消息的屏幕截图

推荐答案

v1.3 Java SDK + Java Chaincode实例化再现了相同的问题:)多次,GO链代码可以正常工作.可能是Java链代码兼容性实例化的错误.

Reproduced the same problem v1.3 Java SDK + Java Chaincode instantiation :) several times, GO chain code works just fine. Probably a bug with Java chain code compatibility instantiation.

2018-11-08 18:48:25,798 main ERROR Channel:4103 - Sending proposal to peer1.domain.com failed because of timeout(120000 milliseconds) expiration
java.util.concurrent.TimeoutException
at org.hyperledger.fabric.sdk.Channel.sendProposalToPeers(Channel.java:4086)
at org.hyperledger.fabric.sdk.Channel.sendInstantiationProposal(Channel.java:2501)
at org.hyperledger.fabric.sdkintegration.End2endIT_custom_java.runChannel(End2endIT_custom_java.java:473)


2018-11-08 21:24:19.099 UTC [core/comm] ServerHandshake -> ERRO 0a6 TLS handshake failed with error EOF {"server": "PeerServer", "remote address": "172.20.0.9:33462"}
2018-11-08 21:24:19.804 UTC [endorser] SimulateProposal -> ERRO 0a7 [channel][7c4fa0e2] failed to invoke chaincode name:"lscc" , error: timeout expired while starting chaincode SimpleChaincode:1 for transaction

而链上的代码工作得很好,代码上没有其他区别 安装正常,实例化Java chaincode总是超时 2018-11-08 20:48:27.686 UTC [lscc] executeInstall-> INFO 031已安装Chaincode [SimpleChaincode]版本[1]进行对等

Whereas go chain code works perfectly fine, no other difference in code Install works fine, instantiate Java chaincode always times out 2018-11-08 20:48:27.686 UTC [lscc] executeInstall -> INFO 031 Installed Chaincode [SimpleChaincode] Version [1] to peer

仅在具有相同日志的java链代码实例化中一次又一次地可重现,go链代码实例化可以正常工作: https://hastebin.com/osafazisaj.rb

Reproducible again and again only with java chaincode instantiation with same logs, go chaincode instantiate works fine: https://hastebin.com/osafazisaj.rb

当我从Kafka切换到SOLO Orderer时,我得到了一个更好的和不同的例外,因为偶尔Kafka Orderer会冻结,从而导致docker网络饱和? 切换到SOLO会引发错误: 无法调用链码名称:"lscc",错误:执行事务时超时已过期

when I switch from Kafka to SOLO orderer, I get a better and different exception, as occassionally Kafka orderer would freeze causing docker network saturation? Switching to SOLO throws the error: failed to invoke chaincode name:"lscc" , error: timeout expired while executing transaction

https://hastebin.com/konoqewofe.md

这篇关于在Hyperledger Fabric v1.3中实例化Java链码的问题-无法调用链码名称:"lscc".的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆