Confluence (3.5.4) won't start anymore due to UnknownHostException: svn.atlassian.com
Asked by Hannes Haataja:

I have a really old version of confluence (3.5.4) that's been running fine until recently i had to restart confluence after switch it did not start anymore.

```
2015-04-13 15:58:47,959 INFO [main] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 3.5.4 (build #2156)2015-04-13 15:58:49,667 INFO [main] [atlassian.plugin.manager.DefaultPluginManager] init Initialising the plugin system2015-04-13 15:58:49,815 INFO [main] [atlassian.plugin.manager.DefaultPluginManager] init Plugin system started in 0:00:00.1472015-04-13 15:58:50,723 INFO [main] [springframework.web.context.ContextLoader] initWebApplicationContext Root WebApplicationContext: initialization started2015-04-13 15:58:52,362 INFO [main] [com.atlassian.confluence.lifecycle] &lt;init&gt; Loading EhCache cache manager2015-04-13 15:58:53,005 ERROR [main] [sf.hibernate.cfg.Configuration] addInputStream Could not configure datastore from input streamorg.dom4j.DocumentException: svn.atlassian.com Nested exception: svn.atlassian.comat org.dom4j.io.SAXReader.read(SAXReader.java:358)at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:287)....Nested exception:java.net.UnknownHostException: svn.atlassian.com        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178)        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)        at java.net.Socket.connect(Socket.java:579)        at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618)        at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:160)        at sun.net.NetworkClient.doConnect(NetworkClient.java:180)        at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)        at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)        at sun.net.www.protocol.https.HttpsClient.&lt;init&gt;(HttpsClient.java:275)        at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371)..
```

DNS is resolving other addresses fine so does not seem to be a dns issue.

How can I resolve this?


Answers:
author: Joe Clark
body: This is actually a bug in Confluence 3.5.4 - upgrading to Confluence 3.5.5 will fix it.

<https://jira.atlassian.com/browse/CONF-22528>

The bug is now more crucial now that svn.atlassian.com doesn't exist any more :smile:

comments: author: Hannes Haataja
body: Installing the patch fixed the problem and Confluence started normally! Thanks a lot!


author: Norman Abramovitz
body: Atlassian does not support Subversion repositories anymore. They moved to Git. So, svn.atlassian.com does not exist. You can try faking out that uri in your local host file and see if you can get your system back up. I would point it back to own machine.

If the gets you up, I would try to find where svn.atlassian.com is configured/used and remove it.

comments: author: Hannes Haataja
body: Thanks for the info! I tried setting up the fake url to localhost but apparently the address has to be valid as i got a 'java.net.ConnectException: Connection refused' instead.


author: Norman Abramovitz
body: Hmm, that's too bad. I would continue faking things up like installing a dummy subversion server on a machine and then pointing svn.atlassian.com to that web services. You could also try looking at your configuration and database tables to see if can disable things as well. Backup before making changes in case things goes terribly wrong.Atlassian support might be able to help, but


Tags: confluence-administration