[MAGNOLIA-4930] Rendering fail due to ConcurrentModificationException Created: 28/Mar/13  Updated: 29/May/13  Resolved: 03/Apr/13

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 4.5.9

Type: Bug Priority: Critical
Reporter: Ondrej Chytil Assignee: Ondrej Chytil
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File stacktrace.txt    
Issue Links:
relation
is related to MAGNOLIA-4729 ACLs only for sub pages does not work... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Known details at forum page.



 Comments   
Comment by Jan Haderka [ 02/Apr/13 ]

Actually you should use latch or barrier in the test to make sure that t2 starts only when t1 is already running, but before it's done. The way it is now, on super slow server, t1 might be finished before t2 has started.

http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/CountDownLatch.html

Comment by Jan Haderka [ 05/Apr/13 ]

You do not restore interrupted status in the test correctly, but since it would fail test anyway I'm letting this go. To see how you should treat such kind of exception properly, please read http://www.ibm.com/developerworks/java/library/j-jtp05236/index.html

Generated at Mon Feb 12 04:00:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.