IBM Support

IV24924: FAILURE TO DELETE DELETED ENTITIES IN UDDI FROM WSRR DURING UDDISYNCHRONIZATION IF SYNC CONFIGURATION READONLY ELEMENT IS YES

Direct links to fixes

8.0.0.3-WS-WSRR-ZOS-IFIV65487_IV79085_IV87422_IV87429_IV89477
8.0.0.3-WS-WSRR-MultiOS-IFIV65487_IV79085_IV87422_IV87429_IV89477
WebSphere Service Registry and Repository V8.0 Fix Pack 2

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Failure of mapping of deleted entities from UDDI -> WSRR
during UDDI synchronization when the sync configuration READONLY
 element is set to YES.

Local fix

  • 



Problem summary


    

  • When you delete a service in UDDI the related service documents
and entities in WSRR should be deleted during the next
synchronization. This should happen even if you have set the
<READONLY> configuration element to 'yes'.

Instead, when <READONLY> is set to 'yes', entities are left in
WSRR and the following error appears in SystemOut.log:

GSR5805E: Errors occurred during mapping and transaction roll
back.

    



Problem conclusion


    

  • The UDDI synchronization code was attempting to clean up
references in the UDDI registry during processing of a deleted
UDDI entity even when the UDDI registry was specified as 'read
only' in the configuration.

A check has been added to the code to prevent attempts to modify
the UDDI registry content when it is specified as 'read only' so
that mapping completes successfully. This means that the
relevent entities in WSRR will now be deleted as expected.

This fix is targeted for inclusion in fix pack 5 for WSRR v6.3,
fix pack 6 for WSRR v7.0, fix pack 3 for WSRR v7.5 and fix pack
1 for WSRR v8.0.

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IV24924
    • 

  • Reported component name
    SERVICE REGISTR
    • 

  • Reported component ID
    5724N7200
    • 

  • Reported release
    630
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2012-07-18
    • 

  • Closed date
    2012-07-20
    • 

  • Last modified date
    2012-07-20
    • 





    

  • 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
    • 

  • R750  PSY
       UP
    • 

  • R800  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:
            

            20 July 2012
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback