Date   

Event: Caliper Project Quarterly Update Due #tsc-project-update - Thursday, December 8, 2022 #tsc-project-update #cal-reminder

Group Notification <noreply@...>
 

Reminder: Caliper Project Quarterly Update Due #tsc-project-update

When:
Thursday, December 8, 2022

Organizer: community-architects@...

View Event

Description:
Please file a project status report for the TSC here:

https://wiki.hyperledger.org/display/TSC/2022+Project+Updates

https://wiki.hyperledger.org/display/TSC/2022+TSC+Project+Update+Calendar


need help to test performace of ethereum using smartcontracts

hippie
 

hey have anyone used hyperledger calliper before to teste performance of ethereum , if so can u help with the same


Re: Problem with messenger mqtt

Attila Klenik
 

Hi!

Here's the doc for configuring the MQTT service: https://hyperledger.github.io/caliper/v0.5.0/caliper-messengers/
Also, enabling debug messages could be useful if the error persists: https://hyperledger.github.io/caliper/v0.5.0/logging/

Best Regards,
Attila Klenik


Re: Problem with messenger mqtt

andZka
 

Update: The error during testing seems to no longer appear, however the launch manager is stuck at messenger setup:
[caliper] [worker-orchestrator] Messenger not configured, entering configure phase...
Meanwhile the workers get stuck at set SUT type.


Problem with messenger mqtt

andZka
 

Hi everyone! I would like to do a test connecting multiple machines for clients. Before I do that, I'm doing a test first with workers communicating via mqtt on localhost.
I wrote a docker compose file to do this using mosquitto as the message broker:
https://github.com/andreaZka/test/blob/main/docker-compose.yml
Here the mosquitto.conf:
https://github.com/andreaZka/test/blob/main/mosquitto/mosquitto.conf
However, there is an error in the testing phase:

Error while performing "test" step: TypeError: moduleName.startsWith is not a function
at Function.loadModuleFunction (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-core/lib/common/utils/caliper-utils.js:152:31)
at new WorkerOrchestrator (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-core/lib/manager/orchestrators/worker-orchestrator.js:56:47)
at new RoundOrchestrator (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-core/lib/manager/orchestrators/round-orchestrator.js:40:35)
at CaliperEngine.run (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-core/lib/manager/caliper-engine.js:152:43)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async Function.handler (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-cli/lib/launch/lib/launchManager.js:62:30)

This occurs equally in both the process manager and the workers.
The connector is custom but run in a single container, it works fine.
What happens, what is this error due to?
andZka


Re: Custom connector

Attila Klenik
 

Hi! 

It's good to hear that you're writing a custom connector for Caliper. If you'd like to share any feedback with us, you can do so here or in the Caliper contributor discord channel after registration (https://discord.com/channels/905194001349627914/941417722946924554).

To answer your question with concrete examples:
  1. The Caliper manager process will call your connector's prepareWorkerArguments function (after initializing the connector through its init function), passing it the number of configured workers as a parameter.
  2. The function can return arbitrary objects for each worker as an array (each element corresponds to a worker). For example, the Ethereum connector's implementation returns the same object for all workers, namely the detailed information of deployed contracts (https://github.com/hyperledger/caliper/blob/91870b7e51425ecc472e3c114eadee3026d18d42/packages/caliper-ethereum/lib/ethereum-connector.js#L421-L427)
  3. Then, before every round, your connector's getContext function is called on every worker (Ethereum connector example: https://github.com/hyperledger/caliper/blob/91870b7e51425ecc472e3c114eadee3026d18d42/packages/caliper-ethereum/lib/ethereum-connector.js#L146). The args parameter is the worker's corresponding object/element from the above array. You process it in any way you want; for example, save it in a class instance variable (once, on the first getContext call) and use the data from the _sendSingleRequest function.

I hope the above explanation clarifies things; let us know if you need further help (either here or in the discord channel)!

Best Regards,
Attila


Custom connector

andZka
 

