IBM Support

PH38717: Error indicating Analyze Client can't create parts displayed in Analysis Browser perspective in IDz, and slf4j errors in .log

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Starting IDz with AD Analyze Client 6.0 installed, in addition
to File Manager and Fault Analyzer, even with -clean option
after reboot, may show error in Application Discovery's
Analysis Browser perspective saying it can't create parts, and
in .log file, error messages like the following may be present:
.
!MESSAGE An error occurred while automatically activating
bundle com.ez.gdb.core (4003).
!STACK 0
org.osgi.framework.BundleException: Error starting module.
.
and later in the stack trace, this root exception is indicated:
.
Root exception:
java.lang.LinkageError: loading constraint violation when
resolving method
"org/slf4j/impl/StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/
ILoggerFactory;" :
loader
"org/eclipse/osgi/internal/loader/EquinoxClassLoader@f469f 703"
of class "org/slf4j/LoggerFactory"
and loader
"org/eclipse/osgi/internal/loader/EquinoxClassLoader@bcca1552"
of class "org/slf4j/impl/StaticLoggerBinder"
have different types for the method signature

Local fix

  • Locating and renaming the slf4j.log4j12_1.7.12.jar file
provided by
Application Discovery Analyze Client may resolve the error
symptoms.  For instance, rename the
file as slf4j.log4j12_1.7.12.jar_ (note trailing underscore in
renamed file's name)in order for it not to be recognized as a
jar file.

Problem summary

  • Errors occurred while loading Analyze Client, due to
incompatibility between different log4j plugins.

Problem conclusion

  • Code changed: Log4J 1.12 plug-in has been upgraded to
 log4j 2.17.1, which resolved the incompatibility.

Temporary fix

  • Removing components with incompatible plugins may help.

Comments

  • 



APAR Information




    

  • APAR number
    PH38717
    • 

  • Reported component name
    APPL DISCOVERY
    • 

  • Reported component ID
    5737B1600
    • 

  • Reported release
    510
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2021-07-06
    • 

  • Closed date
    2022-05-02
    • 

  • Last modified date
    2022-05-02
    • 





    

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

  • Fixed component ID
    5737B1600
    • 



Applicable component levels


    








      
              
                            

              

              [{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSRR9Q","label":"IBM Application Discovery"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"510"}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            03 May 2022
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback