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

Conversation lock not unlocked when ending conversations

    XMLWordPrintable

Details

    • Hide

      deploy the attached reproducer and run "python test.py" , notice the almost 1 second delay for the second response and see the server.log for org.jboss.weld.context.BusyConversationException (instead of the expected org.jboss.weld.context.NonexistentConversationException and no significant delay in the second request )

      Show
      deploy the attached reproducer and run "python test.py" , notice the almost 1 second delay for the second response and see the server.log for org.jboss.weld.context.BusyConversationException (instead of the expected org.jboss.weld.context.NonexistentConversationException and no significant delay in the second request )

    Description

      Having a simple bean

      @Model
      public class Controller {
          @Inject
          Conversation conversation;
      
          public void begin() {
              conversation.begin();
          }
      
          public void end() {
              conversation.end();
          }
      

      invoked from a JSF view,

      trying to end the same conversation from two parallel request results in

      org.jboss.weld.context.BusyConversationException: WELD-000322 Conversation lock timed out: 1

      it seems that the lock was not released, thus the second thread keeps waiting for the conversation timeout.

      The expected result (unless the conversation ending really took so long) would be for the second thread to end in org.jboss.weld.context.NonexistentConversationException: WELD-000321: No conversation found to restore for id 1

      Other notes:

      increasing the CONCURRENT_ACCESS_TIMEOUT makes the issue more apparent.

      Attachments

        Activity

          People

            mkouba@redhat.com Martin Kouba
            maschmid@redhat.com Marek Schmidt
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: