IBM Support

IZ90130: API FIND --Depth 3 on BusinessApplications Fails, causing a NullPointerException error

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM DESCRIPTION
NullPointerException thrown when invoking api.sh find

When invoking api.sh find --depth 3 the user will see an empty
XML output document ("<result />")

The cause is there are objects within the
result tree that have references to non-existing objects. GUIDs
of these child non-existing objects are set in parent objects.

When trying to find these phantom objects using
$COLLATION_HOME/bin/dbquery.sh -csv "select * from persobj where
GUID_X='36A64CCA1EB83D11AA819E062CE37C15'"` there is no
evidence of them being recorded in DB.

Stack trace indicating this issue can be found in ApiServer.log
and it looks similar to the following one:

2010-11-24 15:30:40,359 ApiServer [RMI TCP Connection(91)-
X.X.X.X]  ERROR server.DataWorker - [ApiServer.E.127] Unable to
convert data to XMLcom.collation.proxy.api.client.ApiException:
[PLATFORM.XML.E.25]
The application is unable to get find object members:
java.lang.NullPointerException.
        at com.collation.proxy.api.client.ApiModel.next
(ApiModel.java:245)
        at com.ibm.cdb.api.server.DataWorker.nextXML
(DataWorker.java:318)
        at com.ibm.cdb.api.server.ApiServerBean.nextXML
(ApiServerBean.java:163)
        at com.collation.proxy.api.server.ApiServer.nextXML
(ApiServer.java:705)
        at sun.reflect.GeneratedMethodAccessor137.invoke(Unknown
Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:618)
        at sun.rmi.server.UnicastServerRef.dispatch
(UnicastServerRef.java:309)
        at sun.rmi.transport.Transport$1.run(Transport.java:168)
        at java.security.AccessController.doPrivileged
(AccessController.java:279)
        at sun.rmi.transport.Transport.serviceCall
(Transport.java:164)
        at sun.rmi.transport.tcp.TCPTransport.handleMessages
(TCPTransport.java:506)
        at sun.rmi.transport.tcp.TCPTransport
$ConnectionHandler.handleRequest(TCPTransport.java:838)
        at sun.rmi.transport.tcp.TCPTransport
$ConnectionHandler.run(TCPTransport.java:912)
        at java.lang.Thread.run(Thread.java:810)
Caused by: com.collation.platform.xml.XMLException:
[PLATFORM.XML.E.25]
The application is unable to get find object members:
java.lang.NullPointerException.
        at com.collation.platform.xml.XMLUtils.getMembers
(XMLUtils.java:1446)
        at com.collation.platform.xml.XMLUtils.modelToDom
(XMLUtils.java:437)
        at com.collation.platform.xml.XMLUtils.modelToDom
(XMLUtils.java:539)
        at com.collation.platform.xml.XMLUtils.modelToDom
(XMLUtils.java:539)
        at com.collation.platform.xml.XMLUtils.fillDoc
(XMLUtils.java:350)
        at com.collation.platform.xml.XMLUtils.next
(XMLUtils.java:250)
        at com.collation.proxy.api.client.ApiModel.next
(ApiModel.java:243)
        ... 14 more

Local fix

  • 



Problem summary


    

  • NullPointerException thrown when invoking api.sh find


When invoking api.sh find --depth 3 the user will see an empty
XML output document ("<result />")

The cause is there are objects within the
result tree that have references to non-existing objects. GUIDs
of these child non-existing objects are set in parent objects.

When trying to find these phantom objects using
$COLLATION_HOME/bin/dbquery.sh -csv "select * from persobj where
GUID_X='36A64CCA1EB83D11AA819E062CE37C15'"` there is no
evidence of them being recorded in DB.

Stack trace indicating this issue can be found in ApiServer.log
and it looks similar to the following one:

2010-11-24 15:30:40,359 ApiServer [RMI TCP Connection(91)-
X.X.X.X]  ERROR server.DataWorker - [ApiServer.E.127] Unable to
convert data to XMLcom.collation.proxy.api.client.ApiException:
[PLATFORM.XML.E.25]
The application is unable to get find object members:
java.lang.NullPointerException.
        at com.collation.proxy.api.client.ApiModel.next
(ApiModel.java:245)
        at com.ibm.cdb.api.server.DataWorker.nextXML
(DataWorker.java:318)
        at com.ibm.cdb.api.server.ApiServerBean.nextXML
(ApiServerBean.java:163)
        at com.collation.proxy.api.server.ApiServer.nextXML
(ApiServer.java:705)
        at sun.reflect.GeneratedMethodAccessor137.invoke(Unknown
Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:618)
        at sun.rmi.server.UnicastServerRef.dispatch
(UnicastServerRef.java:309)
        at sun.rmi.transport.Transport$1.run(Transport.java:168)
        at java.security.AccessController.doPrivileged
(AccessController.java:279)
        at sun.rmi.transport.Transport.serviceCall
(Transport.java:164)
        at sun.rmi.transport.tcp.TCPTransport.handleMessages
(TCPTransport.java:506)
        at sun.rmi.transport.tcp.TCPTransport
$ConnectionHandler.handleRequest(TCPTransport.java:838)
        at sun.rmi.transport.tcp.TCPTransport
$ConnectionHandler.run(TCPTransport.java:912)
        at java.lang.Thread.run(Thread.java:810)
Caused by: com.collation.platform.xml.XMLException:
[PLATFORM.XML.E.25]
The application is unable to get find object members:
java.lang.NullPointerException.
        at com.collation.platform.xml.XMLUtils.getMembers
(XMLUtils.java:1446)
        at com.collation.platform.xml.XMLUtils.modelToDom
(XMLUtils.java:437)
        at com.collation.platform.xml.XMLUtils.modelToDom
(XMLUtils.java:539)
        at com.collation.platform.xml.XMLUtils.modelToDom
(XMLUtils.java:539)
        at com.collation.platform.xml.XMLUtils.fillDoc
(XMLUtils.java:350)
        at com.collation.platform.xml.XMLUtils.next
(XMLUtils.java:250)
        at com.collation.proxy.api.client.ApiModel.next
(ApiModel.java:243)
        ... 14 more

    



Problem conclusion


    

  • The fix for this APAR is contained in the following
maintenance packages:
| Fix Pack | 7.2.0.0-TIV-ITADDM-FP0004

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IZ90130
    • 

  • Reported component name
    APP DEPENDENCY
    • 

  • Reported component ID
    5724N5500
    • 

  • Reported release
    720
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2010-12-03
    • 

  • Closed date
    2011-01-26
    • 

  • Last modified date
    2011-01-26
    • 





    

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

  • Fixed component ID
    5724N5500
    • 



Applicable component levels


    

  • R720  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"720","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                                                                    

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            26 January 2011
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback