[
http://jira.jboss.com/jira/browse/JBAS-5072?page=comments#action_12391828 ]
Jay Howell commented on JBAS-5072:
----------------------------------
I fixed the source in the repository under
1.3.4-jboss(http://repository.jboss.com/oswego-concurrent/1.3.4-jboss/), posted the patch
for ConcurrentHashmap and recompiled the src and jar file under the lib directories. I
checked in the 3 files(patch, jar, and src) in the same version as before, 1.3.4. I would
have liked to have added another version number to it, so I could know if it's the old
1.3.4 or the new 1.3.4.
Anyway, I've checked them in and the fix for JBAS-4698 will still be in effect because
the build files for third party still point to the same place as before. So updating the
jar, the source, and the patch should be enough and no build changes are necessary.
Fix null pointer exception when getting keys, values, or entry's
in the ConcurrentHashmap
-----------------------------------------------------------------------------------------
Key: JBAS-5072
URL:
http://jira.jboss.com/jira/browse/JBAS-5072
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA
Reporter: Jay Howell
Assigned To: Jay Howell
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
Fixed null problem for JBAS-4698. The previous fix fixed the problem by using iteration
instead of values(), but it also allowed nulls to be put into the array, which throws a
null pointer exception. This is just further refinement of the JBAS-4698 bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira