Mule
  1. Mule
  2. MULE-5523

Using dynamic endpoint produce error when using async response

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.1
    • Fix Version/s: 3.1.2, 3.2.0
    • Component/s: Core: Endpoints
    • Labels:
      None
    • User impact:
      Medium
    • Similar Issues:
      MULE-7773Dynamic reference to sub flow produces lifecycle errors
      MULE-5026Async Reply: If endpoint used by the async reply is set to "request-response" then AbstractAsyncRequestReplyRequester will wait for ever for reply
      MULE-5488Messages may be sent to the wrong one when using dynamic endpoint
      MULE-557ExceptionBasedRouter is using async behaviour for all endpoints
      MULE-4631ChainingRouter uses send() with async endpoints
      MULE-5783Dynamic endpoints are not working when connector-ref is used
      MULE-5134When multiple connectors are specified dynamic endpoints errors.
      MULE-6200Binding does not work with dynamic endpoints
      MULE-380ChainingRouter sync/async behaviour
      MULE-2832Rename response router in 2.0

      Description

      Using the attached config file, sending a message to the vmProxy endpoint produces the following error:

      "Endpoint scheme must be compatible with the connector scheme. Connector is: "VM", endpoint is "http://localhost:5000/TEST"
      This error does not exists if I use a static URI endpoint instead of the dynamic one.

        Activity

        Show
        Pablo Kraan added a comment - - edited Fix 3.1.x: http://fisheye.codehaus.org/changelog/mule/?cs=21695 Fix 3.x http://fisheye.codehaus.org/changelog/mule/?cs=21701

          People

          • Assignee:
            Pablo Kraan
            Reporter:
            Pablo Kraan
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development