IBM WebSphere Application Server,  Middleware

 WebSphere AS Global Security – ADMS0036E: The configuration synchronization failed

March 27, 2019 / 0 Comments

Nach dem Aktivieren der Global Security schlägt die Node Synchronisation aus dem Deployment Manager fehl.

Das Problem ist mir zumindest in diesen WebSphere Versionen begegnet:

  • IBM WebSphere Application Server Network Deployment 8.5
  • WAS ND bis 8.5.5 Fixpack 15

In den Protokollen finden sich folgende Fehlermeldungen:

[3/25/19 19:53:27:932 CET] 0000008a NodeSyncTask  A    ADMS0036E: The configuration synchronization failed.
[3/25/19 19:53:30:636 CET] 00000048 FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /log/HSL_CELL85/ffdc/nodeagent_2875f3_19.03.25_19.53.30.628307621416607723793.txt com.ibm.ejs.util.am._Alarm.run 95
[3/25/19 19:54:04:409 CET] 00000044 DefaultTokenP I   HMGR0149E: An attempt to open a connection to core group DefaultCoreGroup has been rejected. The sending process has a name of HSL_CELL85\DMGR1\dmgr and an IP address of 192.168.1.100. Global security in the local process is Disabled. Global security in the sending process is Enabled. The received token starts with . The exception is .
[3/25/19 19:54:27:370 CET] 00000087 FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /log/HSL_CELL85/ffdc/nodeagent_c0ba1e0f_19.03.25_19.54.27.1057436260776741690282.txt com.ibm.ws.management.status.NodeAgentStatusCache$StatusCacheTimedThread.run 1371
[3/25/19 19:54:27:785 CET] 0000009f NodeSync    ADMS0005E: The system is unable to generate synchronization request java.lang.reflect.UndeclaredThrowableException
        at com.sun.proxy.$Proxy15.queryNames(Unknown Source)
        at com.ibm.ws.management.AdminClientImpl.queryNames(AdminClientImpl.java:108)

Lösung

Eine erste Synchronisation vom DMGR funktioniert nicht nach dem Einschalten der Global Security. Der Node muss die Synchronisation einmalig starten: 

cd Profile_dir/bin/
./stopServer.sh nodeagent

./syncNode.sh localhost SOAPPORT
ADMU0116I: Tool information is being logged in file /logs/syncNode.log
ADMU0128I: Starting tool with the node profile
ADMU0401I: Begin syncNode operation for node NODE01 with Deployment Manager
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node NODE01 has been synchronized with Deployment Manager

./startServer.sh nodeagent
ADMU3000I: Server nodeagent open for e-business; process id is 20059

Danach kann die Synchronisation auch erfolgreich vom WebSphere Deployment Manager aus gestartet werden.

Leave a Reply