February 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-25696) Deadlock when running JBoss Tools Project Validator on startup

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25696?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25696: ------------------------------- Sprint: devex #145 February 2018 > Deadlock when running JBoss Tools Project Validator on startup > -------------------------------------------------------------- > > Key: JBIDE-25696 > URL: https://issues.jboss.org/browse/JBIDE-25696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: JBoss Developer Studio 11.2.0.GA, Windows 10 > Reporter: Vsevolod Golovanov > Assignee: Jeff MAURY > Fix For: 4.5.3.AM2 > > Attachments: lockedup.png, threaddump-1518088511239.tdump > > > The workspace is one EAR project, a couple dozen EJBs, 2 WARs, a couple dozen JAR webfragments (deployed inside the WARs), some misc projects - 67 projects alltogether. > When opening it sometimes locks up completely - UI is not responding, process CPU is at 0%. > Here's what it looks like: !lockedup.png|thumbnail! > This time I just opened the Problems view and clicked Markers, which never opened. But I don't think this isn't necessary, pretty sure it sometimes hangs without clicking anything at all. > It always shows JBoss Tools Project Validator in the Progress view when this happens. > VisualVM reports a deadlock, seems to be JBoss Tools Validator related: [^threaddump-1518088511239.tdump] > I think this used to happen with JBDS10 too, but I don't know for sure, because I don't have the threaddumps. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25696) Deadlock when running JBoss Tools Project Validator on startup

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25696?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25696: ------------------------------- Fix Version/s: 4.5.3.AM2 > Deadlock when running JBoss Tools Project Validator on startup > -------------------------------------------------------------- > > Key: JBIDE-25696 > URL: https://issues.jboss.org/browse/JBIDE-25696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: JBoss Developer Studio 11.2.0.GA, Windows 10 > Reporter: Vsevolod Golovanov > Fix For: 4.5.3.AM2 > > Attachments: lockedup.png, threaddump-1518088511239.tdump > > > The workspace is one EAR project, a couple dozen EJBs, 2 WARs, a couple dozen JAR webfragments (deployed inside the WARs), some misc projects - 67 projects alltogether. > When opening it sometimes locks up completely - UI is not responding, process CPU is at 0%. > Here's what it looks like: !lockedup.png|thumbnail! > This time I just opened the Problems view and clicked Markers, which never opened. But I don't think this isn't necessary, pretty sure it sometimes hangs without clicking anything at all. > It always shows JBoss Tools Project Validator in the Progress view when this happens. > VisualVM reports a deadlock, seems to be JBoss Tools Validator related: [^threaddump-1518088511239.tdump] > I think this used to happen with JBDS10 too, but I don't know for sure, because I don't have the threaddumps. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25696) Deadlock when running JBoss Tools Project Validator on startup

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25696?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25696: ---------------------------------- Assignee: Jeff MAURY > Deadlock when running JBoss Tools Project Validator on startup > -------------------------------------------------------------- > > Key: JBIDE-25696 > URL: https://issues.jboss.org/browse/JBIDE-25696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: JBoss Developer Studio 11.2.0.GA, Windows 10 > Reporter: Vsevolod Golovanov > Assignee: Jeff MAURY > Fix For: 4.5.3.AM2 > > Attachments: lockedup.png, threaddump-1518088511239.tdump > > > The workspace is one EAR project, a couple dozen EJBs, 2 WARs, a couple dozen JAR webfragments (deployed inside the WARs), some misc projects - 67 projects alltogether. > When opening it sometimes locks up completely - UI is not responding, process CPU is at 0%. > Here's what it looks like: !lockedup.png|thumbnail! > This time I just opened the Problems view and clicked Markers, which never opened. But I don't think this isn't necessary, pretty sure it sometimes hangs without clicking anything at all. > It always shows JBoss Tools Project Validator in the Progress view when this happens. > VisualVM reports a deadlock, seems to be JBoss Tools Validator related: [^threaddump-1518088511239.tdump] > I think this used to happen with JBDS10 too, but I don't know for sure, because I don't have the threaddumps. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25681) OpenShift view: Show pods/deployments for apps without service

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25681?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25681: ------------------------------- Fix Version/s: 4.5.x > OpenShift view: Show pods/deployments for apps without service > -------------------------------------------------------------- > > Key: JBIDE-25681 > URL: https://issues.jboss.org/browse/JBIDE-25681 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.3.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Fix For: 4.5.x > > > In OpenShift view it should be also possible to so chow pods, deployments...not only services, because there could be running running application without services. > Steps: > 1. Create new project > 2. Create new resource in project and use this URL for pod: > https://raw.githubusercontent.com/openshift/origin/master/examples/hello-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25623) Forge New and Noteworthy for 4.5.3.AM1

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25623?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-25623. ----------------------------------- Resolution: Rejected > Forge New and Noteworthy for 4.5.3.AM1 > --------------------------------------------------- > > Key: JBIDE-25623 > URL: https://issues.jboss.org/browse/JBIDE-25623 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Labels: task > Fix For: 4.5.3.AM1 > > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25618 #comment Create N&N for Forge 4.5.3.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Forge for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25616) Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25616: ------------------------------------- Fix Version/s: 4.5.3.AM2 (was: 4.5.3.AM1) > Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25616 > URL: https://issues.jboss.org/browse/JBIDE-25616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Fix For: 4.5.3.AM1 > > Attachments: java, screenshot-1.png > > > Starting of server ends with error: > {code:java} > eclipse.buildId=11.2.0.GA-v20180122-2025-B1884 > java.version=1.8.0_151 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/jkopriva/devstudio_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Jan 24 11:21:45 CET 2018 > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25616) Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25616: ------------------------------------- Fix Version/s: 4.5.3.AM1 (was: 4.5.3.AM2) > Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25616 > URL: https://issues.jboss.org/browse/JBIDE-25616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Fix For: 4.5.3.AM1 > > Attachments: java, screenshot-1.png > > > Starting of server ends with error: > {code:java} > eclipse.buildId=11.2.0.GA-v20180122-2025-B1884 > java.version=1.8.0_151 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/jkopriva/devstudio_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Jan 24 11:21:45 CET 2018 > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25504 at 2/8/18 4:00 PM: ------------------------------------------------------------------ work in progress: [adding utility facet to springboot project dependencies|https://github.com/jbosstools/jbosstools-central/pull/417] This patch for jbosstools-central is adding the utility facet to the dependencies of the springboot project, if those already exist in the workspace. It wont handle the case where one would import those dependencies to the workspace once the springboot project already exists (to be implemented). was (Author: adietish): work in progress: [adding utility facet to springboot project dependencies|https://github.com/jbosstools/jbosstools-central/pull/417] > Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift > -------------------------------------------------------------------------------------- > > Key: JBIDE-25504 > URL: https://issues.jboss.org/browse/JBIDE-25504 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.5.3.AM1 > > Attachments: springboot-dependencies.zip > > > When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case: > * the SpringBoot app has a dependency which is avalailable in the workspace > * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ERT-602) [templates] Templates for empty .java files [EBZ#505610]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-602?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-602: -------------------------------- Sprint: devex #144 January 2018 > [templates] Templates for empty .java files [EBZ#505610] > -------------------------------------------------------- > > Key: ERT-602 > URL: https://issues.jboss.org/browse/ERT-602 > Project: Eclipse Release Train > Issue Type: Task > Components: JDT > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Priority: Trivial > Labels: Text, bzira > > Assuming someone tries content-assist on an empty .java file, it would be nice to show templates such as "Create new class <fileName>", "Create new interface <fileName>", "Create new enum <fileName>"... that would scaffold a minimal content (packange and object declaration at least). > Or maybe those completion items could directly open the right New wizard without leaving opportunity to change the name and let the wizard perform the change. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ERT-602) [templates] Templates for empty .java files [EBZ#505610]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-602?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg reassigned ERT-602: ----------------------------------- Assignee: Roland Grunberg > [templates] Templates for empty .java files [EBZ#505610] > -------------------------------------------------------- > > Key: ERT-602 > URL: https://issues.jboss.org/browse/ERT-602 > Project: Eclipse Release Train > Issue Type: Task > Components: JDT > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Priority: Trivial > Labels: Text, bzira > > Assuming someone tries content-assist on an empty .java file, it would be nice to show templates such as "Create new class <fileName>", "Create new interface <fileName>", "Create new enum <fileName>"... that would scaffold a minimal content (packange and object declaration at least). > Or maybe those completion items could directly open the right New wizard without leaving opportunity to change the name and let the wizard perform the change. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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