September 2014 - jbosstools-issues

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

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16066: ------------------------------------------- I have a workaround for JBIDE-18461, but it would be MUCH BETTER if it was fixed upstream. It is the cause of the "The JBoss WS Runtime Location is not set. Please set the location on the JBoss WS preferences page." message that comes up when you try to go beyond the first page of the WTP-based Web Service wizard. I suspect that it's a timing thing, because I can get WS projects to deploy and start sometimes via the wizard in my dev environment. But it's inconsistent. > 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-18461) org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61

by Brian Fitzpatrick (JIRA)

Brian Fitzpatrick created JBIDE-18461: ----------------------------------------- Summary: org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61 Key: JBIDE-18461 URL: https://issues.jboss.org/browse/JBIDE-18461 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.0.CR1 Reporter: Brian Fitzpatrick Priority: Critical When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework -- 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 Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16066: ------------------------------------------- As a quick update... First, yes EAP_61 should be in the ALL_JBOSS_RUNTIMES list. I created JBIDE-18461 for this problem. > 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-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16066: ------------------------------------------- [~rrabara] Is there a reason you click the "Generate application.xml deployment descriptor" checkbox? Isn't that optional now for AS7-based runtimes? > 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-18460) 'Add type to deployment' quickfix doesn't work with abstract classes

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-18460: ------------------------------------- Summary: 'Add type to deployment' quickfix doesn't work with abstract classes Key: JBIDE-18460 URL: https://issues.jboss.org/browse/JBIDE-18460 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing-tools Affects Versions: 4.2.0.CR1 Reporter: Snjezana Peco Fix For: 4.2.1.Final, 4.3.0.Alpha1 Steps to reproduce: - create an abstract Arquillian JUnit test with a deployment method - create an Arquillian JUnit test extending the previous created abstract class - add a type not included in the deployment method to the test created in the step 2 The "Type is not included in any deployment" marker will be created properly - call the "Add type to deployment" quickfix You will get the "Cannot find a deployment method" dialog. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3143) Closing the internal browser with JBDS 8.0.CR1 on RHEL 6.5 crashes JBDS8 - with Java8

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-3143?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-3143: ------------------------------------- [~ldimaggio], did you test the issue using the servers described in https://mojo.redhat.com/docs/DOC-67643 and, if so, which of them? > Closing the internal browser with JBDS 8.0.CR1 on RHEL 6.5 crashes JBDS8 - with Java8 > ------------------------------------------------------------------------------------- > > Key: JBDS-3143 > URL: https://issues.jboss.org/browse/JBDS-3143 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 8.0.0.CR1 > Environment: RHEL 6.5 > java version "1.8.0" > Java(TM) SE Runtime Environment (build 1.8.0-b132) > Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode) > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 8.0.1.GA > > > To recreate: > * Start JBDS8 > * Open Internal Browser view > * Navigate to a site - such as www.redhat.com > * Close the browser - JBDS8 crashes -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3141) Test victi.ms maven plugin works within jbds (or at least does not fail)

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3141?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3141: ------------------------------------ Although - the sample available here: https://github.com/victims/victims-enforcer/tree/master/sample - seems to have a bug in it as it always fails with a vulnerability. ;-) > Test victi.ms maven plugin works within jbds (or at least does not fail) > ------------------------------------------------------------------------ > > Key: JBDS-3141 > URL: https://issues.jboss.org/browse/JBDS-3141 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: maven > Reporter: Burr Sutter > Assignee: Len DiMaggio > Fix For: 8.0.0.CR2 > > Attachments: Screenshot.png > > > http://victi.ms has a maven plugin to check/assert maven dependencies have issues. > should check how it works and if it works within eclipse -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3141) Test victi.ms maven plugin works within jbds (or at least does not fail)

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3141?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3141: ------------------------------- Attachment: Screenshot.png But - it does report the "ignore" warning that Burr asked about: maven-enforcer-plugin (goal "enforce") is ignored by m2e. pom.xml /sample line 56 Maven Project Build Lifecycle Mapping Problem > Test victi.ms maven plugin works within jbds (or at least does not fail) > ------------------------------------------------------------------------ > > Key: JBDS-3141 > URL: https://issues.jboss.org/browse/JBDS-3141 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: maven > Reporter: Burr Sutter > Assignee: Len DiMaggio > Fix For: 8.0.0.CR2 > > Attachments: Screenshot.png > > > http://victi.ms has a maven plugin to check/assert maven dependencies have issues. > should check how it works and if it works within eclipse -- 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-18454 at 9/30/14 3:10 PM: ------------------------------------------------------------------- In a POC the following seems to work for me (not tested extensively yet): {code} SSLSocketFactory wrappingSocketFactory = new SSLSocketFactory() { @Override public Socket createSocket(InetAddress arg0, int arg1, InetAddress arg2, int arg3) throws IOException { return socketFactory.createSocket(arg0, arg1, arg2, arg3); } @Override public Socket createSocket(String arg0, int arg1, InetAddress arg2, int arg3) throws IOException, UnknownHostException { return socketFactory.createSocket(arg0, arg1, arg2, arg3); } @Override public Socket createSocket(InetAddress arg0, int arg1) throws IOException { return socketFactory.createSocket(arg0, arg1); } @Override public Socket createSocket(String arg0, int arg1) throws IOException, UnknownHostException { return socketFactory.createSocket(arg0, arg1); } @Override public String[] getSupportedCipherSuites() { return null; } @Override public String[] getDefaultCipherSuites() { return null; } @Override public Socket createSocket(Socket s, String host, int port, boolean autoClose) throws IOException { SSLSocket socket = (SSLSocket) socketFactory.createSocket(s, host, port, autoClose); List<String> ciphers = new ArrayList<String>(); for (String cipher : socket.getEnabledCipherSuites()) { if (!cipher.contains("_DHE_")) { ciphers.add(cipher); } }; socket.setEnabledCipherSuites(ciphers.toArray(new String[ciphers.size()])); return socket; } }; ((HttpsURLConnection) connection).setSSLSocketFactory(wrappingSocketFactory); {code} I dont know yet why *#getSupportedCipherSuites* is never called in my current testing (my initial idea was to have them returning all but the _DHE_ ciphers from the wrapped socket factory) was (Author: adietish): In a POC the following seems to work for me (not tested extensively yet): {code} SSLSocketFactory wrappingSocketFactory = new SSLSocketFactory() { @Override public Socket createSocket(InetAddress arg0, int arg1, InetAddress arg2, int arg3) throws IOException { return socketFactory.createSocket(arg0, arg1, arg2, arg3); } @Override public Socket createSocket(String arg0, int arg1, InetAddress arg2, int arg3) throws IOException, UnknownHostException { return socketFactory.createSocket(arg0, arg1, arg2, arg3); } @Override public Socket createSocket(InetAddress arg0, int arg1) throws IOException { return socketFactory.createSocket(arg0, arg1); } @Override public Socket createSocket(String arg0, int arg1) throws IOException, UnknownHostException { return socketFactory.createSocket(arg0, arg1); } @Override public String[] getSupportedCipherSuites() { return null; } @Override public String[] getDefaultCipherSuites() { return null; } @Override public Socket createSocket(Socket s, String host, int port, boolean autoClose) throws IOException { SSLSocket socket = (SSLSocket) socketFactory.createSocket(s, host, port, autoClose); List<String> ciphers = new ArrayList<String>(); for (String cipher : socket.getEnabledCipherSuites()) { if (!cipher.contains("_DHE_")) { ciphers.add(cipher); } }; socket.setEnabledCipherSuites(ciphers.toArray(new String[ciphers.size()])); return socket; } }; ((HttpsURLConnection) connection).setSSLSocketFactory(wrappingSocketFactory); {code} I dont know yet why #getSupportedCipherSuites is never called in my current testing (my initial idea was to have them returning all but the _DHE_ ciphers from the wrapped socket factory) > 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] (JBDS-3141) Test victi.ms maven plugin works within jbds (or at least does not fail)

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3141?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3141: ------------------------------------ So - it seems to work as well as it works from the CLI. > Test victi.ms maven plugin works within jbds (or at least does not fail) > ------------------------------------------------------------------------ > > Key: JBDS-3141 > URL: https://issues.jboss.org/browse/JBDS-3141 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: maven > Reporter: Burr Sutter > Assignee: Len DiMaggio > Fix For: 8.0.0.CR2 > > > http://victi.ms has a maven plugin to check/assert maven dependencies have issues. > should check how it works and if it works within eclipse -- 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