IBM Support

IZ94579: NullPointerException during create

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During create, delete, or update of objects in WebSphere
Service Registry and Repository, the following stack is
generated and the operation fails:


[1/27/11 11:07:30:458 EST] 00000033 api           E
com.ibm.serviceregistry.ServiceRegistrySessionBean retrieve
java.lang.NullPointerException at
com.ibm.sr.tyto.persistence.create.IThingHelper.getModifiedMs(IT
hingHelper.java:158) at
com.ibm.sr.tyto.persistence.mapper.IThingToSdoMapper.setBaseProp
erties(IThingToSdoMapper.java:1039) at
com.ibm.sr.tyto.persistence.mapper.IThingToSdoMapper.convertToSD
O(IThingToSdoMapper.java:337) at
com.ibm.sr.tyto.persistence.mapper.IThingToSdoMapper.convertToSd
oBusinessObject(IThingToSdoMapper.java:863) at
com.ibm.sr.tyto.persistence.mapper.IThingToSdoMapper.convertToSd
oGenericObject(IThingToSdoMapper.java:381) at
com.ibm.sr.tyto.persistence.mapper.IThingToSdoMapper.convertToSD
O(IThingToSdoMapper.java:299) at
com.ibm.sr.tyto.persistence.mapper.IThingToSdoMapper.convertTyto
ToSdo(IThingToSdoMapper.java:149)

Local fix

  • Not applicable

Problem summary

  • If you have multiple users creating, updating, or deleting at
the same time, it is possible that an object which has been
tested early in the thread and found from the database is later
no longer available in the database, or has been updated. This
problem was generating a NullPointerException.

The code has been redesigned so that now you will see a
ServiceRegistryInconsistentGraphReadException. If you see this
exception occasionally, you should refresh your view or catch
the exception and retry the activity.

Problem conclusion

  • This fix is expected in 7.0.0.5, and replaces the
NullPointerException with a
ServiceRegistryInconsistentGraphReadException, but note that it
does not resolve the underlying issue of data which is found
early in the thread and no longer found later in the thread.

If you see this problem frequently, you could consider upgrading
to DB2 v9.7, which should improve the behaviour.

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IZ94579
    • 

  • Reported component name
    SERVICE REGISTR
    • 

  • Reported component ID
    5724N7200
    • 

  • Reported release
    630
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2011-02-07
    • 

  • Closed date
    2011-05-10
    • 

  • Last modified date
    2011-05-10
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    • 



Fix information


    

  • Fixed component name
    SERVICE REGISTR
    • 

  • Fixed component ID
    5724N7200
    • 



Applicable component levels


    

  • R630  PSY
       UP
    • 

  • R700  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.3","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            10 May 2011
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback