[Enrich]Exchanges in bottom route tracing is missing

[Hooghof]

In the tracing, the steps in the bottom route of the enrich component are missing.

This finding follows after #307

Test case on Development
Tenant: Regression Tests
Flow: EnrichArchiveWithTextBody

[brunovg]

This problem was already on 4.14.9
Postpone to 4.17.3

[brunovg]

From what I can see, on this scenario, the generated CamelContext is not fully correct.
One thing that I spot was the bottom branch, after the FTP, that route is not reachable on any point on the CamelContext.
Another main difference, is the use of a pollEnrich directly, without using an Enrich on a previous route.
@skin27 let's talk about this next week, maybe you can spot the main problem more quickly than I

[Hooghof]

All exchanges in the transaction are visible now.

The flow should produce a zip file which contains the files enrich1.txt and enrich3.txt, but it produces a zip file with the files enrich1.txt and an inner zip file with the name enrich1.zip. The file enrich1.zip has the 2 text files enrich1.txt and enrich3.txt in it.

After the aggregate component, the header CamelFileName has the value enrich1.zip. See version 43 of the test flow.

[brunovg]

It seems that the last change we made on Enrich component (calling a extra route with the pollEnrich from an enrich), is causing this issue.

    <route id="2634551c-5244-4930-97b3-bcde9ae0f057">
        <from uri="direct:672b994ec6210718c600033e_test_25f89152-25eb-46c4-86b9-9d83629b9d0c_split" />
        <setProperty propertyName="Enrich-Type">
            <simple>application/zip</simple>
        </setProperty>
        <setProperty propertyName="Error-Route">
            <simple>true</simple>
        </setProperty>
        <enrich strategyRef="CurrentEnrichStrategy">
            <simple>
                direct:672b994ec6210718c600033e_test_2634551c-5244-4930-97b3-bcde9ae0f057_BottomCenter</simple>
        </enrich>
        <to uri="direct:672b994ec6210718c600033e_test_2634551c-5244-4930-97b3-bcde9ae0f057" />
    </route>
    ...
    <route id="88f6c2ed-5136-471b-94c9-2a7e145ee622">
        <from
            uri="direct:672b994ec6210718c600033e_test_2634551c-5244-4930-97b3-bcde9ae0f057_BottomCenter" />
        <choice>
            <when>
                <simple>${exchangeProperty.Enrich-Type} == null</simple>
                <setProperty propertyName="Enrich-Type">
                    <simple>application/override</simple>
                </setProperty>
            </when>
        </choice>
        <pollEnrich strategyRef="CurrentEnrichStrategy" timeout="5000">
            <simple>
                sftp:[email protected]:2022//development/Regression
                Tests/test/in?autoCreate=true&amp;delete=false&amp;recursive=false&amp;fileName=enrich3.txt&amp;passiveMode=true&amp;disconnect=true&amp;throwExceptionOnConnectFailed=true&amp;consumer.bridgeErrorHandler=true&amp;password=RAW(Unmwrnf4bM3RUwoG)&amp;binary=true&amp;moveFailed=RAW(.error)&amp;serverHostKeys=ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256,ssh-rsa&amp;publicKeyAcceptedAlgorithms=ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256,ssh-rsa&amp;keyExchangeProtocols=curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group1-sha1,diffie-hellman-group14-sha1</simple>
        </pollEnrich>
        <to uri="direct:672b994ec6210718c600033e_test_88f6c2ed-5136-471b-94c9-2a7e145ee622" />
    </route>

[brunovg]

We found out that when using Queues, the CamelFileName header was not propagated by default to the next route (changed on 4.8.0).

[Hooghof]

Test findings

1. The first transaction gives a corrupt zip file
2. The second transactions delivers a zip file that can be opened
3. The second zip file contains 3 files: enrich1.txt, enrich2.txt and enrich.zip. The last one contains enrich1.txt, enrich2.txt and enrich3.txt. The included enrich.zip is basically the expected zip file, which should be the response of the flow

Enrich_20250116090323016.zip
Enrich_20250116090621535.zip