[jboss-jira] [JBoss JIRA] Commented: (JBAS-5072) Fix null pointer exception when getting keys, values, or entry's in the ConcurrentHashmap

[Jay Howell (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-5072?page=comments#action_12391882 ] 
            
Jay Howell commented on JBAS-5072:
----------------------------------

I reverted the changes and defined another version of the oswego component.  The new path is http://repository.jboss.com/oswego-concurrent/1.3.4-jboss-update1/

I will update the build-thirdpary.xml files for branch 4.2 and for head with the new version of the oswego library, 1.3.4-jboss-update1.  This also required two changes to component-info.xml files.

The 4.2 branch uses component jbossxb 1.0.0.sp1.  I had to change this component-info.xml file to add the compatibility for the new oswego version. http://repository.jboss.com/jboss/jbossxb/1.0.0.SP1/component-info.xml

In the head, which will be 5 beta3, I believe I had to change the jboss messaging component, to add the compatibility for the new oswego version.  http://repository.jboss.com/jboss/messaging/1.4.0.SP1-brew/component-info.xml




> 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