You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 22, 2021. It is now read-only.
We are using the SDK to connect to Amazon Managed Blockchain but the following error occurs:
java.lang.Exception: java.lang.IllegalArgumentException: Input byte array has incorrect ending byte at 1748
at org.hyperledger.fabric.sdk.Channel.sendProposalToPeers(Channel.java:4140)
at org.hyperledger.fabric.sdk.Channel.getConfigBlock(Channel.java:858)
at org.hyperledger.fabric.sdk.Channel.parseConfigBlock(Channel.java:1781)
at org.hyperledger.fabric.sdk.Channel.loadCACertificates(Channel.java:1618)
at org.hyperledger.fabric.sdk.Channel.initialize(Channel.java:1107)
atcom.transfesa.traceability.providers.DefaultChannelProvider.getLogisticChannelClient(DefaultChannelProvider.java:81)
at com.transfesa.traceability.services.ChannelService.getChainInfo(ChannelService.java:99)
at com.transfesa.traceability.controllers.ChainInfoController.getChainInfo(ChainInfoController.java:25)
We think that the error is because the certificate file supplied by Amazon (managedblockchain-tls-chain.pem) has two certificates when the normal is one. But this is a file supplied by Amazon.
Is it possible that the SDK is not able to handle a file with two certificates and needs only one?
Thanks
The text was updated successfully, but these errors were encountered:
@Steampunk1453 ,
the SDK is not able to handle a file with two certificates and needs only one - you can try deleting one certificate in that file and test to be sure.
If it works, then we may need to modify certificate file before using.
Ok, thanks. Now we use the managedblockchain-tls-chain.pem certificate file with the property "pemFile" and we have not the "Input byte array" error but we have "UNKNOWN: access denied" when we try to connect SDK with Amazon Managed Blockchain
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We are using the SDK to connect to Amazon Managed Blockchain but the following error occurs:
java.lang.Exception: java.lang.IllegalArgumentException: Input byte array has incorrect ending byte at 1748
at org.hyperledger.fabric.sdk.Channel.sendProposalToPeers(Channel.java:4140)
at org.hyperledger.fabric.sdk.Channel.getConfigBlock(Channel.java:858)
at org.hyperledger.fabric.sdk.Channel.parseConfigBlock(Channel.java:1781)
at org.hyperledger.fabric.sdk.Channel.loadCACertificates(Channel.java:1618)
at org.hyperledger.fabric.sdk.Channel.initialize(Channel.java:1107)
atcom.transfesa.traceability.providers.DefaultChannelProvider.getLogisticChannelClient(DefaultChannelProvider.java:81)
at com.transfesa.traceability.services.ChannelService.getChainInfo(ChannelService.java:99)
at com.transfesa.traceability.controllers.ChainInfoController.getChainInfo(ChainInfoController.java:25)
We think that the error is because the certificate file supplied by Amazon (managedblockchain-tls-chain.pem) has two certificates when the normal is one. But this is a file supplied by Amazon.
Is it possible that the SDK is not able to handle a file with two certificates and needs only one?
Thanks
The text was updated successfully, but these errors were encountered: