[JBoss JIRA] (JBIDE-25287) Jolokia Connection errors are swallowed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25287?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-25287:
----------------------------------------
Assignee: Rob Stryker
> Jolokia Connection errors are swallowed
> ---------------------------------------
>
> Key: JBIDE-25287
> URL: https://issues.jboss.org/browse/JBIDE-25287
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Affects Versions: 4.5.0.Final, 4.5.1.AM3
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Labels: jmx, jolokia, openshift
> Fix For: 4.5.x
>
> Attachments: image-2017-10-24-13-30-30-715.png
>
>
> even if it is better than before as we don't have a ClassCastException (see [JBIDE-23869]), as mentioned in [my last comment|https://issues.jboss.org/browse/JBIDE-23869?focusedCommentId=1346...] the error reported by Jolokia when deployed on OpenShift is still swallowed.
> I have another use case for which I have:
> !image-2017-10-24-13-30-30-715.png|thumbnail!
> with stack in log
> {noformat}
> !ENTRY org.jboss.tools.jmx.core 4 0 2017-10-24 13:27:33.523
> !MESSAGE An error occurred while opening the connection.
> !STACK 0
> java.io.IOException: Remote error status=404 (Invalid status of type java.lang.String('Failure') received)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:326)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:115)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.jolokia.client.exception.J4pRemoteException: Invalid status of type java.lang.String('Failure') received
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:67)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:313)
> ... 4 more
> {noformat}
> although when using a Rest client i have this error which contains far more information:
> {noformat}
> {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "pods "camel-ose-springboot-xml-3-t99hx" not found",
> "reason": "NotFound",
> "details": {
> "name": "camel-ose-springboot-xml-3-t99hx",
> "kind": "pods"
> },
> "code": 404
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBIDE-25287) Jolokia Connection errors are swallowed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25287?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25287:
------------------------------------------
[~rob.stryker] dare to look into this please?
> Jolokia Connection errors are swallowed
> ---------------------------------------
>
> Key: JBIDE-25287
> URL: https://issues.jboss.org/browse/JBIDE-25287
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Affects Versions: 4.5.0.Final, 4.5.1.AM3
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Labels: jmx, jolokia, openshift
> Fix For: 4.5.x
>
> Attachments: image-2017-10-24-13-30-30-715.png
>
>
> even if it is better than before as we don't have a ClassCastException (see [JBIDE-23869]), as mentioned in [my last comment|https://issues.jboss.org/browse/JBIDE-23869?focusedCommentId=1346...] the error reported by Jolokia when deployed on OpenShift is still swallowed.
> I have another use case for which I have:
> !image-2017-10-24-13-30-30-715.png|thumbnail!
> with stack in log
> {noformat}
> !ENTRY org.jboss.tools.jmx.core 4 0 2017-10-24 13:27:33.523
> !MESSAGE An error occurred while opening the connection.
> !STACK 0
> java.io.IOException: Remote error status=404 (Invalid status of type java.lang.String('Failure') received)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:326)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:115)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.jolokia.client.exception.J4pRemoteException: Invalid status of type java.lang.String('Failure') received
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:67)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:313)
> ... 4 more
> {noformat}
> although when using a Rest client i have this error which contains far more information:
> {noformat}
> {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "pods "camel-ose-springboot-xml-3-t99hx" not found",
> "reason": "NotFound",
> "details": {
> "name": "camel-ose-springboot-xml-3-t99hx",
> "kind": "pods"
> },
> "code": 404
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBIDE-25166) Resource wizard: using invalid URL does not show error message
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25166?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25166:
-------------------------------------
Attachment: (was: invalid-url-error-present.png)
> Resource wizard: using invalid URL does not show error message
> --------------------------------------------------------------
>
> Key: JBIDE-25166
> URL: https://issues.jboss.org/browse/JBIDE-25166
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Josef Kopriva
> Labels: openshift_v3, resource_wizard
> Fix For: 4.5.x
>
> Attachments: image-2017-10-27-15-12-22-841.png, valid-url-no-errors.png
>
>
> Steps to reproduce:
> 1. Have project in OpenShift connection in OpenShift Explorer
> 2. Right click on project -> New -> Resource...
> 3. Enter invalid URL -> no error is shown, Finish button is enabled
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBIDE-25166) Resource wizard: using invalid URL does not show error message
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25166?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25166 at 10/27/17 9:12 AM:
--------------------------------------------------------------------
[~jkopriva] can you explain what you're missing here? I can enter an invalid url which has an error decoration on the field, an error in the title area and "Finish" disabled.
!image-2017-10-27-15-12-22-841.png!
Once I correct the error the decoration and message in the title disappear, the "Finish" gets enabled:
!valid-url-no-errors.png!
was (Author: adietish):
[~jkopriva] can you explain what you're missing here? I can enter an invalid url which has an error decoration on the field, an error in the title area and "Finish" disabled.
!invalid-url-error-present.png!
Once I correct the error the decoration and message in the title disappear, the "Finish" gets enabled:
!valid-url-no-errors.png!
> Resource wizard: using invalid URL does not show error message
> --------------------------------------------------------------
>
> Key: JBIDE-25166
> URL: https://issues.jboss.org/browse/JBIDE-25166
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Josef Kopriva
> Labels: openshift_v3, resource_wizard
> Fix For: 4.5.x
>
> Attachments: image-2017-10-27-15-12-22-841.png, valid-url-no-errors.png
>
>
> Steps to reproduce:
> 1. Have project in OpenShift connection in OpenShift Explorer
> 2. Right click on project -> New -> Resource...
> 3. Enter invalid URL -> no error is shown, Finish button is enabled
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBIDE-25166) Resource wizard: using invalid URL does not show error message
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25166?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25166:
-------------------------------------
Attachment: invalid-url-error-present.png
> Resource wizard: using invalid URL does not show error message
> --------------------------------------------------------------
>
> Key: JBIDE-25166
> URL: https://issues.jboss.org/browse/JBIDE-25166
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Josef Kopriva
> Labels: openshift_v3, resource_wizard
> Fix For: 4.5.x
>
> Attachments: invalid-url-error-present.png, valid-url-no-errors.png
>
>
> Steps to reproduce:
> 1. Have project in OpenShift connection in OpenShift Explorer
> 2. Right click on project -> New -> Resource...
> 3. Enter invalid URL -> no error is shown, Finish button is enabled
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBIDE-25166) Resource wizard: using invalid URL does not show error message
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25166?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25166:
------------------------------------------
[~jkopriva] can you explain what you're missing here? I can enter an invalid url which has an error decoration on the field, an error in the title area and "Finish" disabled.
!invalid-url-error-present.png!
Once I correct the error the decoration and message in the title disappear, the "Finish" gets enabled:
!valid-url-no-errors.png!
> Resource wizard: using invalid URL does not show error message
> --------------------------------------------------------------
>
> Key: JBIDE-25166
> URL: https://issues.jboss.org/browse/JBIDE-25166
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Josef Kopriva
> Labels: openshift_v3, resource_wizard
> Fix For: 4.5.x
>
> Attachments: invalid-url-error-present.png, valid-url-no-errors.png
>
>
> Steps to reproduce:
> 1. Have project in OpenShift connection in OpenShift Explorer
> 2. Right click on project -> New -> Resource...
> 3. Enter invalid URL -> no error is shown, Finish button is enabled
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24868 at 10/27/17 8:53 AM:
--------------------------------------------------------------------
What seems very likely the cause for node is the livenessProbe that's set to 30secs:
{code}
"livenessProbe" : {
"httpGet" : {
"path" : "/pagecount",
"port" : 8080,
"scheme" : "HTTP"
},
"initialDelaySeconds" : 30,
"timeoutSeconds" : 3,
"periodSeconds" : 10,
"successThreshold" : 1,
"failureThreshold" : 3
},
{code}
They are present for the dc in the template: https://github.com/openshift/nodejs-ex/blob/master/openshift/templates/no...
So if we add a timeout to the route we also need to disable or increase the timeout for the livenessProbe.
The docs for *livenessProbe*, *readynessProbe* etc. in Kube are at https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene...
was (Author: adietish):
What seems very likely the cause for node is the livenessProbe that's set to 30secs:
{code}
"livenessProbe" : {
"httpGet" : {
"path" : "/pagecount",
"port" : 8080,
"scheme" : "HTTP"
},
"initialDelaySeconds" : 30,
"timeoutSeconds" : 3,
"periodSeconds" : 10,
"successThreshold" : 1,
"failureThreshold" : 3
},
{code}
They are present for the dc in the template: https://github.com/openshift/nodejs-ex/blob/master/openshift/templates/no...
So if we add a timeout to the route we also need to disable or increase the timeout for the livenessProbe.
> Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24868
> URL: https://issues.jboss.org/browse/JBIDE-24868
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.0.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.1.Final
>
> Attachments: application-is-not-available.png, breakpoint-suspend-thread.png, webui_edit-add-service.png
>
>
> it will avoid to have "debug connections always killed after 30s staying in a breakpoint"
> see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion
> k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24868:
------------------------------------------
What seems very likely the cause for node is the livenessProbe that's set to 30secs:
{code}
"livenessProbe" : {
"httpGet" : {
"path" : "/pagecount",
"port" : 8080,
"scheme" : "HTTP"
},
"initialDelaySeconds" : 30,
"timeoutSeconds" : 3,
"periodSeconds" : 10,
"successThreshold" : 1,
"failureThreshold" : 3
},
{code}
They are present for the dc in the template: https://github.com/openshift/nodejs-ex/blob/master/openshift/templates/no...
So if we add a timeout to the route we also need to disable or increase the timeout for the livenessProbe.
> Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24868
> URL: https://issues.jboss.org/browse/JBIDE-24868
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.0.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.1.Final
>
> Attachments: application-is-not-available.png, breakpoint-suspend-thread.png, webui_edit-add-service.png
>
>
> it will avoid to have "debug connections always killed after 30s staying in a breakpoint"
> see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion
> k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBIDE-25166) Resource wizard: using invalid URL does not show error message
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25166?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25166:
-------------------------------------
Summary: Resource wizard: using invalid URL does not show error message (was: Create Resource from URL does not show error message when URL is invalid)
> Resource wizard: using invalid URL does not show error message
> --------------------------------------------------------------
>
> Key: JBIDE-25166
> URL: https://issues.jboss.org/browse/JBIDE-25166
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Josef Kopriva
> Labels: openshift_v3, resource_wizard
> Fix For: 4.5.x
>
>
> Steps to reproduce:
> 1. Have project in OpenShift connection in OpenShift Explorer
> 2. Right click on project -> New -> Resource...
> 3. Enter invalid URL -> no error is shown, Finish button is enabled
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months