Wednesday, August 27, 2014

CWWIM4551E Change handler was not defined for repository type 'DOMINO'

After changing the LDAP Server for my Sametime Cell, I was unable to start a Websphere Server using the nodeagent.

On the SystemOut.log for the nodeagent I saw the following messages:

[8/27/14 11:51:05:381 BRT] 0000003d exception     E com.ibm.ws.wim.adapter.ldap.change.ChangeHandlerFactory getChangeHandler CWWIM4551E  Change handler was not defined for repository type 'DOMINO'
[8/27/14 11:51:05:382 BRT] 0000003d exception     E com.ibm.ws.wim.adapter.ldap.change.ChangeHandlerFactory getChangeHandler
                                 com.ibm.websphere.wim.exception.WIMSystemException: CWWIM4551E  Change handler was not defined for repository type 'DOMINO' .
        at com.ibm.ws.wim.adapter.ldap.change.ChangeHandlerFactory.getChangeHandler(ChangeHandlerFactory.java:95)
        at com.ibm.ws.wim.adapter.ldap.LdapAdapter.initialize(LdapAdapter.java:251)
        at com.ibm.ws.wim.RepositoryManager.initialize(RepositoryManager.java:610)
        at com.ibm.ws.wim.RepositoryManager.(RepositoryManager.java:131)
        at com.ibm.ws.wim.RepositoryManager.singleton(RepositoryManager.java:154)
        at com.ibm.ws.wim.RepositoryManager.singleton(RepositoryManager.java:140)
        at com.ibm.ws.wim.RealmManager.initialize(RealmManager.java:133)
        at com.ibm.ws.wim.RealmManager.(RealmManager.java:101)
        at com.ibm.ws.wim.RealmManager.singleton(RealmManager.java:108)
        at com.ibm.ws.wim.registry.util.TypeMappings.(TypeMappings.java:94)
        at com.ibm.ws.wim.registry.util.UniqueIdBridge.(UniqueIdBridge.java:105)
        at com.ibm.ws.wim.registry.WIMUserRegistry.initialize(WIMUserRegistry.java:206)
        at com.ibm.ws.security.registry.UserRegistryImpl.initializeCustomImpl(UserRegistryImpl.java:258)
        at com.ibm.ws.security.registry.UserRegistryImpl.initialize(UserRegistryImpl.java:192)
        at com.ibm.ws.security.config.UserRegistryConfigImpl.do_createRegistryObjects(UserRegistryConfigImpl.java:729)
        at com.ibm.ws.security.config.UserRegistryConfigImpl.createRegistryObjects(UserRegistryConfigImpl.java:686)
        at com.ibm.ws.security.config.UserRegistryConfigImpl.getUserRegistryImpl(UserRegistryConfigImpl.java:671)
        at com.ibm.ws.security.ltpa.CrossRealmUtil.getUserRegistry(CrossRealmUtil.java:286)
        at com.ibm.ws.security.ltpa.CrossRealmUtil.isUserFromThisRealm(CrossRealmUtil.java:61)
        at com.ibm.ws.security.ltpa.LTPAServerObject.realmsMatch(LTPAServerObject.java:2943)
        at com.ibm.ws.security.ltpa.LTPAServerObject.validateToken(LTPAServerObject.java:1184)
        at com.ibm.ws.security.ltpa.LTPAServerObject.validateToken(LTPAServerObject.java:1097)
        at com.ibm.ws.security.token.WSCredentialTokenMapper.validateLTPAToken(WSCredentialTokenMapper.java:1639)
        at com.ibm.ws.hamanager.runtime.DefaultTokenProvider.authenticateMember(DefaultTokenProvider.java:214)
        at com.ibm.ws.hamanager.coordinator.dcs.MemberAuthenticatorImpl.authenticateMember(MemberAuthenticatorImpl.java:87)
        at com.ibm.ws.dcs.vri.transportAdapter.rmmImpl.ptpDiscovery.DiscoveryRcv.acceptStream(DiscoveryRcv.java:185)
        at com.ibm.rmm.ptl.tchan.receiver.PacketProcessor.fetchStream(PacketProcessor.java:470)
        at com.ibm.rmm.ptl.tchan.receiver.PacketProcessor.run(PacketProcessor.java:860)



Stopping the nodeagent did not work:
icsp111:/opt/IBM/WebSphere/AppServer/profiles/STMSPNProfile1/bin # ./stopNode.sh
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/STMSPNProfile1/logs/nodeagent/stopServer.log
ADMU0128I: Starting tool with the STMSPNProfile1 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU0111E: Program exiting with error: javax.management.JMRuntimeException:
           ADMN0022E: Access is denied for the stop operation on Server MBean
           because of insufficient or empty credentials.
ADMU4113E: Verify that username and password information is correct.  If
           running tool from the command line, pass in the correct -username
           and -password.  Alternatively, update the .client.props
           file.
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
ADMU0211I: Error details may be seen in the file:
           /opt/IBM/WebSphere/AppServer/profiles/STMSPNProfile1/logs/nodeagent/stopServer.log


I had to kill -9 the nodeagent process, and then manually sync the node with the System Console:

/opt/IBM/WebSphere/AppServer/profiles/STMSPNProfile1/bin # ./syncNode.sh stsc.company.com 8703 -username wasadmin -password P@ssw0rd
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/icsp111STMSPNProfile1/logs/syncNode.log
ADMU0128I: Starting tool with the STMSPNProfile1 profile
ADMU0401I: Begin syncNode operation for node STMSNode1 with Deployment
           Manager
stsc.company.com: 8703
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node STMSNode1 has been synchronized
           with Deployment Manager
stsc.company.com: 8703



3 comments:

Stepherd said...

It is really a great and useful piece of info. I’m glad that you shared this helpful info with us. Please keep us informed like this. Thank you for sharing.

Staffing Companies in Bangalore

henris said...

Thank you so much for posting like this. I enjoyed much more here. So please keep update like this.

Medical Insurance Plans

Health Insurance UAE

Insurance Companies in Dubai

Jissa said...

Thank you for sharing. And if you are looking for the best relocation process can make easier by our beneficial relocation services with

Warehouse for Rent Singapore

Cheapest Movers in Singapore

Cheapest Storage Space Singapore