Forums

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

Gadget Feed URL warning - Possible Timeout

Santiago Marcos
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 16, 2020

Hi everyone,

First of all, forgive the possible mistakes I can make, english is not may main language. One month ago, the error that you can read in the question started popping.

 

When I click "More info" to see the details of the error, it takes me to the troubleshooting page, then sometimes the error disappears (most of the times the auto check says it is O.K.) and sometimes doesn't. When it does not disappear the help shows me this link . Sure my Base URL is right and we don't use proxys. The thing is that I've been reading the logs and I found this:

 

2020-07-16 11:29:13,268 HealthCheck:thread-4 ERROR ServiceRunner [c.a.t.j.healthcheck.support.GadgetFeedUrlHealthCheck] An error occurred when performing the Gadget feed URL healthcheck
org.apache.http.conn.ConnectTimeoutException: Connect to myaddress.net:8443 [myaddress.net/x.x.x.x] 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:359)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
at com.atlassian.troubleshooting.jira.healthcheck.support.GadgetFeedUrlHealthCheck.check(GadgetFeedUrlHealthCheck.java:56)
at com.atlassian.troubleshooting.healthcheck.impl.PluginSuppliedSupportHealthCheck.check(PluginSuppliedSupportHealthCheck.java:50)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
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.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:339)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)

The problem is not just the error popping... the problem is the first login as a user... the Dashboard takes soooo long to load... that there is no way we can work like this. After that long loading period, you can browse all the issues very very fast, and even return to Dashboard quickly. The problem is the first login or getting back to dashboard after a few minutes.

Another symptom is when I try to add a gadget to my dashboard, it takes some time to load all of the available gadgets

Please, any help is welcome, I am completely desperated.

Considerations:

  • Jira Server is running over Windows.
  • We are runing Jira 7.6.1
  • The VM has enough RAM, and the monitoring JVM memory shows that everything is running smoothly.
  • We don't work through proxy.

0 answers

Suggest an answer

Log in or Sign up to answer