If you trace the nodeagent during synchronization
(com.ibm.*=all=enabled) you can find a
DocumentAlreadyExistsException, because there are two documents in
the same location with different cases.
On UNIX, these files are treated as unique files; however, because
Windows is not case sensitive, the two files are not treated as unique
file names. Synchronization detects that the config directory on Base and
ND do not match because they are missing one of the two files. Therefore,
synchronization fails.
Example of the error message:
[9/4/04 2:54:23:281 PDT] 1cb1b60a GenericSerial > replaceObject
cells/ibmNetwork/applications/ibmapp.ear/deployments/ibmapp/META-INF/manifest.mf
com.ibm.websphere.management.exception.DocumentAlreadyExistsException:
cells/ibmNetwork/applications/ibmapp.ear/deployments/ibmapp/META-INF/manifest.mf
at
com.ibm.ws.management.repository.FileRepository.preCreate(FileRepository.java:624)
at
com.ibm.ws.management.repository.FileRepository.preUpdate(FileRepository.java:1363)
at
com.ibm.ws.management.repository.FileRepository.update(FileRepository.java:1324)
at
com.ibm.ws.management.repository.FileRepository.create(FileRepository.java:589)
at
com.ibm.ws.management.repository.FileRepository.create(FileRepository.java:577)
at com.ibm.ws.management.sync.NodeSyncTask.processFolderSyncUpdate
(NodeSyncTask.java:396)
at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:255)
at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:139)
at java.lang.Thread.run(Thread.java:513)
Look at the directory referenced in the error message; there are entries
similar to the following:
/usr/WebSphere/DeploymentManager/config/cells/ibmNetwork/applications/ibmapp.ear/deployments/ibmapp/META-INF/MANIFEST.MF
/usr/WebSphere/DeploymentManager/config/cells/ibmNetwork/applications/ibmapp.ear/deployments/ibmapp/META-INF/manifest.mf
|