[MGNLUI-934] Messages app causes ConcurrentModificationException Created: 21/Mar/13  Updated: 16/Aug/13  Resolved: 28/Jun/13

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.0
Fix Version/s: 5.1

Type: Bug Priority: Major
Reporter: Samuli Penttilä Assignee: Samuli Penttilä
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2013-03-21 at 1.32.48 PM.png    
Issue Links:
Relates
relates to MAGNOLIA-4919 Create UI tests for admincentral Closed
causality
is causing MGNLUI-935 Pulse message list is messed up 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
Sprint: Iteration 2013-15, Iteration 2013-16, Iteration 2013-17, Beta 2, Beta 3

 Description   

Sending messages through Messages app will sometimes result an ConcurrentModificationException. Is not always reproducible and best way to try to reproduce is to use selenium test AdminCentralUITest.sendAndRetrieveMessage. Had rarely happened during manually testing.

[WARNING] [talledLocalContainer] java.util.ConcurrentModificationException
[WARNING] [talledLocalContainer] at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
[WARNING] [talledLocalContainer] at java.util.HashMap$KeyIterator.next(HashMap.java:828)
[WARNING] [talledLocalContainer] at com.vaadin.server.AbstractCommunicationManager.getDirtyVisibleConnectors(AbstractCommunicationManager.java:2152)
[WARNING] [talledLocalContainer] at com.vaadin.server.AbstractCommunicationManager.writeUidlResponse(AbstractCommunicationManager.java:791)
[WARNING] [talledLocalContainer] at com.vaadin.server.AbstractCommunicationManager.paintAfterVariableChanges(AbstractCommunicationManager.java:728)
[WARNING] [talledLocalContainer] at com.vaadin.server.AbstractCommunicationManager.handleUidlRequest(AbstractCommunicationManager.java:599)
[WARNING] [talledLocalContainer] at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:315)
[WARNING] [talledLocalContainer] at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:201)
[WARNING] [talledLocalContainer] at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
[WARNING] [talledLocalContainer] at info.magnolia.cms.filters.ServletDispatchingFilter.doFilter(ServletDispatchingFilter.java:123)
[WARNING] [talledLocalContainer] at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:91)
[WARNING] [talledLocalContainer] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83)
[WARNING] [talledLocalContainer] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:85)
[WARNING] [talledLocalContainer] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:85)
[WARNING] [talledLocalContainer] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:85)
[WARNING] [talledLocalContainer] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:85)
[WARNING] [talledLocalContainer] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:85)
[WARNING] [talledLocalContainer] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:85)
[WARNING] [talledLocalContainer] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:85)
[WARNING] [talledLocalContainer] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:85)



 Comments   
Comment by Samuli Penttilä [ 28/Mar/13 ]

Created external ticket http://dev.vaadin.com/ticket/11445

Comment by Samuli Penttilä [ 28/Jun/13 ]

No longer reproduceable. Selenium tests that previously were exposing this problem are passing fine.

Generated at Mon Feb 12 08:41:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.