This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 14879 - Concurent modification exception in DataObjectPool
Summary: Concurent modification exception in DataObjectPool
Status: CLOSED DUPLICATE of bug 14872
Alias: None
Product: platform
Classification: Unclassified
Component: Data Systems (show other bugs)
Version: 3.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Vitezslav Stejskal
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-08-29 06:37 UTC by Jaroslav Tulach
Modified: 2008-12-22 23:55 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
The exception (2.86 KB, text/plain)
2001-08-29 06:38 UTC, Jaroslav Tulach
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2001-08-29 06:37:45 UTC
[Ales] "The exception is in attachement, this could be the solution":

         synchronized (this) {
             if (toNotify == null) {
                 return;
             }

             if(System.currentTimeMillis()<toNotifyModified+SAFE_NOTIFY_DELAY) {
                 task.schedule (SAFE_NOTIFY_DELAY);
                 return;
             }


             it = toNotify.iterator ();
             // CHANGE !!!
            toNotify = null;
         }
Comment 1 Jaroslav Tulach 2001-08-29 06:38:41 UTC
Created attachment 2330 [details]
The exception
Comment 2 Jaroslav Tulach 2001-08-29 07:27:09 UTC
I suspect the suggestion solution not to work because of code in
waitNotified method. It needs the toNotify to contain the objects
until really notified, but I am not sure.
Comment 3 Jaroslav Tulach 2001-08-29 14:34:29 UTC
Ales said toNotify=null does not work. We have to go with
toNotify.clone ().iterator ()...
Comment 4 Jan Zajicek 2001-09-10 14:11:40 UTC
The root of the exception is the same as in issue #14872.

*** This issue has been marked as a duplicate of 14872 ***
Comment 5 Quality Engineering 2003-07-01 16:05:10 UTC
Resolved for 3.4.x or earlier, no new info since then -> verified
Comment 6 Quality Engineering 2003-07-01 16:25:00 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.