Hi all,
I created a custom connector to benchmark the Cosmos blockchain.
The connector works but the preparation phase is currently slow due to the fact that the creation of identities for testing is done in the getContext function and therefore is performed by every worker.
By inserting this process into other functions, digital identities are not found by workers.
My intention is to effect the creation of the accounts in the init function by the process manager and then distribute it to the workers with the prepareWorkerArguments function, as suggested among other things by the documentation on the writing-connectors page: https://hyperledger.github.io/caliper/v0.5.0/writing-connectors/
However, I did not understand how these objects returned by the prepareWorkerArguments function can be used by workers, I also checked the code of the connectors already implemented but I could not find concrete examples.
For example, given the result object returned by the prepareWorkerArguments function, how can I use it in the _sendSingleRequest function?
andZka


Hyperledger TOC Election Call for Nominations process closes on Oct 31

David Boswell
 

As a reminder, the Technical Oversight Committee (TOC) election will happen from November 1 to 30, 2022 and we are currently accepting nominations for people who would like to run in the election.

Note that the nomination process will close on October 31 at the end of the day Pacific time, so if you are considering running in the election make sure to submit your nomination before then.

To nominate yourself use the following email template with the subject line "TOC election nomination" and send it to election-2022@...:

Dear Election Committee,

I nominate myself for the TOC election. My email address is <email> and my GitHub ID is <github id>.

The contributions that I have had to the Hyperledger Foundation in the past year are (please check all that apply)
- code contribution to project/lab
- maintainer of project/lab
- TOC Member
- Lab Steward
- SIG leader
- Task Force leader
- Other (please provide details)

Thanks,

<your name>

After you have emailed your nomination, please also create a nomination statement on the Hyperledger Github repo and include the following information: nominee name, short personal bio and a short personal pitch about why someone should consider voting for you.

If you have any questions about the election process, please feel free to write to election-2022@....

Thanks,

Hyperledger staff


Hyperledger TOC Election Call for Nominations

David Boswell
 

This year's Hyperledger Technical Oversight Committee (TOC) election will happen from November 1 to 30, 2022.  Note that Hyperledger's Technical Steering Committee has recently been renamed to Technical Oversight Committee.

The election will include active contributors who have nominated themselves to run as candidates – check to see if you are eligible to run if you are unsure.  We are now opening the call for nominations and this process will go through October 31 at the end of the day Pacific time.

To nominate yourself use the following email template with the subject line "TOC election nomination" and send it to election-2022@...:

Dear Election Committee,

I nominate myself for the TOC election. My email address is <email> and my GitHub ID is <github id>.

The contributions that I have had to the Hyperledger Foundation in the past year are (please check all that apply)
- code contribution to project/lab
- maintainer of project/lab
- TOC Member
- Lab Steward
- SIG leader
- Task Force leader
- Other (please provide details)

Thanks,

<your name>

After you have emailed your nomination, please also create a nomination statement on the Hyperledger Github repo and include the following information: nominee name, short personal bio and a short personal pitch about why someone should consider voting for you.

If you have any questions about the election process, please feel free to write to election-2022@....

Thanks,

Hyperledger staff


Now: Caliper Project Quarterly Update Due #tsc-project-update - 09/22/2022 #tsc-project-update #cal-notice

Group Notification <noreply@...>
 

Caliper Project Quarterly Update Due #tsc-project-update

When:
09/22/2022

Organizer: community-architects@...

View Event

Description:
Please file a project status report for the TSC here:

https://wiki.hyperledger.org/display/TSC/2022+Project+Updates

https://wiki.hyperledger.org/display/TSC/2022+TSC+Project+Update+Calendar


Event: Caliper Project Quarterly Update Due #tsc-project-update - 09/22/2022 #tsc-project-update #cal-reminder

Group Notification <noreply@...>
 

Reminder: Caliper Project Quarterly Update Due #tsc-project-update

When:
09/22/2022

Organizer: community-architects@...

View Event

Description:
Please file a project status report for the TSC here:

https://wiki.hyperledger.org/display/TSC/2022+Project+Updates

https://wiki.hyperledger.org/display/TSC/2022+TSC+Project+Update+Calendar


Caliper: parameter

divya.v@...
 

Hi
I have few doubt in caliper, it will be helpful if any one could help
1. What is master and worker
2. Some parameters in intialize module like no of worker, rounds etc
Thank you
V. V. Divya


