Errors when you create second deployment environment

Edit online

Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15

When you are creating a second deployment environment, you might see errors in the application server log of the first deployment environment.

These errors can occur when the health monitor reads a group of configuration files that are still being created on the second deployment environment. In the SystemOut.log for the application server, you might see messages similar to the following message:

[5/20/14 2:29:06:258 EDT] 00000227 DataSourceCon E DSRA8040I: Failed to connect to the DataSource.  Encountered "": java.io.FileNotFoundException: /opt/bpm85/WebSphere/AppServer/profiles/Node1Profile/config/cells/PSCell1/clusters/WPSDE3.AppCluster/resources.xml (No such file or directory)

In the SystemOut.log for the deployment manager, you might see messages similar to the following message:


[5/20/14 2:29:08:786 EDT] 00000523 FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /opt/bpm85/WebSphere/AppServer/profiles/DmgrProfile/logs/ffdc/dmgr_3eea2fb2_14.05.20_02.29.08.7854652312342454021904.txt com.ibm.wps.hm.rest.system.DataSourceHealthParameter.updateDataSourceStatus 353
[5/20/14 2:29:10:317 EDT] 00000502 MultiSyncMana A  ADMS0207I: Node Synchronization state for node: Node2 - initiate time: 2014.05.20 at 02:27:07:778 EDT
result: In Progress
Update occurred

These errors can safely be ignored.