Confluence - Communications link failure

[zoha khoshnoodi]

Hi 

my confluence server was shut down and after it tun on again my confluence can't start anymore. I check the log and found these errors there:

ERROR [localhost-startStop-3] [engine.jdbc.spi.SqlExceptionHelper] logExceptions Communications link failure

 ERROR [Gemini Blueprint context shutdown thread1] [engine.jdbc.spi.SqlExceptionHelper] logExceptions Communications link failure

what should I do? 

the only thing that I change is my server password and not any thing else.

[Igor M. · Accepted solution]

Hello,

Please make sure your DB server is up, running and reachable from Confluence server.

Check if you do not have any duplicate processes for confluence running if you do, kill them and try to start confluence again.

Have you changed anything on DB side, like DB password? If yes, then you need to upgrade that too as per How to find Confluence's database connection parameters guide. 

Check catalina.out and atlassian-confluence.log for more clues as to why system does not boot

[zoha khoshnoodi]

I check all of them and find this warning in catalina.out :

WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] registered the JDBC driver [org.h2.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

also this :

03-Jul-2018 10:08:24.691 INFO [Abandoned connection cleanup thread] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load []. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load []. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.

[Igor M.]

Those Warning and Info level events appear to be unrelated. I would suggest making sure your DB is up and running, shit down and kill any confluence process in memory and attempt to start Confluence service again.

[zoha khoshnoodi]

.