August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26284) Servers created from relative path can't start

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26284?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-26284. --------------------------------- Fix Version/s: 4.9.0.AM1 Resolution: Done https://github.com/redhat-developer/rsp-server/pull/11 Done > Servers created from relative path can't start > ---------------------------------------------- > > Key: JBIDE-26284 > URL: https://issues.jboss.org/browse/JBIDE-26284 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-server-protocol > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.9.0.AM1 > > > Servers created with their ''server.home.dir'' attribute set to a relative path will error on starting. > Example log from wildfly (and yes, that is the complete log): > {noformat}Error: Could not find or load main class org.jboss.modules.Main{noformat} > Relative paths either need to be resolved, or rejected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26284) Servers created from relative path can't start

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26284?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-26284: ------------------------------------- Hi: I've fixed the issue (yay!) by forbidding you from using relative paths (wat?!). But seriously, there is no reason for a client to to be able to ask a server to search with relative paths. The client has absolutely no way of knowing what folder the server is installed in, or what it's working directory is when it is started. One day in the future a use case may arrive in which runtimes are installed in a subdirectory of the RSP server, however, in those days, I would fully expect the server to handle those situations and not the client. So until a really good usecase is provided, we're blocking relative paths. > Servers created from relative path can't start > ---------------------------------------------- > > Key: JBIDE-26284 > URL: https://issues.jboss.org/browse/JBIDE-26284 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-server-protocol > Reporter: Jan Richter > Assignee: Rob Stryker > > Servers created with their ''server.home.dir'' attribute set to a relative path will error on starting. > Example log from wildfly (and yes, that is the complete log): > {noformat}Error: Could not find or load main class org.jboss.modules.Main{noformat} > Relative paths either need to be resolved, or rejected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26180: ------------------------------- Description: In order to start Eclipse 4.9-based builds, we need an updated target platform. For sprint 152 / AM1: simrel M1 For sprint 153 / AM2: simrel M2 For sprint 154 / AM3: simrel M3 For sprint 155 / GA: simrel RC2/GA Coming in the next update, some orbit changes: * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug) Also: * reddeer 2.3 * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180821-... was: In order to start Eclipse 4.9-based builds, we need an updated target platform. For sprint 152 / AM1: simrel M1 For sprint 153 / AM2: simrel M2 For sprint 154 / AM3: simrel M3 For sprint 155 / GA: simrel RC2/GA Coming in the next update, some orbit changes: * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug) Also: * reddeer 2.3 * m2e 1.9.1.something (ping Fred after M3 is done) > TP: create target platform based on Eclipse 4.9 (Simrel 2018-09) > ---------------------------------------------------------------- > > Key: JBIDE-26180 > URL: https://issues.jboss.org/browse/JBIDE-26180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.9.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final > > Attachments: am1-vs-am2.p2diff.txt > > > In order to start Eclipse 4.9-based builds, we need an updated target platform. > For sprint 152 / AM1: simrel M1 > For sprint 153 / AM2: simrel M2 > For sprint 154 / AM3: simrel M3 > For sprint 155 / GA: simrel RC2/GA > Coming in the next update, some orbit changes: > * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug) > Also: > * reddeer 2.3 > * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180821-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26254) Request parameters are not validated

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26254?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-26254. --------------------------------- Fix Version/s: 4.9.0.AM1 Resolution: Done https://github.com/redhat-developer/rsp-server/pull/8 pushed to master > Request parameters are not validated > ------------------------------------ > > Key: JBIDE-26254 > URL: https://issues.jboss.org/browse/JBIDE-26254 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-server-protocol > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.9.0.AM1 > > > When sending requests with parameters, one can simply send invalid objects as payload. The server does not respond then (because it is too busy throwing exceptions, I presume). > i.e. send: server/findServerBeans(null) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26285) stopServerAsync returns ok when stopping a stopped server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26285?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-26285. --------------------------------- Fix Version/s: 4.9.0.AM1 Resolution: Done Pushed via https://github.com/redhat-developer/rsp-server/pull/9 > stopServerAsync returns ok when stopping a stopped server > --------------------------------------------------------- > > Key: JBIDE-26285 > URL: https://issues.jboss.org/browse/JBIDE-26285 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-server-protocol > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.9.0.AM1 > > > Calling server/stopServerAsync on a server that is already stopped returns: > {noformat}{ severity: 0, pluginId: 'unknown', code: 0, message: 'ok' }{noformat} > There is no indication that the server wasn't actually stopped as a result of the request. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26292) Clean up dependencies on internal packages

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26292?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-26292. --------------------------------- Fix Version/s: 4.9.0.AM1 Resolution: Done Pushed in https://github.com/redhat-developer/rsp-server/pull/10 > Clean up dependencies on internal packages > ------------------------------------------ > > Key: JBIDE-26292 > URL: https://issues.jboss.org/browse/JBIDE-26292 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-server-protocol > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.9.0.AM1 > > > There are several "internal" packages being exported/imported across bundles - i.e. org.jboss.tools.ssp.eclipse.debug.internal.core is being used in like 4 different bundles. > Refactor the packages to the internal packages stay internal to their bundle. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26312) Windows 7 slaves stall for 7 hours while recording test results?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26312?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26312: ------------------------------- Fix Version/s: 4.9.0.Final > Windows 7 slaves stall for 7 hours while recording test results? > ---------------------------------------------------------------- > > Key: JBIDE-26312 > URL: https://issues.jboss.org/browse/JBIDE-26312 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM3 > Reporter: Nick Boldt > Assignee: Pavol Srna > Fix For: 4.9.0.Final > > > This has been happening for a while now. > {code} > 20:24:20 Archiving artifacts > 20:50:34 Recording test results > (nothing happens for like 7 hours) > 04:09:55 Agent went offline during the build > 04:09:55 ERROR: Connection was broken: java.nio.channels.ClosedChannelException > 04:09:55 at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) > 04:09:55 at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179) > 04:09:55 at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:721) > 04:09:55 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) > 04:09:55 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 04:09:55 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 04:09:55 at java.lang.Thread.run(Thread.java:748) > {code} > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... > Anyone have a clue why collecting junit results should take >7hrs on win7, but work fine on other OSes? > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26312) Windows 7 slaves stall for 7 hours while recording test results?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-26312: ---------------------------------- Summary: Windows 7 slaves stall for 7 hours while recording test results? Key: JBIDE-26312 URL: https://issues.jboss.org/browse/JBIDE-26312 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.9.0.AM3 Reporter: Nick Boldt This has been happening for a while now. {code} 20:24:20 Archiving artifacts 20:50:34 Recording test results (nothing happens for like 7 hours) 04:09:55 Agent went offline during the build 04:09:55 ERROR: Connection was broken: java.nio.channels.ClosedChannelException 04:09:55 at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) 04:09:55 at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179) 04:09:55 at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:721) 04:09:55 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) 04:09:55 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 04:09:55 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 04:09:55 at java.lang.Thread.run(Thread.java:748) {code} https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... Anyone have a clue why collecting junit results should take >7hrs on win7, but work fine on other OSes? https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26312) Windows 7 slaves stall for 7 hours while recording test results?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26312?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26312: ---------------------------------- Assignee: Pavol Srna > Windows 7 slaves stall for 7 hours while recording test results? > ---------------------------------------------------------------- > > Key: JBIDE-26312 > URL: https://issues.jboss.org/browse/JBIDE-26312 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM3 > Reporter: Nick Boldt > Assignee: Pavol Srna > > This has been happening for a while now. > {code} > 20:24:20 Archiving artifacts > 20:50:34 Recording test results > (nothing happens for like 7 hours) > 04:09:55 Agent went offline during the build > 04:09:55 ERROR: Connection was broken: java.nio.channels.ClosedChannelException > 04:09:55 at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) > 04:09:55 at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179) > 04:09:55 at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:721) > 04:09:55 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) > 04:09:55 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 04:09:55 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 04:09:55 at java.lang.Thread.run(Thread.java:748) > {code} > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... > Anyone have a clue why collecting junit results should take >7hrs on win7, but work fine on other OSes? > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26180: ------------------------------- Description: In order to start Eclipse 4.9-based builds, we need an updated target platform. For sprint 152 / AM1: simrel M1 For sprint 153 / AM2: simrel M2 For sprint 154 / AM3: simrel M3 For sprint 155 / GA: simrel RC2/GA Coming in the next update, some orbit changes: * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug) Also: * reddeer 2.3 * m2e 1.9.1.something (ping Fred after M3 is done) was: In order to start Eclipse 4.9-based builds, we need an updated target platform. For sprint 152 / AM1: simrel M1 For sprint 153 / AM2: simrel M2 For sprint 154 / AM3: simrel M3 For sprint 155 / GA: simrel RC2/GA > TP: create target platform based on Eclipse 4.9 (Simrel 2018-09) > ---------------------------------------------------------------- > > Key: JBIDE-26180 > URL: https://issues.jboss.org/browse/JBIDE-26180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.9.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final > > Attachments: am1-vs-am2.p2diff.txt > > > In order to start Eclipse 4.9-based builds, we need an updated target platform. > For sprint 152 / AM1: simrel M1 > For sprint 153 / AM2: simrel M2 > For sprint 154 / AM3: simrel M3 > For sprint 155 / GA: simrel RC2/GA > Coming in the next update, some orbit changes: > * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug) > Also: > * reddeer 2.3 > * m2e 1.9.1.something (ping Fred after M3 is done) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2018