Status: Resolved (View Workflow)
Affects Version/s: 1.1.23.Final, 2.1.2.Final, 2.2.1.Final
Steps to Reproduce:
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 )
Git Pull Request:
Having a simple bean
invoked from a JSF view,
trying to end the same conversation from two parallel request results in
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
increasing the CONCURRENT_ACCESS_TIMEOUT makes the issue more apparent.