PI18869: LOOPS WITHIN COMPONENT PROCESS LEAD TO SERVER HANGS

IBM UrbanCode Deploy Fix Pack 2 (6.1.0.2) for 6.1
IBM UrbanCode Deploy Interim Fix 1 for 6.1.0.2
IBM UrbanCode Deploy Fix Pack 3 (6.1.0.3) for 6.1
IBM UrbanCode Deploy Fix Pack 4 (6.1.0.4) for 6.1

APAR status

• Closed as program error.

Error description

• If you create a Component Process that references itself without
  branching to prevent infinite loops, the server eventually hangs
  when accessing the Dashboard. An OutOfMemoryError can be seen in
  the deployserever.out
  
  Steps to reproduce:
  
  1. Create a Component with a Component process
  2. Inside the process, create a Step using: Utility Step > Run
  Component process
  3. Reference the process itself, so that it becomes infinitely
  recursive
  4. Create an Application process that calls this recursive
  process and execute it
  5. In the Dashboard you start seeing a huge number of processes.
  In time, the Dashboard will hang due an OutOfMemoryError.
  

Local fix

• Once the Dashboard hangs, there is no practical way of
  cancelling the recursive process from the user interface.
  
  Stop IBM UrbanCode Deploy and the Agent that was running the
  recursive process.
  Execute the following queries on the database:
  
  delete from wf_dispatched_task;
  delete from wf_workflow;
  
  Restart IBM UrbanCode Deploy.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All end users                                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * If you create a Component Process that references itself     *
  * without                                                      *
  * branching to prevent infinite loops, the server eventually   *
  * hangs                                                        *
  * when accessing the Dashboard. An OutOfMemoryError can be     *
  * seen in                                                      *
  * the deployserever.out.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Fixed in IBM UrbanCode Deploy 6.1.0.2
  

Temporary fix

Comments

APAR Information

• 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

  UC DEPLOY

• Fixed component ID

  5725M5400

Applicable component levels

• R600 PSY

     UP

• R601 PSY

     UP

• R610 PSY

     UP