request-reply router does not preserve session properties

Currently, properties are dropped on message aggregation. This behavior needs to be improved.

is this a regression in 3.2? If so, needs to be fixed, not necessarily improved.

I'm seeing the same behavior in 3.1 and 3.2 using the attached config:

Inbound, outbound, and invocation properties are dropped during message aggregation.
Session properties are preserved.

This is test java/org/mule/issues/PropertiesWithAllTestCase in mule-3.2.x and mule-3.x

I've added my project that this doesn't work with. Session properties are being erased.

There is output from the 3.1 version and the 3.2 version, same code.

The session properties are being lost at

<request-reply timeout="2000">
<jms:outbound-endpoint queue="frontier.destination" />
<jms:inbound-endpoint queue="frontier.price" />
</request-reply>

The session properties that are present before the router get overwritten by the (empty) set in the reply.

3.1.x: r23550
3.2.x: r23551
3.x: r23536

This is still happening in 3.2.2 (however it works in 3.2.1 )
I've attached a test case that reproduces this issue.

Wrong JIRA - Sorry

Running the following configuration

<flow name="flow1">
        <http:inbound-endpoint address="http://localhost:8082/sprop" exchange-pattern="one-way"/>
        <message-properties-transformer scope="session">
            <add-message-property key="foo" value="foo"/>
        </message-properties-transformer>
        <test:component logMessageDetails="true"/>
        <request-reply>
            <vm:outbound-endpoint address="vm://flow2"/>
            <vm:inbound-endpoint path="inbound"/>
        </request-reply>
        <test:component logMessageDetails="true"/>
    </flow>

    <flow name="flow2">
        <vm:inbound-endpoint  path="flow2"/>
        <test:component logMessageDetails="true"/>
        <message-properties-transformer scope="session">
            <add-message-property key="bar" value="bar"/>
        </message-properties-transformer>
        <message-properties-transformer scope="outbound">
            <add-message-property key="outbar" value="bar"/>
        </message-properties-transformer>
    </flow>

I am expecting to see 3 test component outputs, each one listing the Session properties. The sequence should be: {foo:foo}, {foo:foo}, {foo:foo, bar:bar}. I got the following results:

• on Mule 3.1.4 seems that the execution never comes back to flow1 after entering flow2. This is another issue (MULE-6238), but it is related since we can not check the properties behavior with this malfunction.

• on Mule 3.2.x works fine.

• on Mule 3.3.x works fine.

r23550

German Solis This made it into 3.2.2, should be working, also Saveli has confirmed.

The test fails for me in 3.2.2, AFAIK this is a regression since it works correctly in 3.2.1.
Did you test it in 3.2.2 or 3.2.x ?

Which test?

The attached test:

RequestReplyTestCase.zip

It set a session property right before the request-reply, and then it try to access it right after, but the session prop is not available.

In 3.2.x the attached test failed. I changed the jms endpoint to vm endpoinds and all went fine, just as I posted before. Maybe jms connector is the problem?

Mule 3.3 Studio project. Session Properties still get lost on Request-Reply router.

This continues to be an issue but only in the case when the message received from the request-reply inbound endpoint does not included a MULE_SESSION instance.

3.1.x: r24739
3.2.x: r24740
3.3.x: r24741