October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18502) Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-18502: ---------------------------------------- Summary: Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair) Key: JBIDE-18502 URL: https://issues.jboss.org/browse/JBIDE-18502 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Blocker Fix For: 4.2.0.CR2 Attachments: ssl-error-on-connect.png In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using jdks (openjdk and sun) < 1.8 on linux. We have to verify that this affects the Eclipse based tooling (that's also using openshift-java-client) {code} java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair at hudson.plugins.openshift.OpenShiftCloud.getOpenShiftConnection(OpenShiftCloud.java:186) at hudson.plugins.openshift.OpenShiftCloud.getSlaves(OpenShiftCloud.java:877) at hudson.plugins.openshift.OpenShiftCloud.provisionSlave(OpenShiftCloud.java:451) at hudson.plugins.openshift.OpenShiftCloud.provision(OpenShiftCloud.java:413) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:368) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18501) JMX Navigator never clean up Local Processes nodes

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18501?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18501: ---------------------------------- Attachment: jmx-navigator.png > JMX Navigator never clean up Local Processes nodes > -------------------------------------------------- > > Key: JBIDE-18501 > URL: https://issues.jboss.org/browse/JBIDE-18501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.0.CR1 > Environment: Linux, x86_64, Java 7 > Reporter: Denis Golovin > Attachments: jmx-navigator.png > > > After running JBT couple days without restart JMX Navigator gets stuffed with old local processes (see attached picture [^jmx-navigator.png]. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18501) JMX Navigator never clean up Local Processes nodes

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-18501: ------------------------------------- Summary: JMX Navigator never clean up Local Processes nodes Key: JBIDE-18501 URL: https://issues.jboss.org/browse/JBIDE-18501 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 4.2.0.CR1 Environment: Linux, x86_64, Java 7 Reporter: Denis Golovin After running JBT couple days without restart JMX Navigator gets stuffed with old local processes (see attached picture [^jmx-navigator.png]. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3169) For JBDS 8.0.0.CR2: Prepare for CR2 release

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3169?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-3169. ------------------------------- All requested changes are done in master and jbosstools-4.2.x branches. > For JBDS 8.0.0.CR2: Prepare for CR2 release > ------------------------------------------- > > Key: JBDS-3169 > URL: https://issues.jboss.org/browse/JBDS-3169 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 8.0.0.CR2 > > > For JBDS 8.0.0.CR2: Please perform the following tasks: > 0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise, for all other projects: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT > {code} > 5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*: > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and > * *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3169) For JBDS 8.0.0.CR2: Prepare for CR2 release

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3169?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3169: ----------------------------------- Assignee: Denis Golovin > For JBDS 8.0.0.CR2: Prepare for CR2 release > ------------------------------------------- > > Key: JBDS-3169 > URL: https://issues.jboss.org/browse/JBDS-3169 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 8.0.0.CR2 > > > For JBDS 8.0.0.CR2: Please perform the following tasks: > 0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise, for all other projects: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT > {code} > 5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*: > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and > * *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3169) For JBDS 8.0.0.CR2: Prepare for CR2 release

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3169?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3169. --------------------------------- Resolution: Done > For JBDS 8.0.0.CR2: Prepare for CR2 release > ------------------------------------------- > > Key: JBDS-3169 > URL: https://issues.jboss.org/browse/JBDS-3169 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 8.0.0.CR2 > > > For JBDS 8.0.0.CR2: Please perform the following tasks: > 0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise, for all other projects: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT > {code} > 5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*: > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and > * *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3057: ------------------------------------- It is Gnome behavior. It 'pings' window continuously and if ping event is not processed (UI thread is blocked or do something except event processing) in 5 seconds shows "Window is not responding" dialog. For instance I have never seen the window like this in Xfce Desktop Environment. > 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 > Components: upstream > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 8.0.0.GA > > 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.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12337) json_string formatter recognized as invalid syntax

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12337?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-12337: ---------------------------------- Fix Version/s: 4.3.x (was: LATER) > json_string formatter recognized as invalid syntax > -------------------------------------------------- > > Key: JBIDE-12337 > URL: https://issues.jboss.org/browse/JBIDE-12337 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 3.3.0.Final > Environment: Eclipse Juno > Reporter: Ljudevit Hab > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.3.x > > > ?json_string formatter is not recognized as valid syntax: > for example: > email: "${user.email?json_string}" -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18500) Upgrade Forge Runtime to 2.12.0.Final

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-18500: --------------------------------------- Summary: Upgrade Forge Runtime to 2.12.0.Final Key: JBIDE-18500 URL: https://issues.jboss.org/browse/JBIDE-18500 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: forge Affects Versions: 4.2.0.CR1 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 4.2.0.CR2 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8526) Freemarker content assist doesn't work when inside a tag or tag attribute

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8526?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-8526: --------------------------------- Fix Version/s: 4.2.x 4.3.0.Alpha1 (was: 4.2.0.CR2) > Freemarker content assist doesn't work when inside a tag or tag attribute > ------------------------------------------------------------------------- > > Key: JBIDE-8526 > URL: https://issues.jboss.org/browse/JBIDE-8526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 3.3.x > Environment: Windows XP, > Reporter: Ehrann Mehdan > Assignee: Peter Palaga > Fix For: 4.2.x, 4.3.0.Alpha1 > > > In Freemarker 1.1.0.v20110303-1225-H55-Alpha1 > Eclipse platform version: 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi > Build id: M20110210-1200 > This code will not trigger content assist when pressing ctrl+space with a context named data that has property "someValue" > <tag attribute="${data.someValue}">... > This code will (removed opening tag bracket) > tag attribute="${data.someValue}">... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 October 2014