Community
Participate
Working Groups
This bug has come out of Bug 278496. The following 2 aspects are causing ConcurrentModificationException during the call to AJBuilder.postCallListeners: <pre> public aspect SQL_Exception { public pointcut callToSqlException() : call(* java.sql.SQLException+.*(..)) || call(java.sql.SQLException..new(..)); before() : callToSqlException(){ } } public aspect JDBC_Driver { public pointcut callToJDBC() : call(* java.sql.DriverManager+.*(..)) || call(java.sql.DriverManager..new(..)); before() : callToJDBC(){ } } </pre> Trying to reproduce this in my own workspace with no luck.
BuildListeners are only added and removed during the startup and the shutdown of the ajdt core and ui plugins (unless there is a third party plugin that adds more listeners). It is conceivable that if a build is finishing during the time when ajdt.ui is shutting down the ConcurrentModificationException can be thrown. A way around this might be to synchronize all methods that access the build listeners.
OK...just committed a new version of AJDT where calls to the offending method are synchronized. This might avoid your problem. Since I cannot reproduce your problem on my end, I cannot be sure that it will address your problem, so please try it. Build will be available in about 2-3 hours.
Any update on this? Still receiving ConcurrentModification errors?
(In reply to comment #3) > Any update on this? Still receiving ConcurrentModification errors? > Hi, I am waiting for Andrew to react. He mentioned that will look into memory consumptions on large systems. I hope he gets some time to do. Yes, I still get ConcurrentModification and sometimes also get Out of memory error.
Are you on 3.4 or 3.5?
(In reply to comment #5) > Are you on 3.4 or 3.5? Hi, I am on 3.4.
Move to the 2.0.2 release.
Try to solve for 2.1.0.
Determining what will be tackled for 2.1.1 release.
