[jbosstools-issues] [JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus

[Aurélien Pupier (JIRA)]

Aurélien Pupier created JBIDE-25674:
---------------------------------------

             Summary: NPE in JolokiaConnectionWrapper.extractStatus
                 Key: JBIDE-25674
                 URL: https://issues.jboss.org/browse/JBIDE-25674
             Project: Tools (JBoss Tools)
          Issue Type: Bug
            Reporter: Aurélien Pupier


{noformat}
!ENTRY org.eclipse.core.jobs 4 2 2018-01-29 15:56:34.020
!MESSAGE An internal error occurred during: "Connect Job".
!STACK 0
java.lang.NullPointerException
	at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.extractStatus(JolokiaConnectionWrapper.java:340)
	at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
	at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
	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)
{noformat}

I put a breakpoint in org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable() to see which exception it was and it is a "503 Service Unavailable"
in this case the "response" is null

2 possibilities:
- it is normal that it is null in this case Jboss Tools need to handle this case
- it is not normal that it is null and in this case, it needs to be reported upstream (even if a null check might nice as a workaround for now)



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)