Mule
  1. Mule
  2. MULE-6200

Binding does not work with dynamic endpoints

    Details

    • User impact:
      Low
    • Configuration:
      Hide

      <flow name="testBindingFlow">
      <vm:inbound-endpoint path="in" exchange-pattern="request-response"/>
      <object-to-string-transformer />
      <component class="org.mule.binding.BindingComponent">
      <binding interface="org.mule.binding.BindingInterface">
      <outbound-endpoint address="http://localhost:#[map-payload:port]/#[map-payload:path]">
      <expression-transformer evaluator="map-payload" expression="payload" />
      <response>
      <object-to-string-transformer />
      </response>
      </outbound-endpoint>
      </binding>
      </component>
      </flow>

      Show
      <flow name="testBindingFlow"> <vm:inbound-endpoint path="in" exchange-pattern="request-response"/> <object-to-string-transformer /> <component class="org.mule.binding.BindingComponent"> <binding interface="org.mule.binding.BindingInterface"> <outbound-endpoint address="http://localhost:#[map-payload:port]/#[map-payload:path]"> <expression-transformer evaluator="map-payload" expression="payload" /> <response> <object-to-string-transformer /> </response> </outbound-endpoint> </binding> </component> </flow>
    • Log Output:
      Hide
      ********************************************************************************
      Message : Failed to invoke DefaultJavaComponent{testBindingFlow.commponent.607551681}. Component that caused exception is: DefaultJavaComponent{testBindingFlow.commponent.607551681}. Message payload is of type: String
      Code : MULE_ERROR--2
      --------------------------------------------------------------------------------
      Exception stack is:
      1. No connector available (java.lang.UnsupportedOperationException)
        org.mule.endpoint.DynamicOutboundEndpoint:172 (null)
      2. Failed to create proxy for org.mule.binding.BindingComponent@9ad5d46 (org.mule.api.MuleRuntimeException)
        org.mule.component.DefaultInterfaceBinding:83 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MuleRuntimeException.html)
      3. Failed to invoke DefaultJavaComponent{testBindingFlow.commponent.607551681}. Component that caused exception is: DefaultJavaComponent{testBindingFlow.commponent.607551681}. Message payload is of type: String (org.mule.component.ComponentException)
        org.mule.component.AbstractComponent:148 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/component/ComponentException.html)
      --------------------------------------------------------------------------------
      Root Exception stack trace:
      java.lang.UnsupportedOperationException: No connector available
      at org.mule.endpoint.DynamicOutboundEndpoint.getConnector(DynamicOutboundEndpoint.java:172)
      at org.mule.component.BindingInvocationHandler.addRouterForInterface(BindingInvocationHandler.java:68)
      at org.mule.component.BindingInvocationHandler.<init>(BindingInvocationHandler.java:48)
          + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
      ********************************************************************************
      Show
      ******************************************************************************** Message : Failed to invoke DefaultJavaComponent{testBindingFlow.commponent.607551681}. Component that caused exception is: DefaultJavaComponent{testBindingFlow.commponent.607551681}. Message payload is of type: String Code : MULE_ERROR--2 -------------------------------------------------------------------------------- Exception stack is: 1. No connector available (java.lang.UnsupportedOperationException)   org.mule.endpoint.DynamicOutboundEndpoint:172 (null) 2. Failed to create proxy for org.mule.binding.BindingComponent@9ad5d46 (org.mule.api.MuleRuntimeException)   org.mule.component.DefaultInterfaceBinding:83 ( http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MuleRuntimeException.html ) 3. Failed to invoke DefaultJavaComponent{testBindingFlow.commponent.607551681}. Component that caused exception is: DefaultJavaComponent{testBindingFlow.commponent.607551681}. Message payload is of type: String (org.mule.component.ComponentException)   org.mule.component.AbstractComponent:148 ( http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/component/ComponentException.html ) -------------------------------------------------------------------------------- Root Exception stack trace: java.lang.UnsupportedOperationException: No connector available at org.mule.endpoint.DynamicOutboundEndpoint.getConnector(DynamicOutboundEndpoint.java:172) at org.mule.component.BindingInvocationHandler.addRouterForInterface(BindingInvocationHandler.java:68) at org.mule.component.BindingInvocationHandler.<init>(BindingInvocationHandler.java:48)     + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ********************************************************************************
    • Similar Issues:
      MULE-1782Dynamic creation of message receiver endpoints doesn't work
      MULE-2520Management context binding is not working in ScriptConfigurationBuilder
      MULE-5044A dynamic endpoints contaioning a template does not work as a target of a FilteringOutboundRouter
      MULE-5783Dynamic endpoints are not working when connector-ref is used
      MULE-6924Dynamic round robin does not work in cluster
      MULE-6132Dynamic Outbound Endpoint Address
      MULE-5162Dynamic endpoints don't work for VM and JMS transport
      MULE-6014JMS MEP request-response not working if followed by a dynamic endpoint
      MULE-6749ReplyToHandlers do not work with Dynamic Outbound Endpoints
      MULE-3481Disposing a Service does not remove the inbound endpoints

      Description

      Binding component fails with connector not found exception when using dynamic endpoints.

      1. patch.txt
        1 kB
        Alan Cassar

        Activity

        Hide
        Alan Cassar added a comment -

        This patch fixes the issue

        Show
        Alan Cassar added a comment - This patch fixes the issue
        Hide
        Alan Cassar added a comment -

        Test case to support the patch. Without the patch, the test case fails with above exception. With the patch applied. It works fine.

        Show
        Alan Cassar added a comment - Test case to support the patch. Without the patch, the test case fails with above exception. With the patch applied. It works fine.
        Hide
        Alan Cassar added a comment -

        please note in the POM I used Mule version of 3.2.2, you should switch that to the current 3.x branch version.

        Show
        Alan Cassar added a comment - please note in the POM I used Mule version of 3.2.2, you should switch that to the current 3.x branch version.
        Show
        Pablo Kraan added a comment - Fix 3.1.x http://fisheye.codehaus.org/changelog/mule/?cs=24538 Fix 3.2.x http://fisheye.codehaus.org/changelog/mule/?cs=24542 Fix 3.3.x http://fisheye.codehaus.org/changelog/mule/?cs=24543 Fix 3.x http://fisheye.codehaus.org/changelog/mule/?cs=24544

          People

          • Assignee:
            Alejandro Sequeira
            Reporter:
            Alan Cassar
          • Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development