IBM Support

IT37325: ADOPTION OF BIPHTTPLISTENER FAILS IF INTEGRATION NODE IS CREATEDWITH VAULT KEY

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

  • When using integration node with a vault key, killing bipbroker
leads to duplicate biphttplistener i.e new process is created
owned by new bipbroker process and old one still exists as
orphan.

Local fix

  • N

Problem summary

  • ****************************************************************
USERS AFFECTED:
All User of App Connect Enterprise V11 and V12 using vault key
with Integration node.


Platforms affected:
MultiPlatform

****************************************************************
PROBLEM DESCRIPTION:
If bipbroker process gets killed and is auto-restarted by
bipservice , then it causes duplicate processes for
biphttplistener as adoption of existing process by newly started
bipbroker does not happen. This issue occurs only when
integration node is created with a vault key.

Problem conclusion

  • Product has been modified such that the restart of bipbroker by
bipservice does not result in duplicate child processes like
biphttplistener, DataFlowEngine etc.

---------------------------------------------------------------
The fix is targeted for delivery in the following PTFs:

Version    Maintenance Level
v11.0      11.0.0.14
v12.0      12.0.2.0

The latest available maintenance can be obtained from:
http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041

If the maintenance level is not yet available,information on
its planned availability can be found on:
http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
---------------------------------------------------------------

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IT37325
    • 

  • Reported component name
    APP CONNECT ENT
    • 

  • Reported component ID
    5724J0550
    • 

  • Reported release
    B00
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2021-06-18
    • 

  • Closed date
    2021-08-19
    • 

  • Last modified date
    2021-10-06
    • 





    

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

  • Fixed component ID
    5724J0550
    • 



Applicable component levels


    








      
              
                            

              

              [{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            13 October 2021
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback