Archived Content: This information is no longer maintained and is provided "as is" for your convenience.
Summary
Error
Problem is seen in BSM servers that are upgraded from any prior version to BSM 9.26IP1 and above
After upgrade, users notice that RUM configuration from their RUM applications is missing
Other symptoms:
- Failed to get RUM Engine. System error occurred {0} pop-up when trying to access Admin - EUM - Setting tab - Real User Monitor settings or when trying to manually add an engine to a RUM application
- From RUM Engine can not syncronize BSM applications
- When tryiging to validate EUM/RUM model via JMX console show error: Failed to activate EUM Model Validator
- On log HPBSM\log\map-app.log
2017-03-05 23:15:03,918 [ajp-/127.0.0.1:8009-2] (EumException.java:53) ERROR - Failed to get RUM configuration for Logical Application CIs. System error occurred:{0 com.mercury.am.eum.shared.management.exceptions.EumGeneralException: Failed to get RUM configuration for Logical Application CIs. System error occurred: {0}
at com.mercury.am.eum.shared.operations.Operation.execute(Operation.java:94)
- On HPBSM\log\eum.log
2017-03-05 19:00:10,065 [http-/127.0.0.1:8080-2] (SessionDimFS.java:152) ERROR - Failed to read RUM session properties.
com.mercury.am.eum.shared.management.exceptions.EumGeneralException: Failed to get RUM configuration for Logical Application CIs. System error occurred: {0}
at com.mercury.am.eum.shared.operations.Operation.execute(Operation.java:94)
-On HPBSM\log\map-app-msg.log
2017-03-21 06:08:58,094 [ajp-/127.0.0.1:8009-12] ERROR - Failed to convert jpa bean, type=RumAppConfigJpa
java.lang.NullPointerException
at com.mercury.am.eum.rum.model.types.RumAppConfigPropertyType.getInstance(RumAppConfigPropertyType.java:27)
at com.mercury.am.eum.rum.model.jpa.RumAppConfigJpa.getAppConfigPropertyTypeEnum(RumAppConfigJpa.java:1314)
at com.mercury.am.eum.rum.model.impl.RumAppConfigImpl.copyDataFromBean(RumAppConfigImpl.java:191)
at com.mercury.am.eum.rum.model.dto.RumAppConfigDto.<init>(RumAppConfigDto.java:165)
Cause
If a RUM application was defined on a version before BSM 9.26IP1 , it is possible that it does not have a corresponding row on eumrum_properties table on management schema.
Starting from 9.26IP1 R&D started use this eumrum_properties table to keep additional configuration items (docker related). Before 9.26IP1 this was not a problem because they used this table to keep the data that was relevant only for mobile applications
Fix
SELECT app_tier_id FROM eumrum_applications
EXCEPT
SELECT parent_id FROM eumrum_properties
2. Will get the list of IDs
INSERT INTO eumrum_properties (PARENT_ID, PARENT_TYPE, PARENT_CMDB_ID, CUSTOMER_ID, ENTITY_ID, PROPERTY_TYPE, PROPERTY_VALUE)
VALUES (58, 'HTTP_WEB', 1, 1, 58, 'docker_set', 'false;exposed')
(use ids from the list for highlighted items)
There is a tool created by R&D that automates this process. (FixQCCR1I120054UsingDbAccess_v1.1.zip)
All messages that are shown on the command window are also logged into the <unix_timestamp>_FixQCCR1I120054.log file