Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-1954

RequestContext, SessionContext are thread local

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • None
    • None
    • Built-in beans
    • None

      Further to my conversation in Weld forum, https://developer.jboss.org/thread/257300, I think the scope contexts such as RequestContext, SessionContext should be propagated to a different thread on the async call scenarios. The threadlocal contexts have introduced a lot of servlet work, which potentially violates servlet specification. Even now, Tomcat is still having some issues (http://weld.cdi-spec.org/documentation/#8). Can we start thinking about this and get this addressed so that the application servers can get the async handled free?

              Unassigned Unassigned
              emijiang6 Emily Jiang (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: