[jbosstools-issues] [JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection

Aurélien Pupier (JIRA) issues at jboss.org
Fri May 5 07:20:01 EDT 2017


    [ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402552#comment-13402552 ] 

Aurélien Pupier commented on JBIDE-23869:
-----------------------------------------

{quote}Don't think we can do more as the request is rejected by OpenShift for authentication reason. You need to setup your OpenShift credentials on the JMX connection (HTTP header){quote}

Do you mean that the OpenShift server is providing the "Invalid status type java.lang.String('Failure') recevived".
I'm very sceptical on that.
With this error the user has no idea that it is due to some authentication issue, so 2 possibilities:
- OpenShift server is providing a bad response --> this need to be improved on OpenShift server side
- the OpenShift server response is ate by Jolokia or JBoss Tools --> this need to be fixed in Jolokia or JBoss Tools

> ClassCastException with Jolokia connection
> ------------------------------------------
>
>                 Key: JBIDE-23869
>                 URL: https://issues.jboss.org/browse/JBIDE-23869
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jmx, openshift
>            Reporter: Aurélien Pupier
>            Assignee: Jeff MAURY
>              Labels: jmx, jolokia, openshift
>             Fix For: 4.4.4.Final
>
>         Attachments: failure.png, image-2017-02-06-13-54-27-708.png
>
>
>  !image-2017-02-06-13-54-27-708.png|thumbnail! 
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> 	at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> 	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:315)
> 	at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> 	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:55)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)



More information about the jbosstools-issues mailing list