[JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ]
Aurélien Pupier edited comment on JBIDE-25674 at 2/1/18 5:27 AM:
-----------------------------------------------------------------
the request used is
{quote}POST https://camel-ose-springboot-xml-fis-simple-without-devtool.192.168.1.14.... HTTP/1.1{quote}
I would have expected a header with the bearer token !image-2018-02-01-10-43-00-504.png|thumbnail!
The response is:
HttpResponseProxy{HTTP/1.1 503 Service Unavailable [Cache-Control: no-store, Date: Wed, 31 Jan 2018 13:02:44 GMT, Content-Length: 92, Content-Type: text/plain; charset=utf-8, Connection: close] ResponseEntityProxy{[Content-Type: text/plain; charset=utf-8,Content-Length: 92,Chunked: false]}}
The parse exception is:
{noformat}
Unexpected character (E) at position 0.
at org.json.simple.parser.Yylex.yylex(Yylex.java:610)
at org.json.simple.parser.JSONParser.nextToken(JSONParser.java:269)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:118)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:92)
at org.jolokia.client.request.J4pRequestHandler.extractJsonResponse(J4pRequestHandler.java:160)
at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:270)
at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
at org.jolokia.client.J4pClient.execute(J4pClient.java:150)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
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}
The error provided (503) seems to be due to the return of this bug [OSFUSE-554] and reported on this new Fuse version here [OSFUSE-700]
was (Author: aurelien.pupier):
the request used is
{quote}POST https://camel-ose-springboot-xml-fis-simple-without-devtool.192.168.1.14.... HTTP/1.1{quote}
I would have expected a header with the bearer token !image-2018-02-01-10-43-00-504.png|thumbnail!
The response is:
HttpResponseProxy{HTTP/1.1 503 Service Unavailable [Cache-Control: no-store, Date: Wed, 31 Jan 2018 13:02:44 GMT, Content-Length: 92, Content-Type: text/plain; charset=utf-8, Connection: close] ResponseEntityProxy{[Content-Type: text/plain; charset=utf-8,Content-Length: 92,Chunked: false]}}
The parse exception is:
{noformat}
Unexpected character (E) at position 0.
at org.json.simple.parser.Yylex.yylex(Yylex.java:610)
at org.json.simple.parser.JSONParser.nextToken(JSONParser.java:269)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:118)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:92)
at org.jolokia.client.request.J4pRequestHandler.extractJsonResponse(J4pRequestHandler.java:160)
at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:270)
at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
at org.jolokia.client.J4pClient.execute(J4pClient.java:150)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
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}
The error provided (503) seems to be due to the return of this bug [OSFUSE-554]
> NPE in JolokiaConnectionWrapper.extractStatus
> ---------------------------------------------
>
> Key: JBIDE-25674
> URL: https://issues.jboss.org/browse/JBIDE-25674
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM2
>
> Attachments: image-2018-02-01-10-43-00-504.png
>
>
> {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)
8 years, 1 month
[JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ]
Aurélien Pupier edited comment on JBIDE-25674 at 2/1/18 5:10 AM:
-----------------------------------------------------------------
the request used is
{quote}POST https://camel-ose-springboot-xml-fis-simple-without-devtool.192.168.1.14.... HTTP/1.1{quote}
I would have expected a header with the bearer token !image-2018-02-01-10-43-00-504.png|thumbnail!
The response is:
HttpResponseProxy{HTTP/1.1 503 Service Unavailable [Cache-Control: no-store, Date: Wed, 31 Jan 2018 13:02:44 GMT, Content-Length: 92, Content-Type: text/plain; charset=utf-8, Connection: close] ResponseEntityProxy{[Content-Type: text/plain; charset=utf-8,Content-Length: 92,Chunked: false]}}
The parse exception is:
{noformat}
Unexpected character (E) at position 0.
at org.json.simple.parser.Yylex.yylex(Yylex.java:610)
at org.json.simple.parser.JSONParser.nextToken(JSONParser.java:269)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:118)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:92)
at org.jolokia.client.request.J4pRequestHandler.extractJsonResponse(J4pRequestHandler.java:160)
at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:270)
at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
at org.jolokia.client.J4pClient.execute(J4pClient.java:150)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
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}
The error provided (503) seems to be due to the return of this bug [OSFUSE-554]
was (Author: aurelien.pupier):
the request used is
{quote}POST https://camel-ose-springboot-xml-fis-simple-without-devtool.192.168.1.14.... HTTP/1.1{quote}
I would have expected a header with the bearer token !image-2018-02-01-10-43-00-504.png|thumbnail!
The response is:
HttpResponseProxy{HTTP/1.1 503 Service Unavailable [Cache-Control: no-store, Date: Wed, 31 Jan 2018 13:02:44 GMT, Content-Length: 92, Content-Type: text/plain; charset=utf-8, Connection: close] ResponseEntityProxy{[Content-Type: text/plain; charset=utf-8,Content-Length: 92,Chunked: false]}}
The parse exception is:
{noformat}
Unexpected character (E) at position 0.
at org.json.simple.parser.Yylex.yylex(Yylex.java:610)
at org.json.simple.parser.JSONParser.nextToken(JSONParser.java:269)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:118)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:92)
at org.jolokia.client.request.J4pRequestHandler.extractJsonResponse(J4pRequestHandler.java:160)
at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:270)
at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
at org.jolokia.client.J4pClient.execute(J4pClient.java:150)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
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}
> NPE in JolokiaConnectionWrapper.extractStatus
> ---------------------------------------------
>
> Key: JBIDE-25674
> URL: https://issues.jboss.org/browse/JBIDE-25674
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM2
>
> Attachments: image-2018-02-01-10-43-00-504.png
>
>
> {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)
8 years, 1 month
[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-24897:
------------------------------------
FTR the errors on IE/Win10: !IE-screenshot.png!
> add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24897
> URL: https://issues.jboss.org/browse/JBIDE-24897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: fabric8
> Affects Versions: 4.5.2.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM1
>
> Attachments: IE-screenshot.png, fab8anal-in-ds-central.png, fab8anal-in-jbt-central-installed.png, fab8anal-in-jbt-central.png, fabric8-connector.png, stack analysis.mp4, stack report 20180119.png
>
>
> Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra]
> Assuming we also want to create a Central connector to advertise this optional feature.
> In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala]
> Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin
> Affected:
> * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml)
> * https://github.com/jbosstools/jbosstools-build-sites (category.xml)
> * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24897:
-------------------------------
Attachment: IE-screenshot.png
> add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24897
> URL: https://issues.jboss.org/browse/JBIDE-24897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: fabric8
> Affects Versions: 4.5.2.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM1
>
> Attachments: IE-screenshot.png, fab8anal-in-ds-central.png, fab8anal-in-jbt-central-installed.png, fab8anal-in-jbt-central.png, fabric8-connector.png, stack analysis.mp4, stack report 20180119.png
>
>
> Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra]
> Assuming we also want to create a Central connector to advertise this optional feature.
> In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala]
> Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin
> Affected:
> * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml)
> * https://github.com/jbosstools/jbosstools-build-sites (category.xml)
> * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ]
Aurélien Pupier edited comment on JBIDE-25674 at 2/1/18 4:43 AM:
-----------------------------------------------------------------
the request used is
{quote}POST https://camel-ose-springboot-xml-fis-simple-without-devtool.192.168.1.14.... HTTP/1.1{quote}
I would have expected a header with the bearer token !image-2018-02-01-10-43-00-504.png|thumbnail!
The response is:
HttpResponseProxy{HTTP/1.1 503 Service Unavailable [Cache-Control: no-store, Date: Wed, 31 Jan 2018 13:02:44 GMT, Content-Length: 92, Content-Type: text/plain; charset=utf-8, Connection: close] ResponseEntityProxy{[Content-Type: text/plain; charset=utf-8,Content-Length: 92,Chunked: false]}}
The parse exception is:
{noformat}
Unexpected character (E) at position 0.
at org.json.simple.parser.Yylex.yylex(Yylex.java:610)
at org.json.simple.parser.JSONParser.nextToken(JSONParser.java:269)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:118)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:92)
at org.jolokia.client.request.J4pRequestHandler.extractJsonResponse(J4pRequestHandler.java:160)
at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:270)
at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
at org.jolokia.client.J4pClient.execute(J4pClient.java:150)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
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}
was (Author: aurelien.pupier):
the request used is POST https://camel-ose-springboot-xml-fis-simple-without-devtool.192.168.1.14.... HTTP/1.1
The response is:
HttpResponseProxy{HTTP/1.1 503 Service Unavailable [Cache-Control: no-store, Date: Wed, 31 Jan 2018 13:02:44 GMT, Content-Length: 92, Content-Type: text/plain; charset=utf-8, Connection: close] ResponseEntityProxy{[Content-Type: text/plain; charset=utf-8,Content-Length: 92,Chunked: false]}}
The parse exception is:
{noformat}
Unexpected character (E) at position 0.
at org.json.simple.parser.Yylex.yylex(Yylex.java:610)
at org.json.simple.parser.JSONParser.nextToken(JSONParser.java:269)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:118)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:92)
at org.jolokia.client.request.J4pRequestHandler.extractJsonResponse(J4pRequestHandler.java:160)
at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:270)
at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
at org.jolokia.client.J4pClient.execute(J4pClient.java:150)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
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}
> NPE in JolokiaConnectionWrapper.extractStatus
> ---------------------------------------------
>
> Key: JBIDE-25674
> URL: https://issues.jboss.org/browse/JBIDE-25674
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM2
>
> Attachments: image-2018-02-01-10-43-00-504.png
>
>
> {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)
8 years, 1 month
[JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-25674:
-----------------------------------------
the request used is POST https://camel-ose-springboot-xml-fis-simple-without-devtool.192.168.1.14.... HTTP/1.1
The response is:
HttpResponseProxy{HTTP/1.1 503 Service Unavailable [Cache-Control: no-store, Date: Wed, 31 Jan 2018 13:02:44 GMT, Content-Length: 92, Content-Type: text/plain; charset=utf-8, Connection: close] ResponseEntityProxy{[Content-Type: text/plain; charset=utf-8,Content-Length: 92,Chunked: false]}}
The parse exception is:
{noformat}
Unexpected character (E) at position 0.
at org.json.simple.parser.Yylex.yylex(Yylex.java:610)
at org.json.simple.parser.JSONParser.nextToken(JSONParser.java:269)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:118)
at org.json.simple.parser.JSONParser.parse(JSONParser.java:92)
at org.jolokia.client.request.J4pRequestHandler.extractJsonResponse(J4pRequestHandler.java:160)
at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:270)
at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
at org.jolokia.client.J4pClient.execute(J4pClient.java:150)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
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}
> NPE in JolokiaConnectionWrapper.extractStatus
> ---------------------------------------------
>
> Key: JBIDE-25674
> URL: https://issues.jboss.org/browse/JBIDE-25674
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM2
>
>
> {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)
8 years, 1 month
[JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ]
Aurélien Pupier edited comment on JBIDE-25674 at 2/1/18 4:27 AM:
-----------------------------------------------------------------
I reproduced with open.paas.redhat.com and CDK 3.3.0-1.
I'm on Windows 10.
Red Hat JBoss Developer Studio
Version: 11.2.0.GA
Build id: GA-v20180122-2025-B1884
Build date: 20180122-2025
- start Fuse Tooling 10.2.0 (Dev Studio 11.2.0)
- start the CDK (or whatever OpenShift instance on which you want to deploy to)
- create a namespace "test-fis" for instance
- create a Fuse Integration project OpenShift-based (video here)
-- File --> new -->Fuse Integration Project
-- provide a name and then click next
-- use 2.20.1 for Camel Version (enter it manually), click Next
-- Use a predefined template
-- Fuse on OpenShift -> SpringBoot on OpenShift then click Finish
- add SpringBoot dev dependencies as explained here in step 1 and 2 https://github.com/fabric8io-images/s2i/blob/master/java/images/jboss/REA... (the step 3 is done automatically by Eclipse OpenShift Tooling)
- right-click on project Run as...
- select the maven build named "Deploy <projectName> on OpenShift
-- go to JRE tab
-- change VM arguments:
--- provide correct kubernetes.master URL
--- provide namespace to the value you gave, "test-fis" if followed what i suggested
--- (Until Fuse Tech Preview 3 is available publicly) change fabric8.generator.from value from registry.access.redhat.com/jboss-fuse-7/fuse-java-openshift to fabric8/s2i-java
- Start the launch configuration
you can check when it has finished to deploy in the pod log that a message is written every seconds
- in OpenShift explorer view, right-click to the deployed app and choose "Server adapter..."
- select the project that you created and click finish
- (due to https://issues.jboss.org/browse/JBIDE-25288 you might need to delete the server adapter and recreate it)
- double-click on JMX node of the OpenShift Server Adapter created (in JMX view or Servers view, reproduce on both)
was (Author: aurelien.pupier):
I reproduced with open.paas.redhat.com and CDK 3.3.0-1.
I'm on Windows 10.
Red Hat JBoss Developer Studio
Version: 11.2.0.GA
Build id: GA-v20180122-2025-B1884
Build date: 20180122-2025
- start Fuse Tooling 10.2.0 (Dev Studio 11.2.0)
- start the CDK (or whatever OpenShift instance on which you want to deploy to)
- create a namespace "test-fis" for instance
- create a Fuse Integration project OpenShift-based (video here)
-- File --> new -->Fuse Integration Project
-- provide a name and then click next
-- use 2.20.1 for Camel Version, click Next
-- Use a predefined template
-- Fuse on OpenShift -> SpringBoot on OpenShift then click Finish
- add SpringBoot dev dependencies as explained here in step 1 and 2 https://github.com/fabric8io-images/s2i/blob/master/java/images/jboss/REA... (the step 3 is done automatically by Eclipse OpenShift Tooling)
- right-click on project Run as...
- select the maven build named "Deploy <projectName> on OpenShift
-- go to JRE tab
-- change VM arguments:
--- provide correct kubernetes.master URL
--- provide namespace to the value you gave, "test-fis" if followed what i suggested
--- (Until Fuse Tech Preview 3 is available publicly) change fabric8.generator.from value from registry.access.redhat.com/jboss-fuse-7/fuse-java-openshift to fabric8/s2i-java
- Start the launch configuration
you can check when it has finished to deploy in the pod log that a message is written every seconds
- in OpenShift explorer view, right-click to the deployed app and choose "Server adapter..."
- select the project that you created and click finish
- (due to https://issues.jboss.org/browse/JBIDE-25288 you might need to delete the server adapter and recreate it)
- double-click on JMX node of the OpenShift Server Adapter created (in JMX view or Servers view, reproduce on both)
> NPE in JolokiaConnectionWrapper.extractStatus
> ---------------------------------------------
>
> Key: JBIDE-25674
> URL: https://issues.jboss.org/browse/JBIDE-25674
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM2
>
>
> {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)
8 years, 1 month
[JBoss JIRA] (JBIDE-25615) Update test cases for server in Polarion
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25615?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-25615:
---------------------------------------
[~rob.stryker] as far as I know we are testing: start, restart, stop, downloading runtimes in devstudio, deploy project on server and check if it is running. I agree with you on stop testing anything before Wildfly 8 or EAP 6.
> Update test cases for server in Polarion
> ----------------------------------------
>
> Key: JBIDE-25615
> URL: https://issues.jboss.org/browse/JBIDE-25615
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, server
> Affects Versions: 4.5.2.Final
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
>
> Add latest EAP and WildFly, remove servers with expired support.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month