Mule
  1. Mule
  2. MULE-5178

Exceptions stored in DefaultEntryPointResolverSet not threadsafe

    Details

    • User impact:
      Medium
    • Similar Issues:
      MULE-2947ResponseOutputStream contains non-threadsafe dead code
      MULE-5559HttpsConnector fails to throw exception on missing key store
      MULE-8449NPE while removing an entry from object store
      MULE-8179NullPointerException thrown when using persistent object store under high load
      MULE-554Custom Exception readers for handling non-standard exceptions
      MULE-6861Watermark / Binding object store items to flow variables
      MULE-3421Scripting component not thread safe
      MULE-8204ordering for stored procedure parameters causes errors
      MULE-6471Default exception strategy is not being called
      MULE-6990OOM exception using foreach

      Description

      When configuring a <flow> with a component the entry point resolver of the component is shared between all threads. The DefaultEntryPointResolverSet has an instance variable that stores the exceptions that occur when running the entry point resolvers. However, since a single instance of this class is shared between multiple threads, the list of exceptions may contain invalid error messages from different threads.

      Either store the exceptions in a ThreadLocal store or refactor to use one entry point resolver per thread.

        Issue Links

          Activity

            People

            • Assignee:
              Dirk Olmes
              Reporter:
              Dirk Olmes
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development