Odd issue with write transactions #fabric

mhdalkhaldibc@...
 

Hello all,

I'm facing an odd issue. My workload module looks like this:
'use strict';

const { WorkloadModuleBase } = require('@hyperledger/caliper-core');

class MyWorkload extends WorkloadModuleBase {
constructor() {
super();
this.txIndex = 0;
}

async initializeWorkloadModule(workerIndex, totalWorkers, roundIndex, roundArguments, sutAdapter, sutContext) {
await super.initializeWorkloadModule(workerIndex, totalWorkers, roundIndex, roundArguments, sutAdapter, sutContext);
 
for (let i=0; i<this.roundArguments.assets; i++) {
const assetID = `${this.workerIndex}_${i}`;
console.log(`Worker ${this.workerIndex}: Creating asset ${assetID}`);
const request = {
contractId: this.roundArguments.contractId,
contractFunction: 'CreateAsset',
invokerIdentity: 'User1',
contractArguments: [assetID,'blue','20','penguin','500'],
readOnly: false
};
console.log(`request create: `, request);


await this.sutAdapter.sendRequests(request);
}
}

async submitTransaction() {
this.txIndex++;
const request = {
contractId: this.roundArguments.contractId,
contractFunction: 'CreateAsset',
invokerIdentity: 'User1',
contractArguments: [this.txIndex,'blue','20','penguin','500'],
readOnly: false
};
await this.sutAdapter.sendRequests(request);
 
}
....
 
As you see in the submitTransaction part I'm sending a write tx. while read txs worked fine before, write txs are failing with error:
error [caliper] [connectors/v2/FabricGateway] Failed to perform submit transaction [CreateAsset] using arguments [3,blue,20,penguin,500],  with error: Error: No endorsement plan available
 
From the peer logs perspective, the error shown is:
[core.comm] ServerHandshake -> ERRO c49 Server TLS handshake failed in 335.049198ms with error EOF server=PeerServer remoteaddress=
 
What is confusing to me is that in the initializeWorkloadModule part of the workload module, Caliper is sending write transactions and creating assets successfully without any issues. If it was a tls issue as it appears it should always fail, right?
 
Any ideas?
Thanks


Re: error in chaincode execution

Attila Klenik
 

Hi there!

This error originates from your chaincode (a null pointer exception, based on the logs) that results in a failed endorsement. Caliper just reports this fact.
Try to add more logging and input checks to your chaincode to identify the location of the error. You could use the [0_0, testHash, "here i have a complex string generated by an XML document"] arguments as a test input for debugging this problem.

Anyway, the Caliper side cannot cause this behavior (which is a chaincode bug), Caliper just provides the inputs based on your workload module.

Best Regards,
Attila Klenik


error in chaincode execution

famar
 

Hi all, I am having problems running chaincode during caliper testing. I have confidence that my chaincode is correct since I created an app with the JAVA sdk and I can both write and read from the ledger via the appropriate transactions.  The error that caliper gives me is as follows:

 

Failed to perform submit transaction [createClinicalDocument] using arguments [0_0, testHash, "here i have a complex string generated by an XML document"]

with error: EndorseError: 10 ABORTED: failed to endorse transaction, see attached details for more info

Details:

-  peer0.org1.example.com:7051:chaincode response 500, Error during contract method execution

This is the log of the peer:

Thread[fabric-txinvoke:1,5,main] 08:53:03:191 INFO    org.hyperledger.fabric.contract.ContractRouter processRequest                    Got routing:createClinicalDocument:org.example.PatientSummaryUpdateContract

Thread[fabric-txinvoke:3,5,main] 08:53:03:202 SEVERE  org.hyperledger.fabric.Logger error                                              Error during contract method executionorg.hyperledger.fabric.contract.ContractRuntimeException: Error during contract method execution

at org.hyperledger.fabric.contract.execution.impl.ContractExecutionService.executeRequest(ContractExecutionService.java:79)

at org.hyperledger.fabric.contract.ContractRouter.processRequest(ContractRouter.java:123)

at org.hyperledger.fabric.contract.ContractRouter.invoke(ContractRouter.java:134)

at org.hyperledger.fabric.shim.impl.ChaincodeInvocationTask.call(ChaincodeInvocationTask.java:106)

at org.hyperledger.fabric.shim.impl.InvocationTaskManager.lambda$newTask$17(InvocationTaskManager.java:265)

at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:834)

