-
Notifications
You must be signed in to change notification settings - Fork 1.8k
jira collector java.net.SocketTimeoutException #866
Comments
The collector is having issues communicating with jira. The connection is timing out. Try hitting the rest api manually to see if issues come back in a timely manner. You can also try decreasing the page size. |
Alredy tried what you are suggesting. Tried with curl from same place where I'm running the collector and its working file, I'm getting the response. Also tried decreasing the page size. Don't know what else to try. |
Turn up debugging by putting these in your properties file: logging.level.com.atlassian.jira=INFO
logging.level.com.capitalone.dashboard=DEBUG
logging.level.com.capitalone.dashboard.collector=DEBUG those options are not available through docker-compose so you have to modify the command that is run and point it to a mounted properties file. Is there more to the stack trace? What line is failing on in the hygieia code? |
Still not running anything with docker. I have Mongo Up, the API layer UP and connected to the DB, the UI is also showing me that is connected to the API successfully. Only the collector seems to be giving me problems, it is reaching the DB, cause i see it on the log file but for some reason is not getting anything from Jira and I'm getting that Timeout that I showed you.
|
Does curl work from within the running docker container? You can attach a bash shell to the container and run curl. Is your user account locked that it is trying to use? Is jira behind a proxy? The code is timing out attempting to get all of the projects on the jira server. |
@oshingc jira version? I have had problems with 7.1.9. In the past it could pull 200 issues in ~1 second. Now it takes 30 seconds. I had to decrease the page size to 25 to get it to work without timing out. |
The version I use is Jira v6.4.13 |
Did you resolve it? |
Jira version: 7.2.0
I'm getting the followin exception after running the collector on Jira:
Can anybody tell me what may be the issue here? The communication with Mongo is working fine and I believe I configured correctly the properties file. Will appreciate any help.
Thanks,
Leo
The text was updated successfully, but these errors were encountered: