Possible bug with install of Confluence 4.3.7 - listening on wrong port, despite custom install

[Kimberly McKinnis]

I chose custom install for a new install with our developer license, so I could install it alongside another Confluence for testing. However, it can't start due to port 8000 already being in use, when I specifically chose a different port (8001). This confuses me and I cannot find any user error here. Here is the output of the install:

root@devtools-test:~# ./atlassian-confluence-4.3.7-x64.bin

Unpacking JRE ...

Starting Installer ...

This will install Confluence 4.3.7 on your computer.

OK o, Enter , Cancel c

Choose the appropriate installation or upgrade option.

Please choose one of the following:

Express Install (uses default settings) 1 , Custom Install (recommended for advanced users) 2 , Upgrade an existing Confluence installation 3, Enter

2

Where should Confluence 4.3.7 be installed?

/opt/atlassian/confluence

/opt/atlassian/confluencedocs

Default location for Confluence data

/var/atlassian/application-data/confluence

/var/atlassian/application-data/confluencedocs

Configure which ports Confluence will use.

Confluence requires two TCP ports that are not being used by any other

applications on this machine. The HTTP port is where you will access

Confluence through your browser. The Control port is used to Startup and

Shutdown Confluence.

Use default ports (HTTP: 8090, Control: 8000) - Recommended 1, Enter , Set custom value for HTTP and Control ports 2

2

HTTP Port Number

8090

8091

Control Port Number

8000

8001

Confluence can be run in the background.

You may choose to run Confluence as a service, which means it will start

automatically whenever the computer restarts.

Install Confluence as Service?

Yes y, Enter , No n

y

Extracting files ...

Please wait a few moments while Confluence starts up.

Launching Confluence ...

Installation of Confluence 4.3.7 is complete

Your installation of Confluence 4.3.7 is now ready and can be accessed via

your browser.

Confluence 4.3.7 can be accessed at http://localhost:8091

Finishing installation ...

And here is the complaint in the log, though I will attach the full one:

SEVERE: StandardServer.await: create 8000 :

java.net.BindException: Address already in use

at java.net.PlainSocketImpl.socketBind(Native Method)

at java.net.PlainSocketImpl.bind(Unknown Source)

at java.net.ServerSocket.bind(Unknown Source)

at java.net.ServerSocket.<init>(Unknown Source)

at org.apache.catalina.core.StandardServer.await(StandardServer.java:406)

at org.apache.catalina.startup.Catalina.await(Catalina.java:676)

at org.apache.catalina.startup.Catalina.start(Catalina.java:628)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

Feb 14, 2013 1:06:11 AM org.apache.coyote.http11.Http11Protocol pause

INFO: Pausing Coyote HTTP/1.1 on http-8091

Feb 14, 2013 1:06:12 AM org.apache.catalina.core.StandardService stop

It is obviously the other Confluence install listening on port 8000, as expected:

root@devtools-test:~# netstat -anp | grep LIST

tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 1885/mysqld

tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 761/sshd

tcp6 0 0 :::8080 :::* LISTEN 529/java

tcp6 0 0 :::22 :::* LISTEN 761/sshd

tcp6 0 0 :::8090 :::* LISTEN 13943/java

tcp6 0 0 127.0.0.1:8000 :::* LISTEN 13943/java

tcp6 0 0 127.0.0.1:8005 :::* LISTEN 529/java

[Kimberly McKinnis]

Pretty sure this is a bug on Atlassian's end. I had to manually edit server.xml because it still said port 8000. You can see from the install output that I did choose a different port. Thanks Atlassian!