When you deploy applications to the nodes in an IBM Business Process Manager cluster, they fail to start.
You might notice that a few system applications do not start if you try to start the deployment environment or cluster members immediately after the deployment environment is created. You might see the following error messages in the log files:
00000018 DeployedAppli W WSVR0206E: Module, mm.runtime.was.war, of application, mm.was_BPMDE.WebApp.ear/deployments/mm.was_BPMDE.WebApp, failed to start
00000018 ApplicationMg W WSVR0101W: An error occurred starting, mm.was_BPMDE.WebApp
00000015 wtp E org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.DirectoryLoadStrategyImpl collectFilesFromBinaries Failed to extract binaries to temporary location:
Binaries files were not added!
This load strategy [ org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.DirectoryArchiveLoadStrategyImpl@b9a8dc98 ] Container [ com.ibm.etools.commonarchive.impl.WARFileImpl@a281b485 (URI: mm.runtime.was.war, lastModified: 1374716213000, size: 4096, directoryEntry: <unset>, originalURI: mm.runtime.was.war) (types: null) ]
FFDC Exception:com.ibm.ws.exception.RuntimeWarning SourceId:com.ibm.wsspi.runtime.component.WsComponentImpl ProbeId:297 Reporter:com.ibm.ws.runtime.component.CompositionUnitMgrImpl@fb60f135
com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.webcontainer.exception.WebAppNotLoadedException: Failed to load webapp: Failed to load webapp: null
Diagnosing The Problem
To diagnose this issue, review the log files in the nodes. You might also notice that applications in the WebSphere Administrative Console have failed to start.
Resolving The Problem
Resolving the issue
To resolve the issue, manually synchronize any nodes that are not synchronized. Using the WebSphere Administrative Console, click System Administration > Nodes > Synchronize. You can also use the command-line to synchronize the nodes. For more information, see the syncNode command documentation.
Avoiding the issue
Use the following approaches to avoid the issue:
- Check the deployment environment status
Do not restart the deployment manager when the deployment environment is being generated. If you restart it during this process, you might cause the configuration to be inconsistent. Before you restart the Deployment Manager, check the status of the deployment environment. For more information, see the Displaying deployment environment status using the command line document.
- Check the node synchronization status
If the node agent was restarted after the deployment environment is generated, check the synchronization status before starting the IBM Business Process Manager nodes. In the WebSphere administrative console, click System Administration > Nodes > Status.
The failure to synchronize a node before starting IBM Business Process Manager causes applications to not start. You must complete a manual synchronization if a node is not synchronized.
Was this topic helpful?
15 June 2018