PI09287: THE "WAIT FOR SERVER OF CLUSTER" STEP TIMES OUT INSTEAD OF FAILING IF THE TEMP.PY FILE IS DELETED.

IBM UrbanCode Deploy Fix Pack 3 (6.0.1.3) for 6.0.1
IBM UrbanCode Deploy Fix Pack 4 (6.0.1.4) for 6.0.1
IBM UrbanCode Deploy Interim Fix 1 for 6.0.1.4
IBM UrbanCode Deploy Fix Pack 5 (6.0.1.5) for 6.0.1
IBM UrbanCode Deploy Fix Pack 6 (6.0.1.6) for 6.0.1
IBM UrbanCode Deploy Fix Pack 7 (6.0.1.7) for 6.0.1
IBM UrbanCode Deploy Fix Pack 8 (6.0.1.8) for 6.0.1
IBM UrbanCode Deploy Fix Pack 9 (6.0.1.9) for 6.0.1
IBM UrbanCode Deploy Fix Pack 10 (6.0.1.10) for 6.0.1
IBM UrbanCode Deploy Fix Pack 11 (6.0.1.11) for 6.0.1
IBM UrbanCode Deploy Fix Pack 12 (6.0.1.12) for 6.0.1
IBM UrbanCode Deploy iFix 1 for 6.0.1.9

APAR status

• Closed as program error.

Error description

• The "Wait for server of cluster" step does not fail if the
  temp.py file is deleted.  Instead you have to wait until the
  step times out.  The temp.py file being deleted can happen when
  you deploy the same application to two different environments
  where both environments are on the same physical server and the
  working directory isn't environment specific.
  

Local fix

• There is no known workaround at this time.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Any                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The "Wait for server of cluster" step does not fail if the   *
  * temp.py file is deleted.  Instead you have to wait until the *
  * step times out.  The temp.py file being deleted can happen   *
  * when                                                         *
  * you deploy the same application to two different             *
  * environments                                                 *
  * where both environments are on the same physical server and  *
  * the                                                          *
  * working directory isn't environment specific.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Fixed in the February 2014 and future version of the WebSphere
  plugin available on the UrbanCode plugin download site.
  

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

  UDEPLOY

• Fixed component ID

  5725M7700

Applicable component levels

• R500 PSN

     UP

• R500 PSY

     UP