September 2014 - jbosstools-issues

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18454: ------------------------------------------ [~maxandersen] I'll try/verify the above once I have a system to test against and yes, no doubt I'd prefer a solution without any added depedency. > Cant connect to OpenShift running on RHEL 6.6 when using openjdk (javax.net.ssl.SSLException: Could not generate DH keypair) > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18454 > URL: https://issues.jboss.org/browse/JBIDE-18454 > 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 > > > In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using openjdk. 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] (JBDS-2946) The installer should be fast, simple and work on all platforms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2946?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2946: --------------------------------- Fix Version/s: 9.0.0.Alpha1 (was: 8.0.0.GA) > The installer should be fast, simple and work on all platforms > -------------------------------------------------------------- > > Key: JBDS-2946 > URL: https://issues.jboss.org/browse/JBDS-2946 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: installer > Reporter: Max Rydahl Andersen > Fix For: 9.0.0.Alpha1 > > -- 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 Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3057: -------------------------------------- Did anything improve on this topic with the move to Luna SR1 ? > 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] (JBDS-3064) New JBDS 8 Welcome screen graphics

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3064?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3064: -------------------------------------- [~maxandersen] Is there anything we can do so close from GA ? > New JBDS 8 Welcome screen graphics > ---------------------------------- > > Key: JBDS-3064 > URL: https://issues.jboss.org/browse/JBDS-3064 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: ui/branding > Affects Versions: 8.0.0.Beta2 > Reporter: Pavol Srna > Fix For: 8.0.0.CR2 > > > JBDS 8 comes with new splash and installer graphics (see https://issues.jboss.org/browse/JBDS-3036) > It would be good to have new graphics also for the Welcome screen. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15609) versionwatch should ignore when there's a folder & jar which are identical

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15609?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-15609: ----------------------------------- Fix Version/s: 4.3.0.Alpha1 (was: 4.2.0.Final) > versionwatch should ignore when there's a folder & jar which are identical > -------------------------------------------------------------------------- > > Key: JBIDE-15609 > URL: https://issues.jboss.org/browse/JBIDE-15609 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Fix For: 4.3.0.Alpha1 > > > A while ago I added a facility to jar up feature and plugin folders so they could have their md5 sums compared. > Now, the vwatch tool complains when there's a folder and a jar present. > Two possible solutions to this come to mind: > a) ignore this - do not report as *{color:red}a problem{color}* > b) whenever a folder is jarred up, delete the source folder, so the above condition cannot occur -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17732) javaee7 samples require groovy compiler plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17732?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17732: ---------------------------------------- Fix Version/s: 4.2.0.Final (was: 4.2.0.CR2) > javaee7 samples require groovy compiler plugin > ---------------------------------------------- > > Key: JBIDE-17732 > URL: https://issues.jboss.org/browse/JBIDE-17732 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.2.0.Beta2 > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.Final > > > Java EE7 samples (https://github.com/javaee-samples/javaee7-samples/) require the Eclipse Groovy Compiler in order to be imported without any error. > We should see > - if the goovy compiler has been released for Luna > - document how to import the samples in Eclipse in the README.md file on github, so that users know how to import and get started with the samples on Eclipse / JBoss Tools. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18448) Create new Visual Editor FAQ

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18448?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18448: ---------------------------------------- Assignee: Max Rydahl Andersen (was: Konstantin Marmalyukov) > Create new Visual Editor FAQ > ---------------------------- > > Key: JBIDE-18448 > URL: https://issues.jboss.org/browse/JBIDE-18448 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: visual-page-editor-core > Affects Versions: 4.2.0.CR1 > Reporter: Konstantin Marmalyukov > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.CR2 > > > Visual Editor FAQ should be moved to tools.jboss.org -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17404) CordovaSim cannot be launched on RHEL7

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17404?page=com.atlassian.jira.plugi... ] Karel Piwko commented on JBIDE-17404: ------------------------------------- Sorry for this taking that long. It is in my todo list for this week, will be ready tomorrow morning. > CordovaSim cannot be launched on RHEL7 > -------------------------------------- > > Key: JBIDE-17404 > URL: https://issues.jboss.org/browse/JBIDE-17404 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Environment: RHEL7 latest, 64bit > Installed webkitgtk3-devel 0:2.0.4-6-el7 > TicketMonster Cordava example from latest WFK > JBDS 8.0.0.Beta1 > OpenJDK 7 > Reporter: Karel Piwko > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.CR2 > > Attachments: CordovaSimFailure.png, libwebkit2gtk.content, snapshot1.png, webkitgtk.content, webkitgtk3.content > > > Launching BrowserSim fails with NPE, adding information from workspace log > Before webkitgtk3-devel is installed > {code} > !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 13:03:54.128 > !MESSAGE org.jboss.tools.aerogear.hybrid.core > !ENTRY org.jboss.tools.vpe.browsersim 4 0 2014-05-23 13:03:56.162 > !MESSAGE BrowserSim is failed to start with the following error: > "No more handles" > Please note that WebKitGTK 1.2.0 or newer must be installed and available in the library load path. > If not, use your package manager to install libwebkitgtk. > Also see <a href="https://community.jboss.org/docs/DOC-18100">BrowserSim FAQ</a>. > Stack trace: > org.eclipse.swt.SWTError: No more handles > at org.eclipse.swt.SWT.error(SWT.java:4467) > at org.eclipse.swt.SWT.error(SWT.java:4356) > at org.eclipse.swt.SWT.error(SWT.java:4327) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:103) > at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:36) > at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:25) > at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:37) > at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:39) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.createCordovaSim(CordovaSimRunner.java:189) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:90) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:84) > {code} > After: > {code} > !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380 > !MESSAGE org.jboss.tools.aerogear.hybrid.core > !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380 > !MESSAGE org.jboss.tools.aerogear.hybrid.core > !ENTRY org.eclipse.core.jobs 4 2 2014-05-23 14:03:57.395 > !MESSAGE An internal error occurred during: "Launching TicketMonster-Cordova". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:157) > at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:115) > at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationDelegate.launch(CordovaSimLaunchConfigurationDelegate.java:24) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18454: ---------------------------------------- Assignee: Andre Dietisheim > Cant connect to OpenShift running on RHEL 6.6 when using openjdk (javax.net.ssl.SSLException: Could not generate DH keypair) > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18454 > URL: https://issues.jboss.org/browse/JBIDE-18454 > 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 > > > In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using openjdk. 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-18454) Cant connect to OpenShift running on RHEL 6.6 when using openjdk (javax.net.ssl.SSLException: Could not generate DH keypair)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18454: --------------------------------------------- FYI: I do not think we can safely rely/introduce dependency on bouncy castle at this time. Is there no way to do this without bouncy castle ? > Cant connect to OpenShift running on RHEL 6.6 when using openjdk (javax.net.ssl.SSLException: Could not generate DH keypair) > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18454 > URL: https://issues.jboss.org/browse/JBIDE-18454 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Priority: Blocker > Fix For: 4.2.0.CR2 > > > In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using openjdk. 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2014