Mule
  1. Mule
  2. MULE-5525

The ajax transport throws an exception when receiving a message when configured to be run as a servlet

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 3.1.1
    • Fix Version/s: None
    • Component/s: Transport: AJAX
    • Labels:
      None
    • User impact:
      High
    • Similar Issues:
      MULE-5870WSProxyService throws exception using Flows (but not Services) when a message is received.
      MULE-6850Https connector configuration doesn't throw exception when keystore info is wrong
      MULE-182JmsSelectorFilter should not throw exception when invoked
      MULE-6157Ajax Transport RPC Calls Create Duplicate Responses
      MULE-2521Notification when polling transport's message receiver is 'finished'
      MULE-5575Polling receivers use wrong classloader when running in Mule standalone
      MULE-8251HTTP connector throws exception when WSC response is received
      MULE-6289Mule Context missing when receiving a message on TCP inbound endpoint
      MULE-6492NullPointer Exception in org.mule.routing.EventGroup.addEvent when running in a cluster
      MULE-4521Servlet endpoint throws java.io.IOException: chunked stream ended unexpectedly when proxying axis2 service

      Description

      Currently today it is not possible to run the ajax transport within a servlet as it throws an exception every time it gets a message. A patch to the AjaxContainerFunctionalTestCase is attached which demonstrates this issue.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Roko Kruze
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development