Caused by: java.lang.NullPointerException

at org.example.PatientSummaryUpdateContract.createClinicalDocument(PatientSummaryUpdateContract.java:194)

at jdk.internal.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:566)

at org.hyperledger.fabric.contract.execution.impl.ContractExecutionService.executeRequest(ContractExecutionService.java:61)

... 8 more

.. caused by ..nulljava.lang.NullPointerException

at org.example.PatientSummaryUpdateContract.createClinicalDocument(PatientSummaryUpdateContract.java:194)

at jdk.internal.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:566)

at org.hyperledger.fabric.contract.execution.impl.ContractExecutionService.executeRequest(ContractExecutionService.java:61)

at org.hyperledger.fabric.contract.ContractRouter.processRequest(ContractRouter.java:123)

at org.hyperledger.fabric.contract.ContractRouter.invoke(ContractRouter.java:134)

at org.hyperledger.fabric.shim.impl.ChaincodeInvocationTask.call(ChaincodeInvocationTask.java:106)

at org.hyperledger.fabric.shim.impl.InvocationTaskManager.lambda$newTask$17(InvocationTaskManager.java:265)

at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:834)

 

Thread[fabric-txinvoke:3,5,main] 08:53:03:202 SEVERE  org.hyperledger.fabric.shim.impl.ChaincodeInvocationTask call                    [6c24afbc] Invoke failed with error code 500. Sending ERROR

Thread[fabric-txinvoke:5,5,main] 08:53:03:209 SEVERE  org.hyperledger.fabric.Logger error                                              Error during contract method executionorg.hyperledger.fabric.contract.ContractRuntimeException: Error during contract method execution

at org.hyperledger.fabric.contract.execution.impl.ContractExecutionService.executeRequest(ContractExecutionService.java:79)

at org.hyperledger.fabric.contract.ContractRouter.processRequest(ContractRouter.java:123)

at org.hyperledger.fabric.contract.ContractRouter.invoke(ContractRouter.java:134)

at org.hyperledger.fabric.shim.impl.ChaincodeInvocationTask.call(ChaincodeInvocationTask.java:106)

at org.hyperledger.fabric.shim.impl.InvocationTaskManager.lambda$newTask$17(InvocationTaskManager.java:265)

at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:834)

Caused by: java.lang.NullPointerException

at org.example.PatientSummaryUpdateContract.createClinicalDocument(PatientSummaryUpdateContract.java:194)

at jdk.internal.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:566)

at org.hyperledger.fabric.contract.execution.impl.ContractExecutionService.executeRequest(ContractExecutionService.java:61)

... 8 more

.. caused by ..nulljava.lang.NullPointerException

at org.example.PatientSummaryUpdateContract.createClinicalDocument(PatientSummaryUpdateContract.java:194)

at jdk.internal.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:566)

at org.hyperledger.fabric.contract.execution.impl.ContractExecutionService.executeRequest(ContractExecutionService.java:61)

at org.hyperledger.fabric.contract.ContractRouter.processRequest(ContractRouter.java:123)

at org.hyperledger.fabric.contract.ContractRouter.invoke(ContractRouter.java:134)

at org.hyperledger.fabric.shim.impl.ChaincodeInvocationTask.call(ChaincodeInvocationTask.java:106)

at org.hyperledger.fabric.shim.impl.InvocationTaskManager.lambda$newTask$17(InvocationTaskManager.java:265)

at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:834)

 

Thread[fabric-txinvoke:5,5,main] 08:53:03:210 SEVERE  org.hyperledger.fabric.shim.impl.ChaincodeInvocationTask call                    [823aacac] Invoke failed with error code 500. Sending ERROR

Thread[fabric-txinvoke:2,5,main] 08:53:03:210 SEVERE  org.hyperledger.fabric.Logger error                                              Error during contract method executionorg.hyperledger.fabric.contract.ContractRuntimeException: Error during contract method execution

