assimbly / runtime

Java & REST API's for creating and running integrations
Apache License 2.0
17 stars 3 forks source link

[XSLT]Install failure after boot #234

Closed Hooghof closed 3 months ago

Hooghof commented 3 months ago

Test case Instance:next Tenant: Regression Tests Flow: XsltUrl

Possible explanation: this flow gets the xslt from an url. This url links to another flow on next. Perhaps that flow isn't available during the server boot. After a manual start, the flow runs. If the unavailability of the linked xslt is the case, perhaps this is unsolvable.

Install logs

Name XsltComponent
Flow type Default flow
Message Failed to create route ID_657075a721563f000d000323-93bafef0-97d3-481c-ab24-6ea81ccf703f at: >>> step -> [[To[mock:x], To[xslt-saxon:https://development.dovetail.world/test/inbound_http/regressiontests/XsltUrlService?saxonExtensionFunctions=#uuid-function], To[direct:ID_657075a721563f000d000323_test_93bafef0-97d3-481c-ab24-6ea81ccf703f]]] <<< in route: Route(ID_657075a721563f000d000323-93bafef0-97d3-481c-ab24-6e... because of Failed to resolve endpoint: xslt-saxon://https://development.dovetail.world/test/inbound_http/regressiontests/XsltUrlService?saxonExtensionFunctions=#uuid-function due to: javax.xml.transform.TransformerException: java.io.IOException: Server returned HTTP response code: 502 for URL: https://development.dovetail.world/test/inbound_http/regressiontests/XsltUrlService
Hooghof commented 3 months ago

We draw the conclusion that this has to do something with the order of flow starting. I changed the name of the flow which contains the XSLT, in order to see if the name is used in the start order.