Reply-To doesn't work for WMQ transport

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.2.1
  • Fix Version/s: 3.2.1, 3.3 M1
  • Component/s: Transport: JMS
  • Labels:
    None
  • User impact:
    Medium
  • Effort points:
    3
  • Configuration:
    Hide

    <model name="ReplyToHonoredInFlowWithAsyncBlock">
    <service name="initialService">
    <inbound>
    <jms:inbound-endpoint queue="jmsIn1" exchange-pattern="request-response"/>
    </inbound>
    <echo-component/>
    <outbound>
    <pass-through-router>
    <vm:outbound-endpoint path="vmIn1" exchange-pattern="request-response"/>
    <reply-to address="vm://vmResponse"/>
    </pass-through-router>
    </outbound>
    <async-reply>
    <vm:inbound-endpoint path="vmResponse"/>
    <single-async-reply-router/>
    </async-reply>
    </service>

    <service name="replierService">
    <inbound>
    <vm:inbound-endpoint path="vmIn1" exchange-pattern="request-response"/>
    </inbound>
    <test:component appendString=" modified"/>
    </service>
    </model>

    Show
    <model name="ReplyToHonoredInFlowWithAsyncBlock"> <service name="initialService"> <inbound> <jms:inbound-endpoint queue="jmsIn1" exchange-pattern="request-response"/> </inbound> <echo-component/> <outbound> <pass-through-router> <vm:outbound-endpoint path="vmIn1" exchange-pattern="request-response"/> <reply-to address="vm://vmResponse"/> </pass-through-router> </outbound> <async-reply> <vm:inbound-endpoint path="vmResponse"/> <single-async-reply-router/> </async-reply> </service> <service name="replierService"> <inbound> <vm:inbound-endpoint path="vmIn1" exchange-pattern="request-response"/> </inbound> <test:component appendString=" modified"/> </service> </model>
  • Similar Issues:
    None

Description

ReplyTo message property is not being honored because it seems to be lost in the way.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Pablo La Greca added a comment -

ReplyToDestination in MuleEvent was being lost because of all the copies we currently do of the event before routing it.

Mule-ce-3.2.x : 23366, 23370
Mule-ce-3.2.1 : 23371, 23373
Mule-ce-3.x : 23375

Show
Pablo La Greca added a comment - ReplyToDestination in MuleEvent was being lost because of all the copies we currently do of the event before routing it. Mule-ce-3.2.x : 23366, 23370 Mule-ce-3.2.1 : 23371, 23373 Mule-ce-3.x : 23375
Hide
Permalink
Pablo La Greca added a comment -

Mule-ce-3.1.x: 23583

Show
Pablo La Greca added a comment - Mule-ce-3.1.x: 23583
Hide
Permalink
Pablo La Greca added a comment -

Mule-ce-3.1.x: 23587 - related issue with outbound endpoint

Show
Pablo La Greca added a comment - Mule-ce-3.1.x: 23587 - related issue with outbound endpoint
Hide
Permalink
Pablo La Greca added a comment -

Mule-ce-3.1.x: 23590 - fix event used to recreate event

Show
Pablo La Greca added a comment - Mule-ce-3.1.x: 23590 - fix event used to recreate event

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: