PH51339: RUNNING DEPLOYMENT PROCESSES DO NOT RECOVER AFTER MAINTENANCE WINDOW.

APAR status

• Closed as program error.

Error description

• When running a deployment prior to enabling maintenance mode the
  system fails to kick off any child component processes while
  maintenance mode is enabled.
  
  022-09-12 13:24:20,063 CEST FATAL ProcessService-1
  com.urbancode.commons.util.concurrent.NamedThreadFactory[Process
  Service] - Thread[ProcessService-1,5,ProcessService] terminated
  due to uncaught exception:
  com.urbancode.ds.subsys.calendar.entity.CalendarEntryOnBlackoutE
  xception: Can't create Entry because of Blackout(s).
  com.urbancode.ds.subsys.calendar.entity.CalendarEntryOnBlackoutE
  xception: Can't create Entry because of Blackout(s).
  at
  com.urbancode.ds.subsys.calendar.entity.CalendarFactory.assertDa
  teNotDuringCalendarBlackout(CalendarFactory.java:170)
  at
  com.urbancode.ds.subsys.calendar.entity.CalendarFactory.createUn
  savedEntry(CalendarFactory.java:145)
  at
  com.urbancode.ds.subsys.deploy.runtime.DeployRuntimeFactory.crea
  teUnsavedComponentProcessRequest(DeployRuntimeFactory.java:1048)
  at
  com.urbancode.ds.subsys.deploy.runtime.DeployRuntimeFactory.crea
  teComponentProcessRequest(DeployRuntimeFactory.java:1083)
  at
  com.urbancode.ds.subsys.deploy.runtime.ComponentProcessRequestAc
  tionProcessor.createRequest(ComponentProcessRequestActionProcess
  or.java:369)
  at
  com.urbancode.ds.subsys.deploy.runtime.ComponentProcessRequestAc
  tionProcessor.process(ComponentProcessRequestActionProcessor.jav
  a:322)
  at
  com.urbancode.ds.subsys.deploy.runtime.ComponentProcessRequestPr
  ocessor.runActions(ComponentProcessRequestProcessor.java:155)
  at
  com.urbancode.ds.subsys.deploy.runtime.ComponentProcessRequestPr
  ocessor.runInTxContext(ComponentProcessRequestProcessor.java:146
  )
  at
  com.urbancode.ds.subsys.deploy.runtime.ComponentProcessRequestPr
  ocessor.lambda$runWithRetry$1(ComponentProcessRequestProcessor.j
  ava:134)
  at
  com.urbancode.ds.persistence.database.DBOperator.runOperationInT
  x(DBOperator.java:253)
  at
  com.urbancode.ds.persistence.database.DBOperator.access$100(DBOp
  erator.java:43)
  at
  com.urbancode.ds.persistence.database.DBOperator$TxRunner.run(DB
  Operator.java:341)
  at
  com.urbancode.ds.persistence.database.DBOperator.run0(DBOperator
  .java:201)
  at
  com.urbancode.ds.persistence.database.DBOperator.runSync(DBOpera
  tor.java:171)
  at
  com.urbancode.ds.subsys.deploy.runtime.ComponentProcessRequestPr
  ocessor.runWithRetry(ComponentProcessRequestProcessor.java:134)
  at
  com.urbancode.ds.subsys.deploy.runtime.DeployService.lambda$subm
  itComponentProcessSpecBatch$0(DeployService.java:301)
  at
  java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unkn
  own Source)
  at
  java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unk
  nown Source)
  at java.base/java.lang.Thread.run(Unknown Source)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * UrbanCode Deploy Web UI Users                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * "Can't create Entry because of Blackout(s)" error is getting *
  * displayed for running deployment during maintenance mode     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Fix is provided in IBM UrbanCode Deploy 7.3.2.2              *
  ****************************************************************
  

Problem conclusion

• Fix is provided in IBM UrbanCode Deploy 7.3.2.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