EM failed to start with InvalidConfigurationException in APMEnterpriseManager.properties
Article ID: 108026
Updated On:
Products
Issue/Introduction
After upgrading EM from 10.5.2.15 to 10.7.0.45, the EM failed to start with the following errors:
[INFO] [main] [com.ca.wily.jasypt.APMEncryptablePropertyPlaceholderConfigurer] Loading properties file from URL [file:/app/apm/Introscope10.7.0.45/./config/APMEnterpriseManager.properties] com.ca.apm.crypto.InvalidConfigurationException: Given final block not properly padded at com.ca.apm.crypto.SecureCryptImpl.decrypt(SecureCryptImpl.java:160)
at com.ca.apm.crypto.jasypt.APMStringEncryptor.decrypt(APMStringEncryptor.java:88)
at com.ca.wily.jasypt.APMEncryptablePropertyPlaceholderConfigurer.convertPropertyValue(APMEncryptablePropertyPlaceholderConfigurer.java:50)
at org.springframework.beans.factory.config.PropertyResourceConfigurer.convertProperty(PropertyResourceConfigurer.java:121) ...
at java.lang.reflect.Method.invoke(Method.java:498) at com.zerog.lax.LAX.launch(Unknown Source)
at com.zerog.lax.LAX.main(Unknown Source) 7/26/18
[ERROR] [main] [com.wily.apm.model.SpringAppContext] [ Error Creating Spring Application Context with Spring configuration files classpath:jasyptEncryptor.xml]
Environment
CA Application Performance Management 10.7.0.45
Cause
The root cause was due to incorrect encrypted password in the tess-db-cfg.xml file.
Resolution
Reset the password in tess-db-cfg.xml by changing the plainTextPasswords property to true, and enter the password in plain text.
When the Enterprise Manager restarts, it will set the plainTextPasswords property back to false and encrypts the password.
Additional Information
Feedback
