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

ConcurrentModificationException while deactivating conversations

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.1.1.Final
    • 1.1.0.CR3, 1.1.0.Final, Unscheduled
    • Conversations
    • None

    Description

      If a conversation gets deactivated, the code which actually iterates the map of conversations in org.jboss.weld.context.AbstractConversationContext is erroneous and easily runs into a ConcurrentModificationException if there is more than one conversation. We consider this a pretty serious defect because its not possible to use JBoss AS 6.0 GA for a real-world application.

      See attached patch for a fix.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. WELD-837 AbstractConversationContext.deactivate() throws ConcurrentModificationException

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              ajustin@redhat.com Ales Justin
              asiandub_jira Jan Groth (Inactive)
              Votes:
              11 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: