Switch to the JNDI connector

[Hans-Werner Hennes]

Hello, we have the problem that confluence has been sending mails several times for some time. In the log analyzer it is indicated that the timeout of the mail communication is to be increased. If I proceed according to instructions and exactly the settings for the conversion to the JNDI connector makes, then conflucence starts no more.

root@debian:/home/oed# /etc/init.d/confluence restart
executing using dedicated user
If you encounter issues starting up Confluence, please see the Installation guide at http://confluence.atlassian.com/display/DOC/Confluence+Installation+Guide

Server startup logs are located in /opt/atlassian/confluence/logs/catalina.out
Using CATALINA_BASE: /opt/atlassian/confluence
Using CATALINA_HOME: /opt/atlassian/confluence
Using CATALINA_TMPDIR: /opt/atlassian/confluence/temp
Using JRE_HOME: /opt/atlassian/confluence/jre/
Using CLASSPATH: /opt/atlassian/confluence/bin/bootstrap.jar:/opt/atlassian/confluence/bin/tomcat-juli.jar
Using CATALINA_PID: /opt/atlassian/confluence/work/catalina.pid
Jul 18, 2017 4:28:15 AM org.apache.catalina.startup.Catalina stopServer
SCHWERWIEGEND: Could not contact localhost:8000. Tomcat may not be running.
Jul 18, 2017 4:28:15 AM org.apache.catalina.startup.Catalina stopServer
SCHWERWIEGEND: Catalina.stop:
java.net.ConnectException: Verbindungsaufbau abgelehnt

Ask for help on what to do

[AnnWorley]

Please make sure that Confluence fully shut down before you restarted. The message:

Could not contact localhost:8000

 can indicate that Confluence is still holding onto port 8000 (the Tomcat shutdown port) from a previous startup so the new startup can't get the port.

You can run kill -9 on the Confluence PID if you want to force it to quit.