Checking the Java SDK Application Demo

Updated on 2022-11-16 GMT+08:00

View PDF

Fault Locating

Check whether the BCS instance is named java-sdk-demo, uses the Enterprise edition if the security mechanism is OSCCA-published cryptographic algorithms, is a private blockchain deployed in a CCE cluster, and uses SOLO for the consensus mechanism.
NOTE:

Ensure that the development tools have been correctly installed and configured. For details, see Preparation.

To check these details, log in to the BCS console, go to the Instance Management page, and click the target instance to view its details. For details about the configurations required for this demo, see Java SDK Demo.

Check whether the orderer and peer certificates have been downloaded, and whether the SDK file (java-sdk-demo-sdk-config.zip) has been downloaded to the config directory of the demo project. For details, see sections "Download the SDK configuration" and "Download certificates" under Configuring the Application.
NOTE:

The chaincode name specified when you set the SDK file parameters must be the same as that specified during chaincode installation.
Check whether the path of the Main class has been changed as required. For details, see Deploying the Application.
Find the Main.java file in the /javasdkdemo/src/main/java/handler/ directory, and change the file path in the following code of the Main class to the absolute path of the java-sdk-demo-sdk-config.yaml file. Change the backslashes (\) to slashes (/).

helper.setConfigCtx("E:/yourdir/huawei.yaml");
If the BCS instance uses OSCCA-published cryptographic algorithms, check whether the dependency upon fabric-sdk-java-1.4.1-jar-with-dependencies.jar is added to pom.xml. To add the dependency, remove the comments on the dependency as shown in the following figure.
If timeout occurs occasionally and the transaction interval is long, check whether the fault is caused by the connection protection mechanism of a third-party gRPC. The following figure shows the error information.

Solution

In the src\main\java\handler\FabricHelper.java file, add p.put to the sample code as shown in the following figure. Save the code and perform the transaction again.

Click to enlarge

p.put("grpc.NettyChannelBuilderOption.keepAliveTime", new Object[] {5L, TimeUnit.MINUTES});

p.put("grpc.NettyChannelBuilderOption.keepAliveTimeout", new Object[] {8L, TimeUnit.SECONDS});

p.put("grpc.NettyChannelBuilderOption.keepAliveWithoutCalls", new Object[] {true});

p.put("grpc.NettyChannelBuilderOption.maxInboundMessageSize", 102400000);

Parent topic: Demo Problems

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot