[jbosstools-issues] [JBoss JIRA] (JBIDE-25287) Jolokia Connection errors are swallowed

[Jeff MAURY (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-25287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff MAURY updated JBIDE-25287:
-------------------------------
    Fix Version/s: 4.6.x
                       (was: 4.5.x)


> 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.6.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=13468676&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13468676] 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)