DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27315>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27315 Coyote java.util.ConcurrentModificationException removing request processor [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|java.util.ConcurrentModifica|Coyote |tionException |java.util.ConcurrentModifica | |tionException removing | |request processor ------- Additional Comments From [EMAIL PROTECTED] 2004-06-15 11:39 ------- Addtional changes found which may contribute to the problem. Perhaps 'processors' which is an ArrayList should be synchronized via Collections.synchronizedList(new ArrayList(...)). I am concerned because it appears that some object cannot be removed from a pool and is therefore creating a memory leak. Can one of the developers have a look to see if that is the solution? =================================================================== RCS file: /home/cvspublic/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/RequestGroupInfo.java,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/RequestGroupInfo.java 2003/01/20 23:43:41 1.1 +++ jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/RequestGroupInfo.java 2004/01/15 13:16:49 1.2 @@ -13,6 +13,10 @@ processors.add( rp ); } + public void removeRequestProcessor( RequestInfo rp ) { + processors.remove( rp ); + } + public long getMaxTime() { long maxTime=0; for( int i=0; i<processors.size(); i++ ) { Adjust summary to be clearer of the problem. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
