Troubleshooting Connections to the MashZone NextGen Repository
The most common problem when the MashZone NextGen Server server does not restart successfully after you move the MashZone NextGen Repository to a new database is that is cannot connect to the MashZone NextGen Repository. To verify that this is the problem:
1. Open the MashZone NextGen Server log file prestoserver.log in your web application server’s log directory. For Tomcat, 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 MashZone NextGen Server could not successfully connect to the new database.
Common causes for this error include:
The database hosting the
MashZone NextGen Repository is not running.
If this is true, start the MashZone NextGen Repository and verify that it is up. Then restart the MashZone NextGen Server and confirm that this starts successfully.
There are one or more firewalls between the
MashZone NextGen Repository and the
MashZone NextGen Server that are not configured to allow this connection.
Note: This can only happen when the database for the MashZone NextGen Repository is hosted on a different server than the MashZone NextGen Server.
Update the firewall configuration to allow this connection. Then restart the MashZone NextGen Server and confirm that this starts successfully.
The URL or other connection configuration that you entered in
MashZone NextGen for the
MashZone NextGen Repository is incorrect.
To correct an error in this case, edit the resource properties for the MashZone NextGen Repository in the MashZoneNG-install/apache-tomcat/conf/context.xml file.
Then restart the MashZone NextGen Server and confirm that this starts successfully.
Port or connection configuration for the database is not set up properly to allow connections from the
MashZone NextGen Server. See documentation for your database for more information.