[JIRA] (JENKINS-58182) azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs
Title: Message Title Istvan Szekeres commented on JENKINS-58182 Re: azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs Thanks for fixing this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200233.1561454364000.2511.1564384260166%40Atlassian.JIRA.
[JIRA] (JENKINS-58182) azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-58182 azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs Change By: Jie Shen Status: Open Resolved Resolution: Fixed Released As: 1.0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200233.1561454364000.2486.1564370640286%40Atlassian.JIRA.
[JIRA] (JENKINS-58182) azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-58182 azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200233.1561454364000.8978.1561513560317%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58182) azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs
Title: Message Title Jie Shen commented on JENKINS-58182 Re: azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs I will look into it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200233.1561454364000.8980.1561513560347%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58182) azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs
Title: Message Title Istvan Szekeres created an issue Jenkins / JENKINS-58182 azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs Issue Type: Bug Assignee: Azure DevOps Components: azure-commons-plugin Created: 2019-06-25 09:19 Priority: Minor Reporter: Istvan Szekeres Due to firewall (mis)configuration dc.services.visualstudio.com became partially accessible - the TCP connection to it succeeded but no data could be sent. As a result of this Jenkins instances using the azure-commons plugin were unable to start as on startup the plugin was trying to send data but it couldn't so it got blocked, and this completely blocked Jenkins itself as well (at the "Jenkins is starting" phase). It could be nice if it tried to access dc.services either asynchronously or timing out after a few seconds. Also it could possibly write something meaningful into the logs because finding the evidence in the Java thread dump is not the easiest. The thread dump obtained while Jenkins was blocked during startup: "AppInsightsPluginLoadListener.onPluginsLoaded" #29 daemon prio=5 os_prio=0 tid=0x7fea7cfa9000 nid=0x15636 runnable [0x7fea29688000] java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:171) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) - locked <0x86c82868> (a java.lang.Object) at sun.security.ssl.SSLSocketImpl.performInitialH
