February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or short after startup

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19376: -------------------------------------- Assignee: Rob Stryker I see a lot of as/server in the stack trace. [~rob.stryker] could you please take a look? > Eclipse freezes at or short after startup > ----------------------------------------- > > Key: JBIDE-19376 > URL: https://issues.jboss.org/browse/JBIDE-19376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Environment: Eclipse Luna EE. > Reporter: Anton Meller > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.3.Beta1, 4.3.0.Alpha2 > > Attachments: 20150224_threaddump-1424762289905.tdump, 20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump, 20150226_threaddump-1424936318015.tdump > > > Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. > Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or short after startup

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19376: ----------------------------------- Fix Version/s: 4.2.3.Beta1 4.3.0.Alpha2 > Eclipse freezes at or short after startup > ----------------------------------------- > > Key: JBIDE-19376 > URL: https://issues.jboss.org/browse/JBIDE-19376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Environment: Eclipse Luna EE. > Reporter: Anton Meller > Priority: Critical > Fix For: 4.2.3.Beta1, 4.3.0.Alpha2 > > Attachments: 20150224_threaddump-1424762289905.tdump, 20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump, 20150226_threaddump-1424936318015.tdump > > > Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. > Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or short after startup

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19376: ----------------------------------- Priority: Critical (was: Major) > Eclipse freezes at or short after startup > ----------------------------------------- > > Key: JBIDE-19376 > URL: https://issues.jboss.org/browse/JBIDE-19376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Environment: Eclipse Luna EE. > Reporter: Anton Meller > Priority: Critical > Attachments: 20150224_threaddump-1424762289905.tdump, 20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump, 20150226_threaddump-1424936318015.tdump > > > Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. > Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or short after startup

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19376: ----------------------------------- Component/s: server > Eclipse freezes at or short after startup > ----------------------------------------- > > Key: JBIDE-19376 > URL: https://issues.jboss.org/browse/JBIDE-19376 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.2.Final > Environment: Eclipse Luna EE. > Reporter: Anton Meller > Attachments: 20150224_threaddump-1424762289905.tdump, 20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump, 20150226_threaddump-1424936318015.tdump > > > Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. > Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or short after startup

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19376: ----------------------------------- Issue Type: Bug (was: Feature Request) > Eclipse freezes at or short after startup > ----------------------------------------- > > Key: JBIDE-19376 > URL: https://issues.jboss.org/browse/JBIDE-19376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Environment: Eclipse Luna EE. > Reporter: Anton Meller > Attachments: 20150224_threaddump-1424762289905.tdump, 20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump, 20150226_threaddump-1424936318015.tdump > > > Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. > Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3286) Remove Seam tooling from default JBDS installation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3286?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3286: -------------------------------------- Priority: Blocker (was: Major) > Remove Seam tooling from default JBDS installation > -------------------------------------------------- > > Key: JBDS-3286 > URL: https://issues.jboss.org/browse/JBDS-3286 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, installer, requirements, seam > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.Alpha2 > > > With Seam being pretty much dead and the tools in maintenance mode, I'm opening this issue to discuss whether we should drop Seam from the JBDS installer and only keep it available from JBoss Central (required as part of JBIDE-18922 already). > [~burrsutter], [~maxandersen], [~ldimaggio], [~akazakov], [~mmurray] : WDYT? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3298: -------------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.GA) > Push changes to Existing OpenShift Project > ------------------------------------------ > > Key: JBDS-3298 > URL: https://issues.jboss.org/browse/JBDS-3298 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > Use Case #2 Push changes to Existing OpenShift Project > a) assumes the steps in Use Case #1 JBDS-3297 > b) assumes the end-user has uploaded his SSH keys (to allow for git push) > c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc > d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP > e) Eclipse user will test (JUnit, Arquillian) > f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image) > g) Eclipse user will git add and git commit as appropriate > h) Eclipse user will git push to the original URL provided in Use Case #1 > i) Eclipse user will await the automatic rebuild of a new image, deployment of the same > j) Eclipse user will then be provided a URL and the browser can be opened automatically > Note: > i) auto-build=true, auto-deploy=true > assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c. > A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. > If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3297) Download/Import Existing OpenShift Project

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3297?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3297: -------------------------------------- Fix Version/s: 9.0.0.Beta1 > Download/Import Existing OpenShift Project > ------------------------------------------ > > Key: JBDS-3297 > URL: https://issues.jboss.org/browse/JBDS-3297 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > Use Case #1 - Download/Import Existing OpenShift Project > a) Assume OpenShift is started remotely and provides an entrypoint URL (e.g. http://localhost:8080/osapi/v1beta1/projects) > b) Assume end-user is logged in (ignore auth for now) > c) Assume OpenShift already has some deployed "projects", this "project" definition includes the buildconfig, deployconfig, docker image, source git URL, routes and services. > d) Eclipse user will open a dialog and enter the URL from step a > e) Eclipse user will see a list of "things" associated with "projects" from step 1c > "things" > f) Embedded in one of those things is a Git URL - that will be displayed to the user who will agree to git clone it [1f] > g) If the downloaded items include a Maven project, the Eclipse user will see a newly configured Eclipse project based on Maven with the appropriately configured facets > h) If there is no pom.xml, the Eclipse user will see a newly configured generic Eclipse project containing the downloaded files > i) It is expected that a Maven-based Java project will build locally (leveraging Maven Central and/or maven.repository.redhat.com) > j) It is expected that a Maven-based Java project will deploy to a localhost EAP/Wildfly or a locally running Docker container: > docker run -it -p 8080:8080 openshift/wildfly-8-centos > [1f] https://github.com/openshift/origin/blob/master/examples/sample-app/appli... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3306) Create Deployment from Template

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3306?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3306: -------------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.GA) > Create Deployment from Template > ------------------------------- > > Key: JBDS-3306 > URL: https://issues.jboss.org/browse/JBDS-3306 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Burr Sutter > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > Use Case #3 > Create Deployment from Template > a) Assume OpenShift is started remotely and provides an entrypoint URL > b) Assume end-user is logged in (ignore auth for now) > c) Eclipse user will open a dialog and enter the URL from step a > d) Eclipse user will then be presented with a list of templates from the template library > (initially a set of files on the local filesystem until openshift has a real template library api) > e) The template list should allow sorting so that higher priority items are at the top > We will likely need some form of categorization for templates also > f) The template list should be searchable by keyword > g) Eclipse user will select a particular template and > h) Create a new openshift deployment based on selected template > i) follow steps JBDS-3297 f through j (clone, import, project facets, etc) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3322) JSR-356: Websockets. Content-assist for annotations

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3322?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3322: ------------------------------------------- i'm not sure what kind of content assist this would bring, but for now reduced priority and I've marked it to be look at for alpha2 (at least for triage/plan) > JSR-356: Websockets. Content-assist for annotations > --------------------------------------------------- > > Key: JBDS-3322 > URL: https://issues.jboss.org/browse/JBDS-3322 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Minor > Labels: websockets > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, I wish to take advantage of the new Websockets capability. > Content-assist for annotations such as @ServerEndpoint, @OnMessage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 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 February 2015