July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4460) Devsuite registry entry has hardcoded version to 1.4.0

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4460?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4460. ----------------------------- Verified, closing. > Devsuite registry entry has hardcoded version to 1.4.0 > ------------------------------------------------------ > > Key: JBDS-4460 > URL: https://issues.jboss.org/browse/JBDS-4460 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM2 > Environment: windows > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.0.0.AM2 > > > Red Hat Development Suite entry in windows apps still shows as version 1.4.0.GA -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24556) Internal Error when creating runtime+server after creating server+runtime

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24556?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24556. --------------------------------- Verified in devstudio 11.0.0.AM2. > Internal Error when creating runtime+server after creating server+runtime > ------------------------------------------------------------------------- > > Key: JBIDE-24556 > URL: https://issues.jboss.org/browse/JBIDE-24556 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > Following up on JBDS-4128, Preferences -> Server -> Runtime Environments -> Add and checking Create server. This seems to work now. But when I was testing it, I came across the Internal Error in that wizard and I couldn't reproduce it afterwards. > Now I have a way of reproducing the error again. > Steps: > 1. Create an EAP 7.1 server using Servers –> New. Choose all the defaults - you will also create a runtime as part of this. > 2. Go to Preferences -> Server -> Runtime Environments and click Add. Add a new runtime (you can use the same path as the existing one) and check Create server, so that a new server adapter should be created as well. > After you get past the new runtime page, you should see the server page where you choose the server profile. But instead, you will see just Internal Error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2925) We want tools to allow interacting with jboss servers via management operations as much as possible to integrate better with RBAC, arquillian, domain mode etc.

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2925?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-2925. ------------------------------- OK, closing. > We want tools to allow interacting with jboss servers via management operations as much as possible to integrate better with RBAC, arquillian, domain mode etc. > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2925 > URL: https://issues.jboss.org/browse/JBDS-2925 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 11.0.0.AM1 > > > Pushing this. Not all subtasks are done. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24560) Server adapter very slow to restart in debug

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24560?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24560: ------------------------------------- After looking into this, the delay is universally determined by updateDebugConfig, and, specifically, waitFor(rcListenerJob, monitor); This job waits around for a matching pod to be non-null. It receives updates from the client whenever the client event framework throws a change event. I can't see anything in the code at all that is hindering or slowing down the process, or delaying unnecessarily. In fact the code looks very efficient at handling these events, and the delay seems 100% on the runtime side while waiting for a proper event to be received that indicates everything is ok to proceed. =/ partial log: https://paste.fedoraproject.org/paste/PjykYz7uIxnSa8jUR~L3qA > Server adapter very slow to restart in debug > --------------------------------------------- > > Key: JBIDE-24560 > URL: https://issues.jboss.org/browse/JBIDE-24560 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.5.0.Final > > > When the server adapter has been created and just started, if you restart in debug, it is very slow to restart. It seems to happen only the first time after you created it and started. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24291) Improve initial loading of JMX Connection tree

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24291?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24291. --------------------------------- Closing this in favor of the followup JIRAs JBIDE-24593 (now closed) and JBIDE-24759 (newly opened). > Improve initial loading of JMX Connection tree > ---------------------------------------------- > > Key: JBIDE-24291 > URL: https://issues.jboss.org/browse/JBIDE-24291 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: JMXLoad.mp4 > > > JMX Navigator is taking quite a long time to load the first level of elements when the connection is targeting a remote server with quite a high latency (such open.paas.redhat.com which is taking around 450ms for each request for me) > It would be nice to improve the lazy-loading to be able to display the first level of the tree without loading every MBeans and doing one query per MBean Names registered on the server. > For instance on a FIS project, it is 112 MBean Names * 450ms = 50.4s! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24593) Reconnect to jmx yields progress monitor errors

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24593?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24593. --------------------------------- I'm fine with your explanation of the trouble with the progress monitors. But you missed the first part of the description: {quote} when I connect, expand some nodes, call refresh, collapse them then disconnect then reconnect, all the previously expanded node are loaded {quote} I checked and it still happens to me, so I created JBIDE-24759 for that. Closing this JIRA. > Reconnect to jmx yields progress monitor errors > ----------------------------------------------- > > Key: JBIDE-24593 > URL: https://issues.jboss.org/browse/JBIDE-24593 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.5.0.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM2 > > Attachments: JMXLoad.mp4 > > > when I connect, expand some nodes, call refresh, collapse them then disconnect then reconnect, all the previously expanded node are loaded with a progress monitor which is not showing progress and stay blocked at 0% -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24759) JMX Monitor: If you collapse nodes and reset connection, nodes will expand again

by Martin Malina (JIRA)

