Forums

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

Application Links

tell son
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!
July 14, 2020

Hi there

We have trouble about make application links between jira(8.9.0) server and confluence(7.5.1) server.

We using aws EC2, jira use 8443 port and confluence use 9443 port

At first try we make application links, but can't make connect between two. 캡처.PNG

second we try make jira custom server -> custom directory, and last when we try in confluence we receive this [org.apache.http.conn.ConnectTimeoutException: Connect to 161.189.217.105:18080 [/161.189.217.105] failed: connect timed out] as figure show belowimage001(07-15-10-41-06).png

 

below is confluence log 

Caused by: com.atlassian.crowd.exception.OperationFailedException: org.apache.http.conn.ConnectTimeoutException: Connect to 161.189.217.105:18080 [/161.189.217.105] failed: connect timed out
at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:378)
at com.atlassian.crowd.integration.rest.service.RestCrowdClient.searchUsers(RestCrowdClient.java:513)
at com.atlassian.crowd.integration.rest.service.RestCrowdClient.testConnection(RestCrowdClient.java:503)
at com.atlassian.crowd.directory.RemoteCrowdDirectory.testConnection(RemoteCrowdDirectory.java:668)
at com.atlassian.crowd.embedded.core.CrowdDirectoryServiceImpl.testConnection(CrowdDirectoryServiceImpl.java:61)
... 367 more
Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to 161.189.217.105:18080 [/161.189.217.105] failed: connect timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
at org.apache.http.impl.client.cache.CachingExec.callBackend(CachingExec.java:592)
at org.apache.http.impl.client.cache.CachingExec.execute(CachingExec.java:269)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.executeCrowdServiceMethod(RestExecutor.java:495)
at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:367)
... 371 more
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:75)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
... 383 more
2020-07-15 02:50:47,993 INFO [Caesium-1-4] [agent.service.check.StaleChecksCleaner] info Cleaning stale checks

 

please help me solve this issue, thanks

 

 

 

 

1 answer

1 accepted

0 votes
Answer accepted
Joshua Sneed Contegix
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.
July 15, 2020

Hi tell son,

Is the use of port 18080 intentional? Jira tends to use port 8080 unless otherwise specified. You have also indicated that Jira is using port 8443, meaning Jira is using SSL, but you are using HTTP in the URL instead of HTTPS.

I would try HTTPS instead of HTTP in the URL, I would try without a port or with 8080, and try using the actual URL instead of the IP address if DNS is configured. Cheers.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
7.5.1
TAGS
AUG Leaders

Atlassian Community Events