cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

Knowledge Base

Why am I seeing "java.sql.SQLException: Connections could not be acquired from the underlying database!"?

Updated 7/12/18

 

Symptoms

The EUM Server crashes with the following error in log files:
java.sql.SQLException: Connections could not be acquired from the underlying database!

Stack trace from eum-processor.log:

stack trace from eum-processor.log screenshot.png

Diagnosis

1) One reason why this issue occurs is due to the complexity of the password used for the property onprem.dbPassword inside the eum.properties file. This property is used to specify the user password to the EUM database.

 

2) Starting with the 4.4.x release, as EUM has its own database, this error can even surface when the EUM database is not running at all.

 

Solution

The solution to the first problem would be to use simpler passwords (e.g., without non-alphanumeric characters) for the property onprem.dbPassword.

 

Once the property above is modified with a simpler password, complete the following steps:

  1. Save and close the properties file.

  2. Restart the EUM server.

 

For the second issue, make sure that the database is started before starting the EUM server using the commands below:

export JAVA_HOME=<EUM_INSTALL_DIR>/jre

cd <EUM_INSTALL_DIR>/orcha/orcha-master/bin
./orcha-master -d mysql.groovy -p ../../playbooks/mysql-orcha/start-mysql.orcha -o ../conf/orcha.properties -c local

 

See our technical documentation for additional information on starting and stopping the EUM server and database.


Note: You will have to export the JAVA_HOME variable before running these commands.

 

If there is a need for a complex password, it can be done later using the encrypted password generated via below steps:

  1. Encrypt the new database password using the credential key that you enter during installation:

    • On Linux: 


      bin/eum-credential-key.sh encrypt -storepass <plain_credential_key> -plaintext <New_DB_password>
 
    • On Windows:
 

      bin\eum-credential-key.bat encrypt -storepass <plain_credential_key> -plaintext <New_DB_password>

      The command prints out the encrypted form of the DB_password value you entered.

  2. Copy the output from the previous command to your clipboard. 
 
  3. Open bin/eum.properties for editing and replace the value of the onprem.dbPassword setting with the new encrypted password you copied to your clipboard. 
  4. Save and close the properties file.

  5. Restart the EUM server.
Version history
Last update:
‎07-31-2018 10:00 AM
Updated by:
Labels (1)


Found this article helpful? Click the Thumbs Up button.
Have an additional comment? Post it below.
By replying you agree to the Terms and Conditions of the AppDynamics Community.