search

Mobility-Data-Space / mobility-data-space

Mobility Data Space ist the data sharing community for all actors who would like to design the mobility of tomorrow.
https://mobility-dataspace.eu
8 stars 1 forks source link

Clearing House returns 404 Error #27

Closed ghost closed 1 year ago

ghost commented 2 years ago

Based on the 3. Step (Configuration) wiki page, it is necessary to configure the Mobility Dataspace Clearing House in the IDS connector. This doesn't work as expected.

Steps to reproduce the error

  1. Setting up a Dataspace Connector (DSC) as described
  2. Add the clearing.house.url=https://clearing.test.mobility-dataspace.eu/logs/messages/ attribute to the resources/application.properties file
  3. (Re-)starting the DSC
  4. Requesting a resource
  5. Problem occurs

Logs As shown in the DSC logs, the requests against the Test Clearing House fails with a 404 response code. Examples:

INFO - Sending request to https://clearing.test.mobility-dataspace.eu/logs/messages/process/a86e5752-9a2c-4765-8aed-0b04088567e3 ...
WARN - Received response but response-code not in 200-299. [code=(IMSMEW0046), response-code=(404)]

INFO - Sending request to https://clearing.test.mobility-dataspace.eu/logs/messages/messages/log/a86e5752-9a2c-4765-8aed-0b04088567e3 ...
WARN - Received response but response-code not in 200-299. [code=(IMSMEW0046), response-code=(404)]
ip312 commented 2 years ago

Thank you for the reporting. The correct link for the Test Clearing House is https://clearing.test.mobility-dataspace.eu (without /logs/messages/) clearing.house.url=https://clearing.test.mobility-dataspace.eu The incorrect linking caused the problem. We have already changed the link on the wiki page.

hqarawlus commented 2 years ago

After adjustment of the URL, we are still unable to completely log to the clearing house. The process creation is successful, but we receive a response code 400 upon sending a log message. I have attached a snipped of the logs that we receive. 

2022-08-23T13:33:46,573 [http-nio-8080-exec-4] INFO - Sending request to https://clearing.test.mobility-dataspace.eu/process/206a8c2d-ab01-48d6-806b-c46aa5f688b8 ...
2022-08-23T13:33:46,910 [http-nio-8080-exec-4] INFO - Successfully received response to request.

2022-08-23T13:33:46,958 [http-nio-8080-exec-4] INFO - Sending request to https://clearing.test.mobility-dataspace.eu/messages/log/206a8c2d-ab01-48d6-806b-c46aa5f688b8 ...
2022-08-23T13:33:47,102 [http-nio-8080-exec-4] WARN - Received response but response-code not in 200-299. [code=(IMSMEW0046), response-code=(400)]
ghost commented 2 years ago

Can you reproduce the problem @ip312? Are there any updates or hints how the future planning looks like?

ip312 commented 2 years ago

Yes, we are able to reproduce the issue. Our developers are trying to fix it, but it takes time. Sorry for the response delay, I hoped that we could solve the problem faster.