Troubleshooting
Problem
You create a stand-alone profile with the option to delay running the database scripts or clusters that are created using the deployment environment. Then, you see a CWLLG1162E error in the log files and a 500 error when you access the Process Center or other consoles.
Symptom
You see the following errors in the log files:
[7/7/11 14:43:27:080 EDT] 0000005e wle_security E CWLLG1162E: An exception occurred while setting the attribute Locale to value en for user froadmin. Error: com.lombardisoftware.client.delegate.BusinessDelegateException: java.lang.NullPointerException
com.lombardisoftware.client.delegate.BusinessDelegateException: java.lang.NullPointerException
at com.lombardisoftware.client.delegate.BusinessDelegateException.asBusinessDelegateException(BusinessDelegateException.java:41)
at com.lombardisoftware.client.delegate.PersistenceServicesDelegateDefault.findSingleByFilter(PersistenceServicesDelegateDefault.java:302)
at com.lombardisoftware.client.persistence.UserAttributeFactory.findByUserKey(UserAttributeFactory.java:46)
at com.lombardisoftware.userorg.UserOrgModule.setUserAttribute(UserOrgModule.java:501)
at com.lombardisoftware.server.ejb.security.SecurityCore.setUserAttributes(SecurityCore.java:755)
at com.lombardisoftware.server.ejb.security.SecurityCore.setUserLocalePreferences(SecurityCore.java:617)
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.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
.
Caused by: java.lang.NullPointerException
at com.lombardisoftware.server.ejb.persistence.dao.UserAttributeDAO.findByFilter(UserAttributeDAO.java:41)
at com.lombardisoftware.server.ejb.persistence.DefaultHandler.findByFilter(DefaultHandler.java:154)
at com.lombardisoftware.server.ejb.persistence.PersistenceServicesCore$5.call(PersistenceServicesCore.java:173)
at com.lombardisoftware.server.ejb.persistence.PersistenceServicesCore$5.call(PersistenceServicesCore.java:171)
at com.lombardisoftware.server.ejb.persistence.versioning.BranchManager.readAccess(BranchManager.java:143)
at com.lombardisoftware.server.ejb.persistence.PersistenceServicesCore.findByFilter(PersistenceServicesCore.java:171)
at com.lombardisoftware.server.ejb.persistence.PersistenceServicesCore.findSingleByFilter(PersistenceServicesCore.java:183)
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.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
... 75 more
Cause
The system data is not loaded into the database by the bootstrapProcessServerData script.
Resolving The Problem
Stand-alone profile
During the stand-alone profile creation process, the bootstrapProcessServerData code automatically populates the database with the system information. If you delay running the database scripts during the profile creation process, you have to run the bootstrap script manually.
To populate the bootstrap data into a stand-alone profile server, run the bootstrapProcessServerData command from the profile bin directory. For example:
C:\<install_root>\profiles\ProcCtr01/bin
Network deployment environment
After you generate clusters using the deployment environment, you must run the bootstrapProcessServerData command using network deployment parameters. This process populates the bootstrap data into a server part of a network deployment environment.
Run the bootstrap utility from the command line. The bootstrap utility is found in the deployment manager profile directory. For example:
cd install_root/profiles/Dmgr01/bin
bootstrapProcessServerData -nodeName node01 -serverName AppClusterMember1
install_rootis the location where you installed the product.
Additional Tips:
For the Network Deployment -serverName option, use the cluster member name where the Process Center or Process Server is configured. If you use the deployment environment to create a network deployment topology, the Process Center or Process Server is configured on the AppCluster member. You can confirm, by checking where the IBM_BPM_Teamworks_<node_serverName>.ear file is mapped.
The Bootstrap operation is run only one time; even if you have multiple nodes and cluster members. If you have a problem running the bootstrap operation , make sure the 98database.xml file has the correct database information and the user specified has privileges to update the database. See the Best practice to change values in the 98database.xml file information.
For more information, see the information center link in the Related information section.
Related Information
Product Synonym
BPM
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21508659