Bug 1347755

Summary: JobExecutionException is thrown in SessionDataContainer.cleanExpiredUsersSessions
Product: [oVirt] ovirt-engine Reporter: Martin Perina <mperina>
Component: AAAAssignee: Martin Perina <mperina>
Status: CLOSED NOTABUG QA Contact: Gonza <grafuls>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: bugs
Target Milestone: ovirt-4.0.1Flags: mperina: ovirt-4.0.z?
mperina: planning_ack?
mperina: devel_ack+
mperina: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-17 21:34:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Perina 2016-06-17 14:35:46 UTC
Description of problem:

JobExecutionException is thrown in SessionDataContainer.cleanExpiredUsersSessions because we iterate through the existing sessions using iterator, but we are removing expired sessions directly and not using iterator for that.

Version-Release number of selected component (if applicable):

4.0.0

How reproducible:

100%

Steps to Reproduce:
1. Login to webadmin
2. Wait until session is expires
3. Cca 1 minute later SessionDataContainer.cleanExpiredUsersSessions is executed and in server.log JobExecutionException can be seen

Actual results:


Expected results:


Additional info:

Comment 1 Martin Perina 2016-06-17 21:34:08 UTC
My mistake, removal works fine even by direct call due to use of ConcurrentHashMap