October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18457) EAP 6.1 fails to start on Windows 7 - stuck on Starting

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18457?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18457: --------------------------------------------- So not having the right java version sounds like reasonable explanation. What we want to be sure though is that if we have Java 7 and Java 8 installed the Java 7 one is chosen over Java 8 for this EAP instance by default (users can change if they want to). That is the case as far as I remember, can you guys confirm that is what you see ? Meaning if Brian installs java 7 into his JBDS 8 it starts working ? > EAP 6.1 fails to start on Windows 7 - stuck on Starting > ------------------------------------------------------- > > Key: JBIDE-18457 > URL: https://issues.jboss.org/browse/JBIDE-18457 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR2 > > > This is followup of Brian's comments in JBIDE-16066 where he couldn't get EAP 6.1 to start on Windows 7. I tried the same and get the same result. Everything works fine on my mac. > 1. Start JBDS 8.0.0.CR1 > 2. Download EAP 6.1 via runtime detection > 3. Start the server > In my case, at first I got "Starting jboss-eap-6.1: (0 %)" in the status bar and nothing else for like 5 minutes, then the server console showed up and showed: > {code} > 15:28:51,082 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1 > 15:28:51,704 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1 > 15:28:51,824 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting > {code} > And with this the status bar changed to 100 % and the progress view shows: > Preparing launch deletage. > It's been like this at least 5 minutes now. The server is not started. > I checked with Brian and he just didn't witness the first part where there was no console, but he did get what I got after 5 minutes - his server was stuck and would never really start. > ATM I only tried this the one way - EAP 6.1 downloaded via runtime detection. > In my case I have Oracle jdk 1.8, in Brian's case it was 1.7, so it doesn't seem to matter. > Right now I haven't tried other server versions. -- 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 (javax.net.ssl.SSLException: Could not generate DH keypair)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated JBIDE-18454: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1145848, https://bugzilla.redhat.com/show_bug.cgi?id=1127667, https://bugzilla.redhat.com/show_bug.cgi?id=1148308 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1145848, https://bugzilla.redhat.com/show_bug.cgi?id=1127667) > Cant connect to OpenShift running on RHEL 6.6 (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 > > 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 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-18457) EAP 6.1 fails to start on Windows 7 - stuck on Starting

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18457?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18457: ------------------------------------- I'll leave it open and targeted for now. If I finish all my other issues I'll work on replicating on windows. Otherwise I'll push it. > EAP 6.1 fails to start on Windows 7 - stuck on Starting > ------------------------------------------------------- > > Key: JBIDE-18457 > URL: https://issues.jboss.org/browse/JBIDE-18457 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR2 > > > This is followup of Brian's comments in JBIDE-16066 where he couldn't get EAP 6.1 to start on Windows 7. I tried the same and get the same result. Everything works fine on my mac. > 1. Start JBDS 8.0.0.CR1 > 2. Download EAP 6.1 via runtime detection > 3. Start the server > In my case, at first I got "Starting jboss-eap-6.1: (0 %)" in the status bar and nothing else for like 5 minutes, then the server console showed up and showed: > {code} > 15:28:51,082 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1 > 15:28:51,704 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1 > 15:28:51,824 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting > {code} > And with this the status bar changed to 100 % and the progress view shows: > Preparing launch deletage. > It's been like this at least 5 minutes now. The server is not started. > I checked with Brian and he just didn't witness the first part where there was no console, but he did get what I got after 5 minutes - his server was stuck and would never really start. > ATM I only tried this the one way - EAP 6.1 downloaded via runtime detection. > In my case I have Oracle jdk 1.8, in Brian's case it was 1.7, so it doesn't seem to matter. > Right now I haven't tried other server versions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-16066: --------------------------------------- [~bfitzpat], FYI, Radoslav Rabara is no longer working for Red Hat, so I doubt you will get any more feedback from him ;) > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18457) EAP 6.1 fails to start on Windows 7 - stuck on Starting

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18457?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18457: --------------------------------------- Rob, as long as we're sure that it's just the bad Java we used, feel free to bump this to some future release. > EAP 6.1 fails to start on Windows 7 - stuck on Starting > ------------------------------------------------------- > > Key: JBIDE-18457 > URL: https://issues.jboss.org/browse/JBIDE-18457 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR2 > > > This is followup of Brian's comments in JBIDE-16066 where he couldn't get EAP 6.1 to start on Windows 7. I tried the same and get the same result. Everything works fine on my mac. > 1. Start JBDS 8.0.0.CR1 > 2. Download EAP 6.1 via runtime detection > 3. Start the server > In my case, at first I got "Starting jboss-eap-6.1: (0 %)" in the status bar and nothing else for like 5 minutes, then the server console showed up and showed: > {code} > 15:28:51,082 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1 > 15:28:51,704 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1 > 15:28:51,824 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting > {code} > And with this the status bar changed to 100 % and the progress view shows: > Preparing launch deletage. > It's been like this at least 5 minutes now. The server is not started. > I checked with Brian and he just didn't witness the first part where there was no console, but he did get what I got after 5 minutes - his server was stuck and would never really start. > ATM I only tried this the one way - EAP 6.1 downloaded via runtime detection. > In my case I have Oracle jdk 1.8, in Brian's case it was 1.7, so it doesn't seem to matter. > Right now I haven't tried other server versions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17619) Console for remote server disappears when workspace is switched

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17619?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17619: ------------------------------------- Pushed on the strength of fred's +1. It might be better to get it into the repo to save time and if further changes are needed (doubtful) we can make those adjustments. > Console for remote server disappears when workspace is switched > --------------------------------------------------------------- > > Key: JBIDE-17619 > URL: https://issues.jboss.org/browse/JBIDE-17619 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > > This happened to me today. I created a remote server (EAP 6.2, management, no runtime) and when I started it, I saw the console output for the server. But after some more tinkering with it, the console suddenly stopped appearing (I had the console view open). Not even IDE restart helped. > The only thing that helped me here was to delete the server and create a new one. > I think I have a way to reproduce this - it actually happens when you create the server, then switch to a new workspace, then back again. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-534) Forge How To: Generate a Basic UI for Your Application Data

by Suz Dorfield (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-534?page=com.atlassian.jira.plug... ] Suz Dorfield commented on TOOLSDOC-534: --------------------------------------- First draft completed: https://docs.google.com/a/redhat.com/document/d/1gXURYp4-5z5Af68wubLdzG91... > Forge How To: Generate a Basic UI for Your Application Data > ----------------------------------------------------------- > > Key: TOOLSDOC-534 > URL: https://issues.jboss.org/browse/TOOLSDOC-534 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide - Forge Tools > Reporter: Michelle Murray > Assignee: Suz Dorfield > Fix For: 4.2.0.Final > > -- 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