Workaround JDK misbehaviour in WeakCollectionCleaner
----------------------------------------------------
Key: GEOT-1138
URL: http://jira.codehaus.org/browse/GEOT-1138
Project: GeoTools
Issue Type: Improvement
Components: core referencing
Affects Versions: 2.3.0
Reporter: Andrea Aime
Assigned To: Martin Desruisseaux
Fix For: 2.3.1, 2.4.M0
As stated in these two threads:
http://www.nabble.com/Null-pointer-exception-tf3027587.html
http://www.nabble.com/Null-pointer-exception-tf3084434.html
the ReferenceQueue may misbehave during virtual machine shutdown under linux
and jdk 1.5.0._06
and return null without waiting when calling remove().
This triggers an infinite loop where the server logs are filled with tons of
null pointer exception.
I'd suggest to implement a workaround to avoid it, which may be:
* if null is returned, exit from the weak collection cleaner (may this cause
OOM in the long run?)
* if null is returned, don't log an exception, sleep for one or two seconds,
and then restart the loop
Martin, what do you think?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
