History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3258
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: Steve Luo
Reporter: Alexey Shumkin
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Build details cannot be shown because of "Unexpected error" when GitLab server is unreachable

Created: 16/Sep/18 08:37 PM   Updated: 16/Sep/18 10:56 PM
Component/s: None
Affects Version/s: 8.0.14
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment:
Operating System Linux 4.4.0-134-generic, amd64
JVM OpenJDK 64-Bit Server VM 1.7.0_111, Oracle Corporation
QuickBuild Version 8.0.14 - Mon Jul 30 09:20:03 UTC 2018


 Description  « Hide
The "Whoops! An unexpected exception occurred." error is shown when I try to see the latest build.

Error Details:

Message: Exception in rendering component: [Component id = comment]

Root cause:

java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:196)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at sun.security.ssl.InputRecord.readFully(InputRecord.java:442)
at sun.security.ssl.InputRecord.read(InputRecord.java:480)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:944)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1342)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1369)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1353)
at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1341)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
at org.gitlab.api.http.GitlabHTTPRequestor.parse(GitlabHTTPRequestor.java:387)
at org.gitlab.api.http.GitlabHTTPRequestor.to(GitlabHTTPRequestor.java:168)
at org.gitlab.api.http.GitlabHTTPRequestor.to(GitlabHTTPRequestor.java:139)
at org.gitlab.api.GitlabAPI.getProject(GitlabAPI.java:629)
at com.pmease.quickbuild.plugin.scm.gitlab.GitLabClient.getProject(GitLabClient.java:50)
at com.pmease.quickbuild.plugin.scm.gitlab.issue.GitLabSetting.getProjectPath(GitLabSetting.java:117)
at com.pmease.quickbuild.plugin.scm.gitlab.issue.GitLabSetting$$EnhancerByCGLIB$$bf2c61ae.CGLIB$getProjectPath$6(<generated>)
at com.pmease.quickbuild.plugin.scm.gitlab.issue.GitLabSetting$$EnhancerByCGLIB$$bf2c61ae$$FastClassByCGLIB$$4638b18.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:215)
...

Steps:
1. Setup Issue tracker - GitLab server. Specify server URL with cannot be reached from Java (unsupported SSL/incorrect server URL,etc)
2. Try to open a build overview with any SCM changes. Error is shown, build details cannot be seen.

I guess, some placeholder with the error details must be shown on GitLab issues "page" but other build details must be reachable for overview


 All   Comments   Work Log   Change History      Sort Order:
Change by Robin Shen [16/Sep/18 10:56 PM]
Field Original Value New Value
Assignee Robin Shen [ robinshine ] Steve Luo [ steve ]