January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25591) JBoss EAP 7.0 Server adapter fails to start with OpenJDK9

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25591?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25591: ------------------------------------- https://access.redhat.com/articles/2026253 If you scroll down to the EAP 7.0 section, you'll see that Java 9 is not a supported configuration. I will try to make sure that my tools do not allow you to choose Java 9 for EAP 7.0. Another link with more information: https://issues.jboss.org/browse/EAP7-431 Everything I can see indicates that EAP 7.0 is not really able to run under Java 9. Most of the work for Java 9 was done in WildFly, which maps to EAP 7.1. > JBoss EAP 7.0 Server adapter fails to start with OpenJDK9 > --------------------------------------------------------- > > Key: JBIDE-25591 > URL: https://issues.jboss.org/browse/JBIDE-25591 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.2.Final > Environment: Fedora 26 > java-9-openjdk-9.0.1.11-4.fc26.x86_64 > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.5.3.AM1 > > Attachments: .log, server.log > > > Starting of EAP 7.0 server adapter with defined Java Runtime Environment to JavaSE-9 ends up in state stopped and errors are produced. > See logs: > Server: [^server.log] > IDE: [^.log] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25591) JBoss EAP 7.0 Server adapter fails to start with OpenJDK9

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25591?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25591: -------------------------------- Fix Version/s: 4.5.3.AM1 (was: 4.5.2.Final) > JBoss EAP 7.0 Server adapter fails to start with OpenJDK9 > --------------------------------------------------------- > > Key: JBIDE-25591 > URL: https://issues.jboss.org/browse/JBIDE-25591 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.2.Final > Environment: Fedora 26 > java-9-openjdk-9.0.1.11-4.fc26.x86_64 > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.5.3.AM1 > > Attachments: .log, server.log > > > Starting of EAP 7.0 server adapter with defined Java Runtime Environment to JavaSE-9 ends up in state stopped and errors are produced. > See logs: > Server: [^server.log] > IDE: [^.log] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25591) JBoss EAP 7.0 Server adapter fails to start with OpenJDK9

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25591?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25591: -------------------------------- Fix Version/s: 4.5.2.Final (was: 4.5.x) > JBoss EAP 7.0 Server adapter fails to start with OpenJDK9 > --------------------------------------------------------- > > Key: JBIDE-25591 > URL: https://issues.jboss.org/browse/JBIDE-25591 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.2.Final > Environment: Fedora 26 > java-9-openjdk-9.0.1.11-4.fc26.x86_64 > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.5.2.Final > > Attachments: .log, server.log > > > Starting of EAP 7.0 server adapter with defined Java Runtime Environment to JavaSE-9 ends up in state stopped and errors are produced. > See logs: > Server: [^server.log] > IDE: [^.log] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25615) Update test cases for server in Polarion

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25615?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25615: ------------------------------------- [~jkopriva] Can you tell me what kind of tests are being run there? If the tests are extensive or not really accomplishing much, we can probably 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)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25587) Running EAP 7.1 server is not selected by default when deploying

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25587?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25587: -------------------------------- Fix Version/s: 4.6.0.AM1 > Running EAP 7.1 server is not selected by default when deploying > ---------------------------------------------------------------- > > Key: JBIDE-25587 > URL: https://issues.jboss.org/browse/JBIDE-25587 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.2.Final > Environment: FC27 > Red Hat JBoss Developer Studio > Version: 11.2.0.GA > Build id: GA-v20180115-0516-B1866 > Build date: 20180115-0516 > EAP 7.1 > Reporter: Josef Kopriva > Assignee: Rob Stryker > Fix For: 4.6.0.AM1 > > Attachments: JBIDE-25587.ogv, image-2018-01-16-13-42-38-197.png > > > Please make default selection on running server in *Run On Server* dialog. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24733) WTP reorganization

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24733?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24733: -------------------------------- Fix Version/s: 4.6.0.AM1 > WTP reorganization > ------------------ > > Key: JBIDE-24733 > URL: https://issues.jboss.org/browse/JBIDE-24733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.5.x > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.6.0.AM1 > > > Webtools (upstream project) is in sorry shape and needs a lot of things. First, it needs a proper build system, including jobs. To make this less painful, consolidating repositories is also encouraged. Making sure the monolith gets broken up into proper swimlanes is also a necessity. > Finally, once the plugins are properly organized and swim-laned, lots of attention will need to be paid to the features and tests. Right now most tests appear to be full product integration tests, no matter what repo they live in. > There's a lot of work to do. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25674: -------------------------------- Fix Version/s: 4.5.3.AM1 > 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 > Fix For: 4.5.3.AM1 > > > {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)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25617) Add skip registration flag in CDK server adapter

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25617?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25617: -------------------------------- Fix Version/s: 4.5.3.AM1 > Add skip registration flag in CDK server adapter > ------------------------------------------------- > > Key: JBIDE-25617 > URL: https://issues.jboss.org/browse/JBIDE-25617 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, server > Affects Versions: 4.5.2.Final > Reporter: Josef Kopriva > Assignee: Rob Stryker > Fix For: 4.5.3.AM1 > > > User should be given possibility to skip registration (flag --skip-registration). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25674: ------------------------------------- Would you be able to list full steps? CDK version, environment, etc? > 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 > > {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)

7 years, 9 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25674: ------------------------------------- [~aurelien.pupier] I've updated my patch a bit with your new added information, however, I *still* feel like I don't have enough information to submit a proper bug report upstream. What we know is there is a HttpResponse, and the jolokia libraries are trying to parse the stream into JSON. The parse fails, and so it resorts to the status line instead, and throws an exception that doesn't have a JSONObject pJsonRespObject (because the parse failed, so no such object exists). However, we still don't know what was in the actual stream. What we can assume is that the stream wasn't valid JSON, but we still have no idea what the stream contained. This is a critical bit of information before we open a bug report upstream. We need to know what the actual response is. To actually get at what request was made, we'd need to set a breakpoint in J4pRequestHandler and exactly what type of org.apache.http.* request they're making, then make an identical request in a Main class of our own, and read the stream. Alternatively, we could come up with a curl request or something similar. Unfortunately I can't replicate your usecase, so I'm not quite sure what to do here. It'd be very helpful if we could determine what exactly is in the stream. I'll look to see if eventually I can make a main class that does a similar request. > 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 > > {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)

7 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2018