198 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
 
Latest 7 Posts
System Info Report
Thu, Jan 19th 2017 10
Cumulative Hotfix 9001-ST-Proxy-FP-WLIN-A8ZJ5B for Sametime Proxy 9.0.0.1 [April 2016]
Wed, Apr 27th 2016 8
What do you think of when you hear IBM?
Tue, Apr 19th 2016 7
Your ACTION Required for Sametime 9 iOS Customers before May 5, 2016 - Updated security certificate for Push Notifications (iOS)
Mon, Apr 18th 2016 7
Sametime VMCU Capacity
Thu, Oct 8th 2015 6
Documentação em Português do IBM Sametime 9
Wed, Sep 30th 2015 8
Configuring LDAP for Domino on the Sametime Meeting Recording / Renderer Server on WAS 8.5.5.5
Tue, Sep 29th 2015 10
Top 10
IBM Connections 5.0 Cumulative Refresh 1 (CR1) Released!
Thu, Oct 16th 2014 12
Configuring LDAP for Domino on the Sametime Meeting Recording / Renderer Server on WAS 8.5.5.5
Tue, Sep 29th 2015 10
Ubuntu 14.04.1 LTS Post Install Tasks
Sat, Dec 6th 2014 10
System Info Report
Thu, Jan 19th 2017 10
IBM Sametime Proxy Server - add tokenDomain to your stproxyconfig.xml to fix SSO issues
Tue, Mar 31st 2015 9
Documentação em Português do IBM Sametime 9
Wed, Sep 30th 2015 8
Cumulative Hotfix 9001-ST-Proxy-FP-WLIN-A8ZJ5B for Sametime Proxy 9.0.0.1 [April 2016]
Wed, Apr 27th 2016 8
CWWIM4551E Change handler was not defined for repository type 'DOMINO'
Wed, Aug 27th 2014 7
Recommendations for Network FIle System (NFS) Shared Area in Connections / Message Stores in Websphere
Wed, Jul 30th 2014 7
Your ACTION Required for Sametime 9 iOS Customers before May 5, 2016 - Updated security certificate for Push Notifications (iOS)
Mon, Apr 18th 2016 7


CWWIM4551E Change handler was not defined for repository type 'DOMINO'
Twitter Google+ Facebook LinkedIn Addthis Email Gmail Flipboard Reddit Tumblr WhatsApp StumbleUpon Yammer Evernote Delicious
   

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





---------------------
http://dansilva.blogspot.com/2014/08/cwwim4551e-change-handler-was-not.html
Aug 27, 2014
8 hits



Recent Blog Posts
10
System Info Report
Thu, Jan 19th 2017 8:23p   Dan Silva




Created and Maintained by Yancy Lent - About - Planet Lotus Blog - Advertising - Mobile Edition