Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Aug 6 2012
    • Component/s: None
    • Labels:
      None

      Description

      Remove component-managed from the spec
      We should remove component-managed from the spec, because this function is duplicate of what a user would get by supplying a ManagedThreadFactory to a Java SE executor service.

      Regarding the sentence "If the threads are pooled, the overhead of reusing a thread disappears since the context does not have to change the thread's context." - This statement isn't entirely accurate. Think of security context, where different users are running the same component. It would be an error to keep reusing the context of user1 on pooled threads for user2 and user3 who are also using the component. The the security context will be all wrong. This is another reason why we want to get rid of Component-Managed Executor. If we instead let it be the component's responsibility to get this behavior by supplying a ManagedThreadFactory to a Java SE executor service, then it will be clear to the component exactly what they're doing.

        Activity

        anthony.lai created issue -
        anthony.lai made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s Aug 6 2012 [ 15963 ]
        Resolution Fixed [ 1 ]
        anthony.lai made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            anthony.lai
            Reporter:
            anthony.lai
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: