When a JSP website shows database connection errors, the cause is usually not the JSP page itself, but a problem between your Java application, the Tomcat service, and the MySQL database settings. In a hosted environment, this can happen after a password change, a database rename, an incorrect JDBC URL, a stopped service, or a connection limit being reached. In many cases, the website still loads the application, but fails when the code tries to open a database session.
If your site is running on a managed Java hosting setup with Plesk and a private Tomcat instance, the good news is that most database connection issues can be diagnosed without changing the application architecture. The key is to check the database name, user permissions, host value, JDBC driver, Java version, and service status in the right order.
Common reasons a JSP site cannot connect to MySQL
JSP applications usually connect to MySQL through JDBC. If any part of that chain is wrong, the application may return errors such as Communications link failure, Access denied, Unknown database, or a generic application error page.
1. Wrong database credentials
The most common reason is an incorrect database username or password in the application configuration. This can happen after:
- a control panel password reset
- copying a site from staging to live
- importing a project from another environment
- editing the configuration file manually
Even a single wrong character in the password will prevent the JDBC connection from working.
2. Incorrect database host value
In hosting environments, MySQL is often accessed using a specific host name rather than localhost, depending on the platform setup. Some applications work only with the exact database host provided in the hosting control panel. If the application is configured with the wrong host, the connection request may fail before authentication even starts.
3. The database user does not have permission
In MySQL, a user must be assigned to the correct database with the needed privileges. A valid username and password are not enough if the account is not linked to the database or if permissions were removed. This often causes Access denied errors or failures when the application tries to read tables.
4. The JDBC connection string is outdated
JSP applications often store the MySQL connection URL in a properties file, XML config, environment variable, or Java source file. If the URL uses an old database name, an old port, the wrong SSL mode, or an obsolete driver class, the application may no longer connect after a migration or update.
5. MySQL service or resource limits
In a shared hosting or managed hosting setup, temporary resource limits can interrupt database access. For example:
- MySQL connection limits reached
- account resource limits hit during peak traffic
- database service temporarily unavailable
- application creating too many short-lived connections
If the site works sometimes and fails at busy times, this is a strong sign that the problem may be related to connection handling or usage limits rather than a bad password.
6. Java, Tomcat, or driver mismatch
A JSP site can fail to connect if the JDBC driver is not compatible with the Java version or if the application is deployed on a Tomcat instance that uses a different runtime than expected. This is especially important when running a private JVM or a custom Tomcat version through a control panel extension such as My App Server.
How to check the issue in Plesk or a managed hosting panel
When troubleshooting database connection errors, start in the hosting control panel. This helps you confirm whether the problem is in the account settings or inside the application code.
Check the database name and user
Open the database management area and verify that:
- the database exists
- the database user exists
- the user is assigned to that database
- the password matches the one used by the application
If the site was recently migrated or restored, confirm that the application configuration was updated to match the current database name and user.
Confirm the database host
Use the database host value shown in the hosting panel. Do not assume that localhost is always correct. Some setups use a dedicated internal host name or a specific endpoint that the application must use.
Review the Tomcat or application logs
For JSP hosting, the logs are often the fastest way to identify the exact cause. Look for messages such as:
Access denied for userUnknown databaseCommunications link failureToo many connectionsPublic Key Retrieval is not allowedClassNotFoundExceptionfor the MySQL driver
If the error appears in the application log but not in the browser, it usually means the database connection is failing inside the Java code after the page starts loading.
Check the service status
If you are using a private Tomcat service in a managed hosting account, verify that the service is running. A stopped or restarting service can make the website appear broken, even when the database is healthy.
In a setup that uses My App Server, the Tomcat instance is managed separately from the web server, so service status matters. If the JVM or Tomcat service is down, the JSP application may not reach the code that opens the MySQL connection.
Fixing the most frequent MySQL connection errors
Access denied for user
This usually means the username, password, or permissions are wrong.
Try the following:
- Reset the database password in the hosting panel.
- Update the password in the application configuration.
- Confirm that the user is assigned to the correct database.
- Make sure the username format is correct for the hosting account.
If the site uses a connection pool, restart the Tomcat service after changing credentials so old connections are cleared.
Unknown database
This means the application is trying to open a database that does not exist or is spelled incorrectly.
Check for:
- typos in the database name
- migration to a new database name
- case sensitivity in configuration files
- old staging settings still being used on production
Update the database name in the JDBC configuration and redeploy the application if needed.
Communications link failure
This error often points to a network, host, or timeout issue rather than a wrong username and password.
Possible causes include:
- wrong database host
- MySQL service not reachable
- firewall or local connection restriction
- timeout because connections are not being reused properly
- database server overloaded
Check whether the app is using the correct JDBC URL and whether the host value matches the one provided in the control panel.
Too many connections
This means the application or multiple applications are opening more MySQL sessions than allowed.
To reduce the problem:
- make sure database connections are closed after use
- review the connection pool settings
- avoid opening a new connection for every request if pooling is available
- check for loops or background tasks that repeatedly connect to MySQL
In JSP applications, poor connection handling can quickly exhaust available resources on a shared hosting account.
JDBC configuration points to review
When a JSP application fails to connect to MySQL, the issue is often in the JDBC configuration file. Review the following items carefully.
Database URL
Make sure the JDBC URL matches the correct format for your MySQL version and hosting setup. A typical MySQL URL includes the host, port, and database name. If SSL is required or disabled by the environment, the URL may need an additional parameter.
Examples of things to verify:
- correct host name
- correct port number
- correct database name
- matching character encoding
- SSL settings compatible with the server
Driver class
Confirm that the application uses the correct MySQL JDBC driver class and that the driver JAR is present in the application or Tomcat library path. If the driver is missing, the application may fail before any database connection attempt is made.
Username and password storage
Credentials are often stored in:
web.xml- properties files
- Spring configuration
- application-specific config files
- environment variables
Check every place where the application can load database settings. In some projects, an old file remains in the deployment package and overrides the one you edited.
Connection pooling settings
If the app uses a connection pool, incorrect settings can create repeated failures. Review:
- maximum pool size
- idle timeout
- validation query
- test on borrow
- maximum wait time
Bad pool settings can cause the application to report database errors even when MySQL itself is available.
What to do if you are using My App Server
In a hosting setup with My App Server, you can manage a private Tomcat and JVM from the control panel. This is useful for JSP hosting because it keeps your Java application isolated from other sites in the same account and gives you more direct control over the runtime.
Restart the application service after configuration changes
After changing database credentials, JDBC settings, or driver files, restart the Tomcat service. This reloads the application and clears cached connections. If the application was holding old credentials in memory, a restart is often required before the new settings take effect.
Verify the Java version
Some JDBC drivers and application frameworks require a specific Java version. If the site worked before a Java upgrade, the new runtime may have changed driver behavior or compatibility. Check whether the selected Java version matches the needs of your app.
Check the deployed WAR or exploded app
If you upload a WAR file or deploy a JSP application manually, confirm that the configuration file included in the deployment package is the updated one. A common mistake is editing a local file but deploying an older build to the server.
Watch for duplicate database configurations
Some Java applications contain more than one database config location. For example, a framework may read settings from both a properties file and a servlet context parameter. Make sure the active path is the one you changed.
Step-by-step troubleshooting checklist
Use this checklist to isolate the cause quickly.
- Confirm that the database exists in the hosting panel.
- Check that the database user is assigned to that database.
- Verify the password used by the application.
- Confirm the database host value in the JDBC URL.
- Review the MySQL and Tomcat logs for the exact error message.
- Check whether the MySQL JDBC driver is installed and compatible.
- Restart the Tomcat or My App Server service after changes.
- Test whether the issue appears on all pages or only on one function.
- Look for connection pool exhaustion or too many connections.
- If needed, test the database credentials from a simple server-side test page or a lightweight connection test in the application.
Best practices to avoid future connection errors
Once the site is working again, a few good practices can help prevent the issue from coming back.
Keep configuration in one place
Use a single, clearly documented file or environment source for database settings. This reduces the chance of editing the wrong value during updates or deployments.
Use the hosting control panel for credential changes
When a password is changed in the control panel, update the application immediately and restart the service if needed. Avoid leaving old credentials in test files or backup configs.
Monitor logs regularly
Even a working JSP site can start showing early warning signs before a full failure. Repeated warnings about connection timeouts, retries, or authentication problems should be investigated early.
Reuse connections correctly
Make sure the application closes connections, statements, and result sets properly. If pooling is enabled, tune it to suit the size of the application and the hosting limits.
Keep the JDBC driver current
Use a MySQL JDBC driver version compatible with both your Java runtime and the MySQL server version. Driver mismatches are a common source of unexpected connection problems after upgrades.
FAQ
Why does my JSP site work on some pages but not on others?
This usually means only certain pages use the database. Static pages or pages without database queries may load normally, while pages that require MySQL fail when they try to fetch data.
Why do I get a database error only after deploying a new WAR file?
The new deployment may contain outdated credentials, a missing JDBC driver, or a configuration file that does not match the live database setup. Compare the deployed settings with the current values in the hosting panel.
Can a Tomcat restart fix database connection errors?
Yes, in some cases. Restarting Tomcat clears cached connections and reloads application settings. It will not fix wrong credentials or an invalid database host, but it can resolve stale connections after a password change or deployment update.
Why would the same app work locally but fail on hosting?
Local and hosted environments often differ in database host name, driver version, MySQL permissions, and Java runtime. A JSP app that connects successfully on a local machine may still fail if the hosted configuration does not match.
Do I need to edit Java code to fix every database error?
Not always. Many connection issues are caused by control panel settings, configuration files, or service status rather than application logic. Start with the database credentials, host, and logs before changing code.
Conclusion
When a JSP website shows database connection errors in the UK market, the most likely causes are incorrect MySQL credentials, a wrong host value, missing permissions, driver issues, or a Tomcat service that needs attention. In a managed hosting setup with Plesk and My App Server, these problems can usually be solved by checking the control panel settings, reviewing logs, and restarting the Java service after updates.
If the application uses a private Tomcat or a custom Java runtime, always confirm that the JDBC driver, Java version, and configuration files match the live database setup. A methodical check of the connection chain will usually identify the issue faster than guessing in the code.