Martin Malina created JBIDE-24759: ------------------------------------- Summary: JMX Monitor: If you collapse nodes and reset connection, nodes will expand again Key: JBIDE-24759 URL: https://issues.jboss.org/browse/JBIDE-24759 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 4.5.0.AM2 Reporter: Martin Malina when I connect, expand some nodes, call refresh, collapse them then disconnect then reconnect, all the previously expanded node are loaded -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24758) Server editor complains about wrong runtime folder even if fixed

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24758?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24758: --------------------------------------- What's worse, when I actually tried to start the server, it still tried to use the old location: The archive: /Users/rasp/tmp/jboss-eap-6.4/jboss-modules.jar which is referenced by the classpath, does not exist. I expected that the server start simply failed - it was an error pop up window. But it keeps Starting, even though there is no output in the console. I had to quit it using the stop button in servers view. I checked again in the server editor and Runtime Environment and it shows the correct path there. So something is fishy. I then tried to go through Behavior Profile and just clicked Finish, hoping that this would reset the server and it would work now. But no, the server still won't start. If I go to Preferences -> Server -> Runtimes and then Edit on the runtime, it contains the correct path. So I think it must be some kind of caching problem. I restarted the IDE and it still fails. Again, I checked that the runtime has the correct path. And now I also checked the launch config. And that seems ok too - these are the calculated arguments, all containing the correct path: {code} -mp "/Users/rasp/jbossqa/runtimes/jboss-eap-6.4/modules" -jaxpmodule javax.xml.jaxp-provider -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/jboss-eap-6.4/standalone {code} > Server editor complains about wrong runtime folder even if fixed > ---------------------------------------------------------------- > > Key: JBIDE-24758 > URL: https://issues.jboss.org/browse/JBIDE-24758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > > I had a runtime and server adapter set up for eap 6.4. I deleted the server on the disk. When I opened the server editor, I was shown a red message in the status bar: > The server's runtime folder does not exist: ...... > So far so good. > So I unzip eap 6.4 somewhere else, clicked Runtime Environment in the server editor, and pointed the runtime to the new correct directory. Then I saved the editor. But the error message in the status bar still won't go away. I have to close the editor and then open it again, then the message no longer shows up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24758) Server editor complains about wrong runtime folder even if fixed

by Martin Malina (JIRA)

Martin Malina created JBIDE-24758: ------------------------------------- Summary: Server editor complains about wrong runtime folder even if fixed Key: JBIDE-24758 URL: https://issues.jboss.org/browse/JBIDE-24758 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.5.0.AM2 Reporter: Martin Malina I had a runtime and server adapter set up for eap 6.4. I deleted the server on the disk. When I opened the server editor, I was shown a red message in the status bar: The server's runtime folder does not exist: ...... So far so good. So I unzip eap 6.4 somewhere else, clicked Runtime Environment in the server editor, and pointed the runtime to the new correct directory. Then I saved the editor. But the error message in the status bar still won't go away. I have to close the editor and then open it again, then the message no longer shows up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24509) No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24509?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24509: ------------------------------------ [~juzhao] Checked with raw Neon.1 and use 'Update my installation' without a problem. Will close it unless you have another remark > No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final > ------------------------------------------------------------------------ > > Key: JBIDE-24509 > URL: https://issues.jboss.org/browse/JBIDE-24509 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Environment: JBoss Tools 4.4.4.Final > http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_... > Eclipse Neon 4.6.1 > Fedora 24 and Windows 10 > Reporter: Xia Zhao > Priority: Blocker > Fix For: 4.5.x > > Attachments: OpenShift3.png, Screenshot from 2017-05-25 13-37-32.png, Screenshot from 2017-05-25 14-25-53.png, Screenshot from 2017-06-02 10-20-42.png, Screenshot from 2017-06-02 10-39-16.png, Screenshot from 2017-06-02 10-54-54.png > > > Description of problem: > No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final, after installation, only these 3 tools exist without having the openshift v3 tools: > JBoss OpenShift 2 Tools > JBoss OpenShift JavaScript Tools > JBoss Tools EGit Integration > Version-Release number of selected component (if applicable): > JBoss Tools 4.4.4.Final > http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_... > How reproducible: > Always > Steps to Reproduce: > 1.Install JBT for Openshift v3 Tools according to http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_...: > --> Add the following URL to Eclipse Neon 4.6.1 installation via: > Help > Install New Software... > Work with: > http://download.jboss.org/jbosstools/neon/stable/updates/ > Then select all the components, choose to install them. > 2. Restart Eclipse Neon 4.6.1 after JTB installation finished > 3. Go into Openshift Explorer window, click on "New Connections Wizard", choose "Openshift 3" for server type, the Authentication panel is empty > 4. Go to Help > Intallation Details, search for openshift > Actual results: > 4. JBoss OpenShift 3 Tools are not installed, only the following 3 exist: > JBoss OpenShift 2 Tools 3.3.3.v20170510-1453 org.jboss.tools.openshift.express.feature.feature.group JBoss by Red Hat > JBoss OpenShift JavaScript Tools 3.3.3.v20170502-0607 org.jboss.tools.openshift.js.feature.feature.group JBoss by Red Hat > JBoss Tools EGit Integration 3.3.3.v20170405-1252 org.jboss.tools.openshift.egit.integration.feature.feature.group JBoss by Red Hat > Expected results: > JBoss OpenShift 3 Tools should be installed if following http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_... > Additional info: > Issue reproduced on both Fedora 24 and Windows 10. > This is a regression, with old JBT build 4.3.3 Final, the openshift 3 tools existed and worked fine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2017