Troubleshooting Confluence while Running as a Windows Service

  • If none of the above solves your problem, please refer to the complete list of known issues in our Knowledge Base.
  • When investigating memory issues or bugs, it may be useful to view information from Confluence's garbage collection. To turn on the verbose garbage collection, use the command:

    tomcat6 //US//Confluence ++JvmOptions="-Xloggc:<CONFLUENCE-INSTALL>\logs\atlassian-gc.log"
  • The Confluence 2.9 installer does not work when installed as service, due to a missing semi-colon in service.bat. Please refer to reported issue CONF-12785.
  • You can use a Sysinternals tool called Procmon.exe from the The Microsoft Windows Sysinternals Team, to check that the error occurred at the specific time when the Confluence service started. You need to match the time when Tomcat failed, as captured by this tool, against the time in the Windows Event Viewer.

    Note

    We do not recommend that you run this tool for too long as it may disrupt other Atlassian applications. Once you have captured the required information you will need to press Ctrl + E to stop capturing.

Requesting Support

If, after following the troubleshooting guide above, you still cannot make Confluence run as a Windows Service or if there is an error when setting the JVM configuration for the service, you can create a support request.

Please provide the following information when creating your support request, because we will need it to assist you:

  • Are you running a 32 bit or 64 bit Windows?
  • Give us the result of running java -version from Windows command line console.
  • A screen shot of your Windows Registry setting for Tomcat.
  • If you have modified service.bat, please give us a copy of this file for review.
  • What application server are you using? eg. Are you using the Confluence distribution?
  • Your atlassian-confluence.log file.
RELATED TOPICS

Start Confluence Automatically on Windows as a Service

  • No labels