If a connector is already registered in a broker, and then sends a second update connector, the triplestore of the broker clears.
Broker Version is v4.2.8 .
A has a connector (DSC) and send an update message to broker
A creates a resource,distribution,artifact,contract in their connector, and sends a resource update message to broker
B sends a query message from their own connector, and they see the resource added by A
C also has a connector (DSC) and sends an update message to the broker
C also has a connector (DSC) and sends another update message to the broker
broker logs after this:
10:16:49.393 [http-nio-8080-exec-1] WARN de.fraunhofer.iais.eis.ids.component.core.MessageDispatcher - No security token verifier set. Use setSecurityTokenVerifier method.
10:16:49.393 [http-nio-8080-exec-1] INFO de.fraunhofer.iais.eis.ids.component.core.logging.MessageLogger - ConnectorUpdateMessage received from https://w3id.org/idsa/autogen/baseConnector/provider (called by de.fraunhofer.iais.eis.ids.component.core.logging.MessageLogger)
affectedConnector: https://w3id.org/idsa/autogen/baseConnector/provider
10:16:49.393 [http-nio-8080-exec-1] INFO de.fraunhofer.iais.eis.ids.component.core.logging.MessageLogger - Payload hash: 1636056658
10:16:49.430 [http-nio-8080-exec-1] INFO de.fraunhofer.iais.eis.ids.broker.core.common.persistence.SelfDescriptionPersistenceAndIndexing - Updating a connector which is already known to the broker: http://central-core:8282/connectors/1012493422
10:16:49.484 [http-nio-8080-exec-1] INFO de.fraunhofer.iais.eis.ids.index.common.persistence.RepositoryFacade - Changing passivation of graph http://central-core:8282/connectors/1012493422. Is now active: true
10:16:49.540 [http-nio-8080-exec-1] INFO de.fraunhofer.iais.eis.ids.index.common.persistence.NullIndexing - Index update IGNORED.
Fuseki log after this
[2022-04-06 10:24:21] Fuseki INFO [6160] GET http://broker-fuseki:3030/connectorData/sparql?query=ASK+FROM+NAMED+%3Chttps%3A%2F%2Fbroker.ids.isst.fraunhofer.de%2Fadmin%3E+WHERE+%7B+GRAPH+%3Fg+%7B+%3Chttp%3A%2F%2Fcentral-core%3A8282%2Fconnectors%2F1012493422%3E+%3Chttps%3A%2F%2Fw3id.org%2Fidsa%2Fcore%2FgraphIsActive%3E+true+.+%7D+%7D+
[2022-04-06 10:24:21] Fuseki INFO [6160] Query = ASK FROM NAMED <https://broker.ids.isst.fraunhofer.de/admin> WHERE { GRAPH ?g { <http://central-core:8282/connectors/1012493422> <https://w3id.org/idsa/core/graphIsActive> true . } }
[2022-04-06 10:24:21] Fuseki INFO [6160] 200 OK (2 ms)
[2022-04-06 10:24:21] Fuseki INFO [6161] GET http://broker-fuseki:3030/connectorData/sparql?query=ASK+FROM+NAMED+%3Chttp%3A%2F%2Fcentral-core%3A8282%2Fconnectors%2F1012493422%3E+WHERE+%7B+GRAPH+%3Chttp%3A%2F%2Fcentral-core%3A8282%2Fconnectors%2F1012493422%3E+%7B+%3Fs+%3Fp+%3Fo+.+%7D+%7D+
[2022-04-06 10:24:21] Fuseki INFO [6161] Query = ASK FROM NAMED <http://central-core:8282/connectors/1012493422> WHERE { GRAPH <http://central-core:8282/connectors/1012493422> { ?s ?p ?o . } }
[2022-04-06 10:24:21] Fuseki INFO [6161] 200 OK (3 ms)
[2022-04-06 10:24:21] Fuseki INFO [6162] POST http://broker-fuseki:3030/connectorData
[2022-04-06 10:24:21] Fuseki INFO [6162] Update
[2022-04-06 10:24:21] Fuseki INFO [6162] 204 No Content (23 ms)
[2022-04-06 10:24:21] Fuseki INFO [6163] POST http://broker-fuseki:3030/connectorData
[2022-04-06 10:24:21] Fuseki INFO [6163] Update
[2022-04-06 10:24:21] Fuseki INFO [6163] 204 No Content (26 ms)
[2022-04-06 10:24:21] Fuseki INFO [6164] GET http://broker-fuseki:3030/connectorData/sparql?query=ASK+FROM+NAMED+%3Chttp%3A%2F%2Fcentral-core%3A8282%2Fconnectors%2F1012493422%3E+WHERE+%7B+GRAPH+%3Chttp%3A%2F%2Fcentral-core%3A8282%2Fconnectors%2F1012493422%3E+%7B+%3Fs+%3Fp+%3Fo+.+%7D+%7D+
[2022-04-06 10:24:21] Fuseki INFO [6164] Query = ASK FROM NAMED <http://central-core:8282/connectors/1012493422> WHERE { GRAPH <http://central-core:8282/connectors/1012493422> { ?s ?p ?o . } }
[2022-04-06 10:24:21] Fuseki INFO [6164] 200 OK (4 ms)
[2022-04-06 10:24:21] Fuseki INFO [6165] GET http://broker-fuseki:3030/connectorData/sparql?query=CONSTRUCT+%7B+%3Chttp%3A%2F%2Fcentral-core%3A8282%2Fconnectors%2F1012493422%3E+%3Fp+%3Fo+.+%7D+FROM+NAMED+%3Chttps%3A%2F%2Fbroker.ids.isst.fraunhofer.de%2Fadmin%3E+WHERE+%7B+GRAPH+%3Chttps%3A%2F%2Fbroker.ids.isst.fraunhofer.de%2Fadmin%3E+%7B+%3Chttp%3A%2F%2Fcentral-core%3A8282%2Fconnectors%2F1012493422%3E+%3Fp+%3Fo+%7D+%7D
[2022-04-06 10:24:21] Fuseki INFO [6165] Query = CONSTRUCT { <http://central-core:8282/connectors/1012493422> ?p ?o . } FROM NAMED <https://broker.ids.isst.fraunhofer.de/admin> WHERE { GRAPH <https://broker.ids.isst.fraunhofer.de/admin> { <http://central-core:8282/connectors/1012493422> ?p ?o } }
[2022-04-06 10:24:21] Fuseki INFO [6165] 200 OK (18 ms)
[2022-04-06 10:24:21] Fuseki INFO [6166] POST http://broker-fuseki:3030/connectorData
[2022-04-06 10:24:21] Fuseki INFO [6166] Update
[2022-04-06 10:24:21] Fuseki INFO [6166] 204 No Content (48 ms)
[2022-04-06 10:24:21] Fuseki INFO [6167] POST http://broker-fuseki:3030/connectorData?graph=https://broker.ids.isst.fraunhofer.de/admin
[2022-04-06 10:24:21] Fuseki INFO [6167] Body: Content-Length=153, Content-Type=application/rdf+thrift, Charset=null => RDF-THRIFT : Count=1 Triples=1 Quads=0
[2022-04-06 10:24:21] Fuseki INFO [6167] 200 OK (25 ms)
Logs in B's DSC after this
2022-04-06T10:36:57,139 [http-nio-8080-exec-9] WARN - TEST_DEPLOYMENT: IDS-Message is sent without a valid DAT, will not be sent in PRODUCTIVE_DEPLOYMENT. [code=(IMSCOW0041), reason=(Mandatory required information of the connector certificate is missing (AKI/SKI)! Needed to determine the fingerprint of the connector for the DAPS! Possible reason: Are you using a valid connector certificate issued by the DAPS?)]
2022-04-06T10:36:57,336 [http-nio-8080-exec-9] INFO - Successfully loaded Keystore.
-2022-04-06T10:36:57,471 [http-nio-8080-exec-9] INFO - Successfully loaded Truststore.
2022-04-06T10:36:57,548 [http-nio-8080-exec-9] WARN - Trustmanager is trusting all Certificates in TEST_DEPLOYMENT mode, you should not use this in production! [code=(IMSCOW0032)]
2022-04-06T10:36:57,564 [http-nio-8080-exec-9] WARN - TEST_DEPLOYMENT: IDS-Message is sent without a valid DAT, will not be sent in PRODUCTIVE_DEPLOYMENT. [code=(IMSCOW0041), reason=(Mandatory required information of the connector certificate is missing (AKI/SKI)! Needed to determine the fingerprint of the connector for the DAPS! Possible reason: Are you using a valid connector certificate issued by the DAPS?)]
-2022-04-06T10:36:57,593 [http-nio-8080-exec-9] INFO - Sending request to http://34.77.70.203:8282/infrastructure ...
2022-04-06T10:36:58,254 [http-nio-8080-exec-9] INFO - Successfully received response to request.
2022-04-06T10:36:58,299 [http-nio-8080-exec-9] INFO - Successfully passed SHACL-Validation.
2022-04-06T10:36:58,423 [http-nio-8080-exec-9] INFO - Successfully updated connector. [url=([http://34.77.70.203:8282/infrastructure})](http://34.77.70.203:8282/infrastructure%7D))]
B sends a query message from their own connector, and they don't see the resource added by A
If a connector is already registered in a broker, and then sends a second update connector, the triplestore of the broker clears. Broker Version is v4.2.8 .
A has a connector (DSC) and send an update message to broker
A creates a resource,distribution,artifact,contract in their connector, and sends a resource update message to broker
B sends a query message from their own connector, and they see the resource added by A
C also has a connector (DSC) and sends an update message to the broker
C also has a connector (DSC) and sends another update message to the broker broker logs after this:
Fuseki log after this
Logs in B's DSC after this
B sends a query message from their own connector, and they don't see the resource added by A