December 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-25992) FileNotFoundException: org.jboss.tools.as.itests.CreateServerCheckDefaultsTestorg.jboss.ide.eclipse.as.wildfly.80/xpaths.xml (No such file or directory)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-25992?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25992: ------------------------------- Fix Version/s: 4.11.0.AM1 > FileNotFoundException: org.jboss.tools.as.itests.CreateServerCheckDefaultsTestorg.jboss.ide.eclipse.as.wildfly.80/xpaths.xml (No such file or directory) > -------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25992 > URL: https://issues.jboss.org/browse/JBIDE-25992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, server > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Major > Fix For: 4.11.0.AM1 > > > Server.it.weekly jobs are failing because of this error in the console log: > {code} > java.io.FileNotFoundException: /mnt/hudson_workspace/workspace/server.it.weekly/f623f724/as/itests/org.jboss.tools.as.itests/target/ > work/data/.metadata/.plugins/org.jboss.ide.eclipse.as.core/ > org.jboss.tools.as.itests.CreateServerCheckDefaultsTestorg.jboss.ide.eclipse.as.wildfly.80/xpaths.xml (No such file or directory) > {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... > If this is a normal, expected exception, then I can exclude if from the console parser [1]. > If not, then it should be fixed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26086) SSP server does not send error codes for bad requests

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26086?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26086: ------------------------------- Fix Version/s: 4.11.x > SSP server does not send error codes for bad requests > ----------------------------------------------------- > > Key: JBIDE-26086 > URL: https://issues.jboss.org/browse/JBIDE-26086 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-server-protocol > Affects Versions: 4.6.0.AM3 > Reporter: Jan Richter > Assignee: Rob Stryker > Priority: Major > Fix For: 4.11.x > > > Sending a request the server does not like produces no response, it is simply logged on the server side and the client is not notified of what happened. Something like a code 400 would be appreciated. > For example, initiating a connection with no content-length header simply logs the following on the server side, but the client is stuck waiting. > {noformat}java.lang.IllegalStateException: Missing header Content-Length in input "GET / HTTP/1.1 > Sec-WebSocket-Version: 13 > Sec-WebSocket-Key: 4vrbTo0+BlSk5wK7si6SWQ== > Connection: Upgrade > Upgrade: websocket > Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits > Host: localhost:27511 > " > at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:89) > at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:95) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748){noformat} > This is most likely a 'feature' of lsp4j, thoughts? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26357) JMX MBean Tree is auto collapsing when walking down the tree items of EAP 7.1 server adapter

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26357?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26357: ------------------------------- Fix Version/s: 4.11.x > JMX MBean Tree is auto collapsing when walking down the tree items of EAP 7.1 server adapter > -------------------------------------------------------------------------------------------- > > Key: JBIDE-26357 > URL: https://issues.jboss.org/browse/JBIDE-26357 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.9.0.AM3 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Major > Fix For: 4.11.x > > Attachments: JMXServerConnectionAutoCollapseIssue.gif > > > JMX MBean tree in JMX Navigator do autocollapse when walking the tree items. When I go for an item twice, it will not collapse only on first time. I am not sure about reproducing the issue as I got it when using EAP server adapter. Wildfly is not doing it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26088) arbitrary folder should not be able to be searched for runtimes

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26088?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26088: ------------------------------- Fix Version/s: 4.11.x > arbitrary folder should not be able to be searched for runtimes > --------------------------------------------------------------- > > Key: JBIDE-26088 > URL: https://issues.jboss.org/browse/JBIDE-26088 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-server-protocol > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Major > Fix For: 4.11.x > > > Server currently has following interface / json entry point: > CompletableFuture<List<ServerBean>> findServerBeans(DiscoveryPath path); > However, any arbitrary system path can be searched this way. It'd be better if any discovery path had to be kept in the model via addDiscoveryPath first, to ensure that the server isn't somehow restricted from searching various paths. > Of course right now there's no API or configuration file to actually restrict scanning various folders, but I would imagine that eventually such restrictions would be made such that the void addDiscoveryPath(DiscoveryPath path); entrypoint could restrict or reject additions. > I believe [~dgolovin] disagrees with this approach. Please discuss. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25860) CDK/Minishift Server Adapter - No monitoring port can be added

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-25860?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25860: ------------------------------- Fix Version/s: 4.11.x > CDK/Minishift Server Adapter - No monitoring port can be added > -------------------------------------------------------------- > > Key: JBIDE-25860 > URL: https://issues.jboss.org/browse/JBIDE-25860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.3.AM3 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.11.x > > > What is monitoring good for in server adapters like CDK and/or Minishift if any monitoring is not available and cannot be added? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26445) Remote server cannot start on windows when connected via local remote system type

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26445?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26445: ------------------------------- Fix Version/s: 4.11.x > Remote server cannot start on windows when connected via local remote system type > --------------------------------------------------------------------------------- > > Key: JBIDE-26445 > URL: https://issues.jboss.org/browse/JBIDE-26445 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.9.0.Final > Environment: windows > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.11.x > > > I got this in Console when trying to start remote EAP 7.x server adapter: > {code} > 'cmd' is not recognized as an internal or external command, operable program or batch file. > {code} > And server is still starting until timeout is reached. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26305) Jars inside an EAR application are not compressed

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26305?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26305: ------------------------------- Fix Version/s: 4.11.x > Jars inside an EAR application are not compressed > ------------------------------------------------- > > Key: JBIDE-26305 > URL: https://issues.jboss.org/browse/JBIDE-26305 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Major > Fix For: 4.11.x > > > A customer has reported an issue where an ear project, when deployed to EAP 7.1, contains exploded jars which then breaks his app. It seems that in his case it happens both in the case of a jar inside a war inside an ear, as well as just a jar inside an ear. > Also, when the customer deploys the same app in the same workspace and same eclipse to EAP 6.4, it works fine - all the jars are zipped. > The customer reports that he can change this behavior in the Deployments tab of the server editor, but it would be nice to be able to define this beforehand in a config file. > I tried to reproduce this in devstudio 12 and in my case the behavior was the same with both EAP 6.4 and 7.1 - in both cases an included jar was exploded which I think is wrong. > So two main things to consider: > 1. Is this a bug? I believe it is - a jar lib should always be zipped by default. Or do you disagree? > 2. Is there a way to specify if a module of an EAP is zipped or not in a config file? If not, can this be added? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4645) JDK9 Certification - Hibernate

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4645?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4645: ----------------------------- Fix Version/s: 12.x > JDK9 Certification - Hibernate > ------------------------------ > > Key: JBDS-4645 > URL: https://issues.jboss.org/browse/JBDS-4645 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: hibernate > Reporter: Pavol Srna > Assignee: Rastislav Wagner > Priority: Major > Fix For: 12.x > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4653) JDK9 Certification - Browsersim/Cordovasim/Livereload

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4653?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4653: ----------------------------- Fix Version/s: 12.x > JDK9 Certification - Browsersim/Cordovasim/Livereload > ----------------------------------------------------- > > Key: JBDS-4653 > URL: https://issues.jboss.org/browse/JBDS-4653 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: browsersim, cordovasim, livereload > Reporter: Pavol Srna > Assignee: Rastislav Wagner > Priority: Major > Fix For: 12.x > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4746) GPG key for code siging

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4746?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4746: ----------------------------- Fix Version/s: 12.x > GPG key for code siging > ----------------------- > > Key: JBDS-4746 > URL: https://issues.jboss.org/browse/JBDS-4746 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build > Reporter: Mat Booth > Assignee: Ondrej Dockal > Priority: Major > Fix For: 12.x > > > Hi, this is related to JBDS-4740 -- allow building of flatpak applications. > I will need to GPG sign flatpak applications before users can install them. > Does jenkins know about any GPG keys for code signing? And if so, where does the keyring live? > When I ran "{{gpg --list-keys}}" during a build, to list all the keys in the default keyring location (the default location is ~/.gnupg or /home/hudson/.gnupg in this case), there was no such keyring. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

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 December 2018