at org.hyperledger.fabric.contract.execution.impl.ContractExecutionService.executeRequest(ContractExecutionService.java:79)

at org.hyperledger.fabric.contract.ContractRouter.processRequest(ContractRouter.java:123)

at org.hyperledger.fabric.contract.ContractRouter.invoke(ContractRouter.java:134)

at org.hyperledger.fabric.shim.impl.ChaincodeInvocationTask.call(ChaincodeInvocationTask.java:106)

at org.hyperledger.fabric.shim.impl.InvocationTaskManager.lambda$newTask$17(InvocationTaskManager.java:265)

at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:834)

Caused by: java.lang.NullPointerException

at org.example.PatientSummaryUpdateContract.createClinicalDocument(PatientSummaryUpdateContract.java:194)

at jdk.internal.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:566)

at org.hyperledger.fabric.contract.execution.impl.ContractExecutionService.executeRequest(ContractExecutionService.java:61)

... 8 more

.. caused by ..nulljava.lang.NullPointerException

at org.example.PatientSummaryUpdateContract.createClinicalDocument(PatientSummaryUpdateContract.java:194)

at jdk.internal.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:566)

at org.hyperledger.fabric.contract.execution.impl.ContractExecutionService.executeRequest(ContractExecutionService.java:61)

at org.hyperledger.fabric.contract.ContractRouter.processRequest(ContractRouter.java:123)

at org.hyperledger.fabric.contract.ContractRouter.invoke(ContractRouter.java:134)

at org.hyperledger.fabric.shim.impl.ChaincodeInvocationTask.call(ChaincodeInvocationTask.java:106)

at org.hyperledger.fabric.shim.impl.InvocationTaskManager.lambda$newTask$17(InvocationTaskManager.java:265)

at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:834)

 

Thread[fabric-txinvoke:2,5,main] 08:53:03:212 SEVERE  org.hyperledger.fabric.shim.impl.ChaincodeInvocationTask call                    [4e1c0fa5] Invoke failed with error code 500. Sending ERROR

Thread[fabric-txinvoke:1,5,main] 08:53:03:215 SEVERE  org.hyperledger.fabric.Logger error                                              Error during contract method executionorg.hyperledger.fabric.contract.ContractRuntimeException: Error during contract method execution

at org.hyperledger.fabric.contract.execution.impl.ContractExecutionService.executeRequest(ContractExecutionService.java:79)

at org.hyperledger.fabric.contract.ContractRouter.processRequest(ContractRouter.java:123)

at org.hyperledger.fabric.contract.ContractRouter.invoke(ContractRouter.java:134)

at org.hyperledger.fabric.shim.impl.ChaincodeInvocationTask.call(ChaincodeInvocationTask.java:106)

at org.hyperledger.fabric.shim.impl.InvocationTaskManager.lambda$newTask$17(InvocationTaskManager.java:265)

at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:834)

Caused by: java.lang.NullPointerException

at org.example.PatientSummaryUpdateContract.createClinicalDocument(PatientSummaryUpdateContract.java:194)

at jdk.internal.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:566)

at org.hyperledger.fabric.contract.execution.impl.ContractExecutionService.executeRequest(ContractExecutionService.java:61)

... 8 more

.. caused by ..nulljava.lang.NullPointerException

at org.example.PatientSummaryUpdateContract.createClinicalDocument(PatientSummaryUpdateContract.java:194)

at jdk.internal.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:566)

at org.hyperledger.fabric.contract.execution.impl.ContractExecutionService.executeRequest(ContractExecutionService.java:61)

at org.hyperledger.fabric.contract.ContractRouter.processRequest(ContractRouter.java:123)

at org.hyperledger.fabric.contract.ContractRouter.invoke(ContractRouter.java:134)

at org.hyperledger.fabric.shim.impl.ChaincodeInvocationTask.call(ChaincodeInvocationTask.java:106)

at org.hyperledger.fabric.shim.impl.InvocationTaskManager.lambda$newTask$17(InvocationTaskManager.java:265)

at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:834)

 

