Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Severe error on confluence startup

Gavin Kennedy
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 27, 2019

SEVERE [main] org.apache.catalina.core.StandardServer.await StandardServer.await: create[localhost:8000]:
 java.net.BindException: Address already in use: JVM_Bind

 

Any ideas - confluence won't start....

3 answers

1 vote
Alexis Robert
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 27, 2019

Hi @Gavin Kennedy , 

 

this means that you probably have another application (Jira maybe ?) that is running on the same port than Confluence.

You will need to check what processes are running, and change Confluence port or stop these other applications.

You can follow this documentation to change Confluence port.

 

Let me know if you have any questions, 

 

--Alexis

0 votes
Ben
Contributor
May 18, 2019 edited

HI,

I also have that kind of problem, confluence complains since a week or so about the error below.  My tomcat confluence server is listening on  8090  and for synchrony on 8092.

This morning I had a process running on 8090. But af ter i stopped that external proces I still get this error, and the thing is: confluence is not running on port  8000.

Any suggestions, maybe confluence is  set back to a default somewhere which might be port 8000 ?

Thanks

18-May-2019 13:23:21.903 SEVERE [main] org.apache.catalina.core.StandardServer.await StandardServer.await: create[localhost:8000]:
java.net.BindException: Address already in use (Bind failed)
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
at java.net.ServerSocket.bind(ServerSocket.java:375)
at java.net.ServerSocket.<init>(ServerSocket.java:237)
at org.apache.catalina.core.StandardServer.await(StandardServer.java:422)
at org.apache.catalina.startup.Catalina.await(Catalina.java:770)
at org.apache.catalina.startup.Catalina.start(Catalina.java:716)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:350)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:492)

Alexis Robert
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 19, 2019

Hi @Ben , 

 

I think port 8000 is used for the shutdown connector. You should basically try to list the processes listening on that port with "netstat -laputen | grep 8000" and try to kill the process.

 

Let me know if this helps, 

 

--Alexis

0 votes
Petr Vaníček
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 27, 2019

Hi, 

it's not starting because you are already using port 8000. You should change it to another one in INSTALL-DIR/conf/server.xml

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events