JR60709: YOU SEE A NOSUCHFILE EXCEPTION WHEN YOU START THE TASK MANAGER LOGGER WHILE THE IBM BUSINESS AUTOMATION WORKFLOW SERVER STARTS

APAR status

• Closed as documentation error.

Error description

• When you start an IBM Business Automation Workflow server with
  the embedded Content Navigator, you see following exception
  while the Task Manager logger starts on a managed node that has
  different installation root path than that of the deployment
  manager (Dmgr):
  
  [11/28/18 21:40:25:725 CET] 000000c5 webapp        E
  com.ibm.ws.webcontainer.webapp.WebApp
  notifyServletContextCreated SRVE0283E: Exception caught while
  initializing context: {0}
                                   java.lang.RuntimeException:
  java.nio.file.NoSuchFileException:
  /deas118/WebSphere/AppServer/taskManagerLogs/taskManager/AppClus
  ter_DEAS218Node01/ECMTaskManagerApplication.log.0.lck
   at
  com.ibm.ecm.task.TaskLogger$1.initialValue(TaskLogger.java:46)
   at
  com.ibm.ecm.task.TaskLogger$1.initialValue(TaskLogger.java:21)
   at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:193)
   at java.lang.ThreadLocal.get(ThreadLocal.java:183)
   at com.ibm.ecm.task.TaskLogger.get(TaskLogger.java:65)
   at com.ibm.ecm.task.TaskLogger.info(TaskLogger.java:97)
   at
  com.ibm.ecm.task.StartUpListener.extractContextParamsAndMakeCont
  extParams(StartUpListener.java:397)
   at
  com.ibm.ecm.task.StartUpListener.contextInitialized(StartUpListe
  ner.java:120)
   at
  com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreate
  d(WebApp.java:1734)
  
  PRODUCTS AFFECTED
  IBM Business Automation Workflow
  

Local fix

• Read "YOU SEE A NOSUCHFILE EXCEPTION WHEN YOU START THE TASK
  MANAGER LOGGER WHILE THE IBM BUSINESS AUTOMATION WORKFLOW SERVER
   STARTS"
  (http://www.ibm.com/support/docview.wss?uid=ibm100880563).
  

Problem summary

• You receive this exception when multiple managed nodes are in
  Business Automation Workflow clusters and one of the managed
  nodes is suddenly installed under a different path that that of
  the Dmgr node.
  

Problem conclusion

• A technote will be published to reflect this rarely occuring
  product limitation.
  

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

Applicable component levels