Troubleshooting
Problem
After clustering IBM® WebSphere® Portal v6.1, all ConfigEngine scripts end with a "NullPointerException" regardless of whether or not you receive a BUILD SUCCESSFUL.
Symptom
This error message will only display in the console window where you ran the ConfigEngine script and will not log anywhere.The full message is:
==============================
BUILD SUCCESSFUL
Total time: 9 seconds
isIseries currently set to: null
uploading registry
Created admin client: com.ibm.ws.management.AdminClientImpl@4d044d04
Created config Service Proxy: com.ibm.websphere.management.configservice.ConfigServiceProxy@4a084a08
CELL: dmgrCell
CELL: dmgrCell
com.ibm.websphere.management.exception.ConfigServiceException: java.lang.NullPointerException
at com.ibm.websphere.management.configservice.ConfigServiceProxy.resolve(ConfigServiceProxy.java:468)
at com.ibm.wkplc.was.registry.AdminConfigRegistry.createNewRegistry(AdminConfigRegistry.java:226)
at com.ibm.wkplc.models.compregistry.ResourceWidget.saveResourceToAdminConfig(ResourceWidget.java:362)
at com.ibm.wkplc.models.compregistry.GenerateNodeRegistryXML.syncCacheToRegistry(GenerateNodeRegistryXML.java:419)
at com.ibm.wkplc.models.compregistry.RegistryHelper.uploadRegistryToWAS(RegistryHelper.java:83)
.
.
.
Caused by: java.lang.NullPointerException
at com.ibm.ws.sm.workspace.impl.RepositoryContextImpl.initChildTypesToLo ad(RepositoryContextImpl.java:1252)
at com.ibm.ws.sm.workspace.impl.RepositoryContextImpl.<init>(RepositoryC ontextImpl.java:117)
at com.ibm.ws.sm.workspace.impl.WorkSpaceImpl.createRootContext(WorkSpac eImpl.java:196)
at com.ibm.ws.sm.workspace.impl.WorkSpaceImpl.getRootContext(WorkSpaceIm pl.java:309)
at com.ibm.ws.sm.workspace.impl.WorkSpaceImpl.findContext(WorkSpaceImpl. java:222)
at com.ibm.ws.management.configservice.WorkspaceHelper.getScopeContexts( WorkspaceHelper.java:223)
at com.ibm.ws.management.configservice.ConfigServiceImpl.getAllBasic(Con figServiceImpl.java:1400)
=================================
Cause
Required files were not copied over to the Deployment Manager prior to clustering. In the Information Center instructions for setting up the Deployment Manager, you are required to run a ConfigEngine script:
- ConfigEngine.bat collect-files-for-dmgr
This script collects the following files:
- AppServer/lib/wkplc.comp.registry.jar
AppServer/lib/wp.wire.jar
AppServer/plugins/com.ibm.ws.portletcontainer.deploytask_6.1.0.jar
AppServer/profiles/Dmgr01/config/.repository/metadata_wkplc.xml
NOTE:This failure will not cause any functional problems nor will it specifically cause a ConfigEngine script to fail. If you receive a BUILD FAILED and this exception occurs, this exception has nothing to do with why the ConfigEngine script failed.
Resolving The Problem
To prevent this error from displaying, follow these steps:
1. On the Portal node, run the following ConfigEngine script:
- ConfigEngine.sh|bat collect-files-for-dmgr
2. Extract the collection to some temporary directory. You should get a file structure that includes the following:
- AppServer/lib/wkplc.comp.registry.jar
AppServer/lib/wp.wire.jar
AppServer/plugins/com.ibm.ws.portletcontainer.deploytask_6.1.0.jar
AppServer/profiles/Dmgr01/config/.repository/metadata_wkplc.xml
3. Ensure that the four files listed in Step 2 are copied to your DMGR.
4. Restart the DMGR
Was this topic helpful?
Document Information
Modified date:
03 December 2021
UID
swg21330596