How to Troubleshoot Common Java Hosting Startup Errors
If your web browser throws an error page or your app fails to launch after deployment, you can leverage log traces to figure out what went wrong.
Common Issues at Startup
- Unsupported Class Version Error: This occurs if you compile your application locally using a newer Java version (e.g., JDK 21) than the JDK runtime version selected inside your dashboard. To fix this, change your runtime version menu selection in the control panel to match your local setup, or recompile your code targeting the older framework.
- Context Initialization Failures: If your configuration properties files contain typos or your framework XML setup fails to initialize, the application server will throw a startup error and refuse to route traffic.
How to Read Your Application Logs
The system records all console outputs (stdout/stderr) and framework errors into localized system logs. You can access these traces directly via the panel interface:
- Go to your control panel dashboard and look for the Log Browser tool for your target domain.
- Look for the dedicated application server log files or general runtime log streams.
- Scroll to the bottom of the log viewer to track down recent exceptions, stack traces, or missing resource warnings that point out the exact line code failing initialization.
Refreshing the Application Lifecycle
If your application gets locked up due to an unhandled memory exception or database timeout, go to your Java dashboard menu area, click Disable, wait a minute, and click Enable to force clear the background processes and spin up a clean instance execution thread.