Thread[fabric-txinvoke:1,5,main] 08:53:03:215 SEVERE  org.hyperledger.fabric.shim.impl.ChaincodeInvocationTask call                    [a1a085a9] Invoke failed with error code 500. Sending ERROR

Thread[fabric-txinvoke:3,5,main] 08:53:03:227 INFO    org.hyperledger.fabric.contract.ContractRouter processRequest                    Got invoke routing request

Thread[fabric-txinvoke:3,5,main] 08:53:03:228 INFO    org.hyperledger.fabric.contract.ContractRouter processRequest                    Got the invoke request for:createClinicalDocument [0_0, testHash,"same string as before"]

 


Re: Question: Is the Caliper able to work only local? Performance issue

Attila Klenik
 

Dear Sangwoo Park,

Caliper can also be used in distributed mode, meaning that the manager and worker processes are deployed on separate (virtual) machines.
Take a look at the relevant doc page/section: https://hyperledger.github.io/caliper/v0.5.0/architecture/#distributed-message-broker-communication

You can also find an example setup in the Caliper repository: https://github.com/hyperledger/caliper/blob/main/packages/caliper-tests-integration/fabric_docker_distributed_tests/docker-compose.yaml#L268

Even though this is a local setup (everything is running on the same machine), the different Caliper-related services are configured independently. So it's easy to, for example, transform the above local Docker setup to a distributed Docker Swarm setup (or a Kubernetes one), the principles are the same. 

Best regards,
Attila Klenik


Question: Is the Caliper able to work only local? Performance issue

SANGWOO PARK
 

Hello, experts!
I am researching about the Performance of Hyperledger Fabric with the Caliper.
Today, I suddenly thought about something good idea to upgrade the performance of the Read/Write set TPS.

On the first step of using the Caliper, we usually install it and run it on the local which means using a computer resources.
So, I thought about using two different computers to run the TPS test with the Caliper. Thus, we able to utilize two computers resources which is twice bigger than a computer.

However, I have no idea how to remotely connect the Caliper and blockchain network in two different individual computer.
Question 1. Is it even possible to work as my idea?
Question 2. If do so, do you know how to make this kind of testing environment?

I will be really appreciated if you answer my questions.

Thank you
SANGWOO PARK
Best regard,
sangwoopark1218@...
+82-10-4953-1218


Updated Event: Hyperledger Caliper Contributors Meeting #cal-invite

Group Notification <noreply@...>
 

Hyperledger Caliper Contributors Meeting

When:
Wednesday, July 20, 2022
1:00pm to 2:00pm
(UTC+00:00) UTC
Repeats: Every 4 weeks on Wednesday

Where:
https://zoom.us/my/hyperledger.community?pwd=STZQd0xMZU9xRVVOVnpQM3JNQ2dqZz09

Organizer: Attila Klenik

View Event

Description:
Contact: Attila Klenik (Discord: klenik#9902)

Join Zoom Meeting
https://zoom.us/j/4034983298?pwd=STZQd0xMZU9xRVVOVnpQM3JNQ2dqZz09

Meeting ID: 403 498 3298
Passcode: 475869


Now: Caliper Project Quarterly Update Due #tsc-project-update - 06/23/2022 #tsc-project-update #cal-notice

Group Notification <noreply@...>
 

Caliper Project Quarterly Update Due #tsc-project-update

When:
06/23/2022

Organizer: community-architects@...

View Event

Description:
Please file a project status report for the TSC here:

https://wiki.hyperledger.org/display/TSC/2022+Project+Updates

https://wiki.hyperledger.org/display/TSC/2022+TSC+Project+Update+Calendar


Event: Caliper Project Quarterly Update Due #tsc-project-update - 06/23/2022 #tsc-project-update #cal-reminder

Group Notification <noreply@...>
 

Reminder: Caliper Project Quarterly Update Due #tsc-project-update

When:
06/23/2022

Organizer: community-architects@...

View Event

Description:
Please file a project status report for the TSC here:

https://wiki.hyperledger.org/display/TSC/2022+Project+Updates

https://wiki.hyperledger.org/display/TSC/2022+TSC+Project+Update+Calendar

1 - 20 of 180