nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Install JIRA Core and Confluence on the Same CentOS Server

Levi Rogers

I have found a few similar questions but they talk about using apache as a front end proxy. I am not sure I see why that is a requirement they are listening on different ports. I installed both in different directories and I see both ports listed in Netstat but I can only connect to one.

SELINUX is enabled. I am thinking something around that. We are evaluating with a Starter License to see if these products will be a good fit company wide.

Thanks for any help.

Accepted answers

Levi Rogers

Well silly me, I didn't add my firewall cmd permanently. So....it is good. Thanks for your help guys.

All comments

Evgeny Gryaznov

The answer is very simple. Two different process in CentOs CAN'T share one port number. Jira an Confluence use different TomCat process and different ports for running. Apache and Nginx usually bind to 80 port and redirect (proxy) requests to Jira or Confluence personal ports.

And don't forget, what you cant simple change port numbers in server.xml to 80 port, because ports 1-1024 allowed only for system (root) users.

To discover what wrong with your installation, just examine catalina.log in both (jira and confluentce) home root log directories.

Danyal Iqbal

+1 for examining the log. Make sure both products started up correctly.

-1 for installing both products on the same machine. (Bad Idea)

Just out of curiosity: Which one can you connect to?jira or confluence?

Levi Rogers

This is a test environment. That is why they are on the same server. They are listening on different ports 8080 and 8090, that is why I don't understand why it won't work.

JIRA Works, Confluence does not.

Confluence Log:

