corda

How do I stop the node from printing the node.conf in the logs? I understand we can change the logging level since the node.conf is printed at INFO level, but I want to avoid that as much as possible since I still want some other information that is at INFO level to be printed out. The contents of node.conf are printed at INFO level by the net.corda.node.services.config.ConfigHelper class. To prevent the contents of node.conf from being printed to the logs, you'd have to specify a custom logging configuration so that for the net.corda.node.services.config.ConfigHelper class, only messages at

I have a one-to-many relationship where I am trying to add a list of object/class in my state. i.e I have a contract state that has a list of attachments List<Attachment> , where Attachment is just a class with fields like attachmentHash , uploadedDate , fileType I wanted to query with something in the child but I get syntax error "AttachmentEntity is not a subtype of PersistentState" QueryCriteria.VaultCustomQueryCriteria( builder { (ContractSchemaV1.AttachmentEntity::uploadDate).equal(givenDate) })) I let AttachmentEntity be a subclass of PersistentState and the node started up with the

We have a use case which requires the following steps: (1) Initiator triggers the transaction flow through UI (2) The flow is initiated, signed by the initiator and sent to recipient for his verification and signatures (in Corda) (3) The initiator's flow should get suspended until the recipient validates the transaction by verifying the contract code and submits "verified" again through the UI (4) This should restart the initiator's flow and the remaining process should be followed as expected in Corda It was mentioned a few weeks back that user interaction is not yet supported in Corda; is

We have developed an app, which creates obligations in vault in a table. If the row size of the table is less than 200, the application works fine. However, if the rows are more than 200 then during the execution it gives the following error - Please specify a PageSpecification as there are more results [201] than the default page size [200] After increasing the pagination to 400 from the default 200, I am getting java heap out of memory error. I tired to increase the heap size of node from 512m (default) to 1024m. But, still this issue is not resolved and I am getting the error in H2 DB-

I have the following series of flows: Initiator , my initiating flow AliceFlow , which one counterparty uses to respond to Initiator BobFlow , which the other counterparty uses to respond to Initiator Normally, the two response flows would be defined in separate CorDapps. However, for testing purposes, I have defined them in the same file. When I run flow tests, I get the error below. How can I fix this? java.lang.IllegalArgumentException: com.template.Initiator has been specified as the initiating flow by both com.template.BobResponder and com.template.AliceResponder You need to define your

Setting up the Notary Service for Oracle RAC (Corda Enterprise). I need some help configuring Corda Enterprise in Oracle RAC (reference: "Highly Available Notary Service - Setting up the Notary Service": http://docs.corda.r3.com/running-a-notary-cluster/installing-the-notary-service.html ). Regarding the "msql" tag, is it possible to configure an Oracle RAC? Is there an "oracle" tag? In the "notary" tag's "serviceLegalName" parameter where should I put the name of the Notary that the Nodes see (name of the Notary in NetworkMap)? "O = HA Notary" For Oracle RAC can I follow this pattern? http:/