June 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Jiri Peterka commented on JBDS-3057: ------------------------------------ Yes, it's Gnome Shell "issue", either Gnome Shell is more strict in terms of application responsiveness or possibly applications are slower on Gnome Shell. Maybe both. > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > Attachments: jbds-not-responding.png > > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3057: ------------------------------------- I don't think there is anything in the workspace log - this is just the OS not happy with the response of the application. But I can check logs later if needed. > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > Attachments: jbds-not-responding.png > > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3057: ------------------------------------- Jirka Peterka says this happens on Fedora sometimes, too. > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > Attachments: jbds-not-responding.png > > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17391) Provide JAX-RS Resource fields type validation

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17391?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-17391: ---------------------------------- Summary: Provide JAX-RS Resource fields type validation (was: Provide JAX-RS Fields type validation) > Provide JAX-RS Resource fields type validation > ---------------------------------------------- > > Key: JBIDE-17391 > URL: https://issues.jboss.org/browse/JBIDE-17391 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta3 > > > From JAX-RS 1.1 spec (chap 3.2): > {quote} > 1. Primitive types. > 2. Types that have a constructor that accepts a single String argument. > 3. Types that have a static method named valueOf or fromString with a single String argument that return an instance of the type. If both methods are present then valueOf MUST be used unless the type is an enum in which case fromString MUST be used. > 4. List<T>, Set<T>, or SortedSet<T>, where T satisfies 2 or 3 above. > {quote} > JAX-RS 2.0 introduced the notion of ParamConverterProvider: > {quote} > Valid parameter types for each of the above annotations are listed in the corresponding Javadoc, however in general (excluding @Context) the following types are supported: > 1. Types for which a ParamConverter is available via a registered ParamConverterProvider. See Javadoc for these classes for more information. > 2. Primitive types. > 3. Types that have a constructor that accepts a single String argument. > 4. Types that have a static method named valueOf or fromString with a single String argument that return an instance of the type. If both methods are present then valueOf MUST be used unless the type is an enum in which case fromString MUST be used1. > 5. List<T>, Set<T>, or SortedSet<T>, where T satisfies 3 or 4 above. > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3057: ------------------------------------- Actually, first start of JBDS wasn't the only time I saw the "not responding" window. When I created a jsp file, the vpe editor took quite a bit of time to load and that triggered this window as well. > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > Attachments: jbds-not-responding.png > > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3057: -------------------------------- Attachment: jbds-not-responding.png Screenshot: !jbds-not-responding.png! > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > Attachments: jbds-not-responding.png > > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3057: -------------------------------- Workaround Description: On the window that says "JBDS is not responding", click Wait and wait until JBDS starts responding again. > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by Martin Malina (JIRA)

Martin Malina created JBDS-3057: ----------------------------------- Summary: JBDS causes "not responding" message on RHEL Key: JBDS-3057 URL: https://issues.jboss.org/browse/JBDS-3057 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.1.1.GA Environment: RHEL 7 Beta OpenJDK 1.7 JBDS 7.1.1 Reporter: Martin Malina I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. On subsequent starts of JBDS with the same workspace, this does not happen. The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3057: ----------------------------- CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? CDW release: ? > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17506) Missing VJET plugin in Central

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-17506: ------------------------------------- Summary: Missing VJET plugin in Central Key: JBIDE-17506 URL: https://issues.jboss.org/browse/JBIDE-17506 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.2.0.Beta2 Reporter: Marián Labuda Priority: Blocker JBT 4.2.0.Beta2a (respin-a) central does not containt VJET plugin. Also in JBDS 8.0.0.Beta2a build B106 is not VJET plugin listed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 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 June 2014