28-May-2018 19:46:11.046 INFO [192.168.11.32-startStop-2] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler.initialize Initializing ExecutorService 'defaultSockJsTaskScheduler'
28-May-2018 19:46:11.122 INFO [192.168.11.32-startStop-2] org.springframework.web.socket.server.support.WebSocketHandlerMapping.registerHandler Mapped URL path [/v1/bayeux-sync1] onto handler of type [class org.springframework.web.socket.server.support.WebSocketHttpRequestHandler]
28-May-2018 19:46:11.755 INFO [192.168.11.32-startStop-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.register Mapped "{[/healthcheck]}" onto public com.atlassian.synchrony.proxy.web.HealthCheckResult com.atlassian.synchrony.proxy.web.SynchronyProxyRestController.getSynchronyProxyInfo()
28-May-2018 19:46:11.756 INFO [192.168.11.32-startStop-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.register Mapped "{[/reload],methods=[PUT]}" onto public org.springframework.http.ResponseEntity com.atlassian.synchrony.proxy.web.SynchronyProxyRestController.reloadConfiguration(com.atlassian.synchrony.proxy.web.SynchronyProxyConfigPayload)
28-May-2018 19:46:11.825 INFO [192.168.11.32-startStop-2] org.springframework.web.servlet.handler.SimpleUrlHandlerMapping.registerHandler Mapped URL path [/**] onto handler of type [class org.springframework.web.servlet.resource.DefaultServletHttpRequestHandler]
28-May-2018 19:46:11.900 INFO [192.168.11.32-startStop-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.initControllerAdviceCache Looking for @ControllerAdvice: WebApplicationContext for namespace 'dispatcher-servlet': startup date [Mon May 28 19:46:10 CDT 2018]; root of context hierarchy
28-May-2018 19:46:12.085 INFO [192.168.11.32-startStop-2] org.springframework.context.support.DefaultLifecycleProcessor.start Starting beans in phase 2147483647
28-May-2018 19:46:12.132 INFO [192.168.11.32-startStop-2] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization completed in 1989 ms
28-May-2018 19:46:20.478 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8090"]
28-May-2018 19:46:20.489 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 13522 ms
[root@025s-jira-1 logs]# 28-May-2018 19:46:11.046 INFO [192.168.11.32-startStop-2] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler.initialize Initializing ExecutorService 'defaultSockJsTaskScheduler'
bash: 28-May-2018: command not found
[root@025s-jira-1 logs]# 28-May-2018 19:46:11.122 INFO [192.168.11.32-startStop-2] org.springframework.web.socket.server.support.WebSocketHandlerMapping.registerHandler Mapped URL path [/v1/bayeux-sync1] onto handler of type [class org.springframework.web.socket.server.support.WebSocketHttpRequestHandler]
bash: 28-May-2018: command not found
[root@025s-jira-1 logs]# 28-May-2018 19:46:11.755 INFO [192.168.11.32-startStop-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.register Mapped "{[/healthcheck]}" onto public com.atlassian.synchrony.proxy.web.HealthCheckResult com.atlassian.synchrony.proxy.web.SynchronyProxyRestController.getSynchronyProxyInfo()
bash: syntax error near unexpected token `('
[root@025s-jira-1 logs]# 28-May-2018 19:46:11.756 INFO [192.168.11.32-startStop-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.register Mapped "{[/reload],methods=[PUT]}" onto public org.springframework.http.ResponseEntity com.atlassian.synchrony.proxy.web.SynchronyProxyRestController.reloadConfiguration(com.atlassian.synchrony.proxy.web.SynchronyProxyConfigPayload)
bash: syntax error near unexpected token `('
[root@025s-jira-1 logs]# 28-May-2018 19:46:11.825 INFO [192.168.11.32-startStop-2] org.springframework.web.servlet.handler.SimpleUrlHandlerMapping.registerHandler Mapped URL path [/**] onto handler of type [class org.springframework.web.servlet.resource.DefaultServletHttpRequestHandler]
bash: 28-May-2018: command not found
[root@025s-jira-1 logs]# 28-May-2018 19:46:11.900 INFO [192.168.11.32-startStop-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.initControllerAdviceCache Looking for @ControllerAdvice: WebApplicationContext for namespace 'dispatcher-servlet': startup date [Mon May 28 19:46:10 CDT 2018]; root of context hierarchy
bash: 28-May-2018: command not found
bash: root: command not found
[root@025s-jira-1 logs]# 28-May-2018 19:46:12.085 INFO [192.168.11.32-startStop-2] org.springframework.context.support.DefaultLifecycleProcessor.start Starting beans in phase 2147483647
bash: 28-May-2018: command not found
[root@025s-jira-1 logs]# 28-May-2018 19:46:12.132 INFO [192.168.11.32-startStop-2] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization completed in 1989 ms
bash: 28-May-2018: command not found
[root@025s-jira-1 logs]# 28-May-2018 19:46:20.478 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8090"]
bash: 28-May-2018: command not found
[root@025s-jira-1 logs]# 28-May-2018 19:46:20.489 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 13522 ms
bash: 28-May-2018: command not found

JIRA Log:

[root@025s-jira-1 logs]# tail catalina.2018-05-28.log
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:802)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1410)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)

28-May-2018 19:20:48.461 WARNING [http-nio-8080-exec-8] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://025s-jira-1.xxx.local:8080/rest/gadget/1.0/login, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
28-May-2018 19:21:26.209 WARNING [http-nio-8080-exec-6] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://025s-jira-1.xxx:8080/rest/activity-stream/1.0/preferences?_=1527553285388, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.

Levi Rogers

They are not listening or running on the same port. 8080 and 8090 respectively. See my other attachment for logs. Thanks again.

Vickey Palzor Lepcha

@Danyal Iqbal I don't think running them on the same machine is a bad idea. I have been running them for ages now with no problem at all.

There could be only one issue - performance, but that's not an application issue, which can also be taken care of by pumping up the server resources.

Vickey Palzor Lepcha

Try increasing your memory allocation - addition of Synchrony causes huge memory usage in Confluence

Check your proccesses - see if everything has been clean shut down. Kill all your confluence process and try starting once again.

Levi Rogers

Well silly me, I didn't add my firewall cmd permanently. So....it is good. Thanks for your help guys.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

server

confluence-server

jira

jira-server