IBM Support

JR57787: YOU SEE AN ERROR WHEN YOU START AN EXPOSED HERITAGE HUMAN SERVICE

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.

Direct link to fix

bpm.8570.cf2017.06.delta.repository

 

APAR status

  • Closed as program error.

Error description

  • When you start an exposed heritage human service by using IBM
Portal, the Process Admin Console, or a custom client, the
service sometimes fails immediately and you see an error stating
 "The service you are trying to access is no longer available."


PRODUCTS AFFECTED
IBM BPM Advanced
IBM BPM Standard
IBM BPM Express

Local fix

  • 



Problem summary


    

  • When a heritage human service is exposed as a dashboard,
startable service, administration service, or URL, it can be
started as a stand-alone service even if it doesn't have task
context. The runtime state of such a stand-alone service is
stored in the memory. Because users might simply close their
browser and, therefore, not necessarily finish the service, the
IBM Business Process Manager (BPM) runtime environment has a
cleanup mechanism that removes the state of stand-alone services
 from the memory after it has not been used for a configurable
time (the default is one hour).

When the IBM BPM runtime environment starts a new service, it is
added it to an internal registry of running stand-alone services
without the current time as the access time. Until the access
time is set to the current time, a concurrent thread cleans up
the stand-alone service.

    



Problem conclusion


    

  • A fix is available for IBM BPM V8.5.5.0 that will be included in
 IBM BPM V8.5.7.0 cumulative fix 2017.06 that corrects the
initialization logic of a stand-alone service so that it is
added to the internal registry with the correct access time so
that concurrent threads no longer clean it up.

A fix is also available for IBM BPM V8.5.6.2 (also know as
8.5.6.0 cumulative fix 2 or CF02).

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    JR57787
    • 

  • Reported component name
    BPM ADVANCED
    • 

  • Reported component ID
    5725C9400
    • 

  • Reported release
    855
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2017-04-20
    • 

  • Closed date
    2017-05-17
    • 

  • Last modified date
    2017-08-17
    • 





    

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

  • Fixed component ID
    5725C9500
    • 



Applicable component levels


    

  • R855  PSY
       UP
    • 

  • R857  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            17 August 2017
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback