Troubleshooting Connections to the Presto Repository
The most common problem when the Presto Server server does not restart successfully after you move the Presto Repository to a new database is that is cannot connect to the Presto Repository. To verify that this is the problem:
1. Open the Presto Server log file prestoserver.log in your web application server’s log directory. For TomEE, this is:
web-apps-home/logs/prestoserver.log
2. Check for a log entry for Cannot create PoolableConnectionFactory near the end of the file. This error indicates the Presto Server could not successfully connect to the new database.
Common causes for this error include:
The database hosting the
Presto Repository is not running.
If this is true, start the Presto Repository and verify that it is up. Then restart the Presto Server and confirm that this starts successfully.
There are one or more firewalls between the
Presto Repository and the
Presto Server that are not configured to allow this connection.
Note: | This can only happen when the database for the Presto Repository is hosted on a different server than the Presto Server. |
Update the firewall configuration to allow this connection. Then restart the Presto Server and confirm that this starts successfully.
The URL or other connection configuration that you entered in
Presto for the
Presto Repository is incorrect.
To correct an error in this case, edit the resource properties for the Presto Repository in the presto-install/apache-tomee-jaxrs/conf/tomee.xml file.
Then restart the Presto Server and confirm that this starts successfully.
Port or connection configuration for the database is not set up properly to allow connections from the
Presto Server. See documentation for your database for more information.
