The following provides some general troubleshooting tips and subsections with categorized information to help you get back on track. Search for an answer to your question or browse the different troubleshooting topics.
View Server Log File
To troubleshoot unexpected behavior, the server.log file usually displays errors that can be read. During a startup, the server.log displays a lot of useful information and possible errors such as problems connecting to the database or similar.
A good procedure is to start a fresh log file to only get the information you need. To start a new log file, do the following:
Stop the application server.
Remove the old server.log (delete or archive) from standalone/log.
Start the application server.
Follow the server.log file in standalone/log/server.log.
Errors shown last in the file may be follow up symptoms of the original error. If you receive an error at the end of the log file, review the beginning of the file to find the first error, which is usually the cause.
For more information, see Logging.
To troubleshoot unexpected behavior, enable more detailed (debug) logging by running the following command in the JBoss CLI:
Do not get intimidated by long stack-traces but look for the message text and additional clues on lines starting with Caused by:. Reproduce issues in a test environment with full debug logging enabled and to find out under what circumstances the issue occurs, seemingly spontaneous or as a response to a certain set of actions or input? For more information, see Enabling Debug Logging and Logging.
Ensure that your configuration is correct and performed according to the steps described in the EJBCA Installation section.
Public forums for discussions and help requests are hosted on Sourceforge and there are also mailing lists to subscribe to.
Customers with a valid support contract can contact PrimeKey Support and search the PrimeKey Support Portal.