Troubleshooting
Problem
When you run the bootstrapProcessServerData.bat or bootstrapProcessServerData.sh command with an unknown cluster name, a null pointer exception might occur.
Symptom
A null pointer exception similar to the following text might occur in the command window and the bootstrap log file:
java.lang.NullPointerException
at com.ibm.bpm.bootstrap.BootstrapProcessServerDataHelper.determineClusterMember(BootstrapProcessServerDataHelper.java:828)
at com.ibm.bpm.bootstrap.BootstrapProcessServerDataHelper.init(BootstrapProcessServerDataHelper.java:135)
at com.ibm.bpm.bootstrap.BootstrapProcessServerDataHelper.bootstrapData(BootstrapProcessServerDataHelper.java:213)
at com.ibm.bpm.bootstrap.BootstrapHelper.execute(BootstrapHelper.java:91)
at com.ibm.websphere.management.async.client.AsyncCommandClient.execute(AsyncCommandClient.java:177)
at com.ibm.ws.scripting.adminCommand.AdminCmdController.executeCmd(AdminCmdController.java:1876)
at com.ibm.ws.scripting.adminCommand.AdminCmdController.processCmd(AdminCmdController.java:317)
at com.ibm.ws.scripting.adminCommand.AdminCmdProxyHandler.invoke(AdminCmdProxyHandler.java:92)
at com.ibm.ws.scripting.adminCommand.AdminCmdProxyBase.__method4(AdminCmdProxyBase.java:58)
at com.ibm.ws.scripting.adminCommand.AdminTask.bootstrapProcessServerData(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java)
at org.python.core.PyMethod.__call__(PyMethod.java)
at org.python.core.PyObject.__call__(PyObject.java)
at org.python.core.PyInstance.invoke(PyInstance.java)
at org.python.pycode._pyx50.f$0(<input>:1)
at org.python.pycode._pyx50.call_function(<input>)
at org.python.core.PyTableCode.call(PyTableCode.jaa)
at org.python.core.PyC
Cause
Currently, the bootstrapProcessServerData command does not run a prerequisite check for the cluster name. Therefore, a warning is not provided to indicate that the specified cluster name does not exist.
Resolving The Problem
Run the bootstrapProcessServerData command again with an existing cluster name.
Product Synonym
BPM
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21638917