April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22066) Server adapter: Stopping debugging of OpenShift application should get application back to normal state.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22066?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22066: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.AM3) > Server adapter: Stopping debugging of OpenShift application should get application back to normal state. > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22066 > URL: https://issues.jboss.org/browse/JBIDE-22066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM1 > > > When user stop or delete Server Adapter where debugging has been enabled, application should be able to get back to normal state - remove environment variable for debugging and remove ports for debugging from deployment config. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22175) Warnings in JBDS after importing kitchensink-jsp quickstart

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22175?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22175: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.0.Final) (was: 4.4.4.AM3) > Warnings in JBDS after importing kitchensink-jsp quickstart > ----------------------------------------------------------- > > Key: JBIDE-22175 > URL: https://issues.jboss.org/browse/JBIDE-22175 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, upstream > Reporter: Sande Gilda > Assignee: Victor Rubezhny > Fix For: 4.4.4.Final > > > After importing the quickstart into JBDS, the following warnings are produced > * The tag handler class for "c:forEach" (org.apache.taglibs.standard.tag.rt.core.ForEachTag) was not found on the Java Build Path > * The tag handler class for "c:out" (org.apache.taglibs.standard.tag.rt.core.OutTag) was not found on the Java Build Path -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24306) Cannot connect to JMX through OpenShift Server adapter to a FIS project

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24306?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24306: ----------------------------------------- [~jeffmaury] I am on Red Hat JBoss Developer Studio Version: 10.4.0.AM3 Build id: AM3-v20170406-1058-B390 Build date: 20170406-1058 10.3.GA is based on 4.4.3, right? I can't test with it, it wasn't possible to create Server adapters for FIS stuff > Cannot connect to JMX through OpenShift Server adapter to a FIS project > ----------------------------------------------------------------------- > > Key: JBIDE-24306 > URL: https://issues.jboss.org/browse/JBIDE-24306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Aurélien Pupier > Attachments: image-2017-04-25-14-48-51-427.png, screenshot-1.png > > > !image-2017-04-25-14-48-51-427.png|thumbnail! > in log: > {noformat} > eclipse.buildId=10.4.0.AM3-v20170406-1058-B390 > java.version=1.8.0_112 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/C:/ws-devsuite-1.4.0-170425/ -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.jmx.core > Error > Tue Apr 25 14:47:14 CEST 2017 > An error occurred while opening the connection. > java.io.IOException: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324) > at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:80) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage > at org.jolokia.client.J4pClient.mapException(J4pClient.java:333) > at org.jolokia.client.J4pClient.execute(J4pClient.java:198) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311) > ... 5 more > Caused by: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage > at org.apache.http.impl.client.CloseableHttpClient.determineTarget(CloseableHttpClient.java:94) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55) > at org.jolokia.client.J4pClient.execute(J4pClient.java:190) > ... 8 more > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22075: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Confusing error message when trying to attach remote debugger to OS app run in debug mode > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22075 > URL: https://issues.jboss.org/browse/JBIDE-22075 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: debugging, openshift_v3 > Fix For: 4.4.4.Final > > Attachments: debug-button-toolbar.png, error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, launch-debug-no-error.mov, remote-debugger-already-launched.png > > > If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically. > If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message > When I am trying to run remote debugging of an application on OpenShift I get following error > !!error-in-launching-remote-debugger.png! ! > {code} > Failed to connect to remote VM > com.sun.jdi.connect.spi.ClosedConnectionException > at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222) > at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214) > at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185) > at java.lang.Thread.run(Thread.java:745) > {code} > *Steps to reproduce:* > ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace. > EXEC: Select "Restart in Debug" in context menu of server adapter. > ASSERT: Server adapter is in state debugging ("[Debugging, Started]"). > EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging. > RESULT: Error is shown. > EXPECTED RESULT: The error message should tell you that there already is an instance running. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24312) Explorer: SSL certificate dialog shows up many many times when using internal test server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24312?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24312: --------------------------------------- [~jeffmaury], thanks, I didn't notice your comment, so I simply changed my comment once I learnt that I needed to complete the sign up process first. > Explorer: SSL certificate dialog shows up many many times when using internal test server > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24312 > URL: https://issues.jboss.org/browse/JBIDE-24312 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Environment: MacOS > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.4.4.Final > > Attachments: Screencast_04-25-2017_06-56-06+PM.webm, create connection paas.mp4, diff-in-serial.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24312) Explorer: SSL certificate dialog shows up many many times when using internal test server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24312?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-24312 at 4/26/17 4:46 AM: ---------------------------------------------------------------- At first I couldn't connect at all because I needed to accept the ToC, I didn't know about that. Now I can reproduce this. For me, when I expanded my newly created project, it took 23 confirmations of ssl certificate. And while I'm writing this, I noticed that a new dialog showed up and now I confirmed 8 more of them and there are more. In my project, I can see glusterfs-cluster show up. was (Author: mmalina): I tried this now and this is the first cert I get: {code} Issued By: Country (C): US State (ST): North Carolina Serial Number: 52616C65696768Organization (O): Red Hat, Inc. Organizational Unit (OU): Information Technology Common Name (CN): open.paas.redhat.com Serial Number: 5B424065666530643234 Validity: Issued On: Thu, 27 Oct 2016 13:11:06 Expires On: Sat, 27 Oct 2018 13:11:06 SHA1 Fingerprint: 1334F5B02AECA76B07E38B749311C46C92E351BD {code} This is the second: {code} Issued By: Country (C): US State (ST): North Carolina Serial Number: 52616C65696768Organization (O): Red Hat, Inc. Organizational Unit (OU): Information Technology Common Name (CN): open.paas.redhat.com Serial Number: 5B42403563616230396164 Validity: Issued On: Thu, 27 Oct 2016 13:11:06 Expires On: Sat, 27 Oct 2018 13:11:06 SHA1 Fingerprint: 1334F5B02AECA76B07E38B749311C46C92E351BD {code} And then I get: Unauthorized to access resource. You can access the server using Basic authentication. So I cannot Finish the new connection wizard. Do I need to ask for an account or something? > Explorer: SSL certificate dialog shows up many many times when using internal test server > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24312 > URL: https://issues.jboss.org/browse/JBIDE-24312 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Environment: MacOS > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.4.4.Final > > Attachments: Screencast_04-25-2017_06-56-06+PM.webm, create connection paas.mp4, diff-in-serial.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23711) Properites: "Edit default route" on Build config does nothing

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23711?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23711: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Properites: "Edit default route" on Build config does nothing > ------------------------------------------------------------- > > Key: JBIDE-23711 > URL: https://issues.jboss.org/browse/JBIDE-23711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Labels: openshift_v3, properties > Fix For: 4.4.4.Final > > > Context menu of build configs in properties view has entry "Edit default route..." which does nothing. Is it even supposed to be there? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23814) Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23814?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23814: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error > ----------------------------------------------------------------- > > Key: JBIDE-23814 > URL: https://issues.jboss.org/browse/JBIDE-23814 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: Red Hat JBoss Developer Studio > Version: 10.2.0.GA > Build id: GA-v20161125-1418-B55 > Build date: 20161125-1418 > JBoss Openshift UI Plugin > Version: 3.3.1.v20161125-0956 > OpenShift > openshift v3.3.1.3 > Reporter: Siamak Sadeghianfar > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.4.Final > > Attachments: jbds-error.png, jboss-eap70-openshift.png > > > When adding a Server Adapter for an JBoss EAP 7 based deployments on OpenShift, operation fails with this error: > {{Could not sync /private/tmp/workspace-demo/.metadata/.plugins/org.jboss.ide.eclipse.as.core/inventory-dev-ssadeghi@inventory/deploy to all pods running the service inventory > OpenShiftBinaryCapability process exited: error: auth info "ssadeghi-redhat.com" does not exist}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23900) Refactor OpenShift server adapter to isolate EAP/Wildfly and NodeJS specific stuff

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23900?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23900: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Refactor OpenShift server adapter to isolate EAP/Wildfly and NodeJS specific stuff > ---------------------------------------------------------------------------------- > > Key: JBIDE-23900 > URL: https://issues.jboss.org/browse/JBIDE-23900 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > > We should isolate EAP/Wildfly and NodeJS specific stuff for the server adapter into separate classes / extensions > We should also provide a mechanism for the sever adapter to be stack agnostic so that we can add more stacks by just addding an extension > This will be probably required by FUSE integration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24111) Verify EAP 7.1 compatibility from EAP team

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24111?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24111: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.AM3) > Verify EAP 7.1 compatibility from EAP team > ------------------------------------------ > > Key: JBIDE-24111 > URL: https://issues.jboss.org/browse/JBIDE-24111 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.4.AM1 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: eap, server > Fix For: 4.5.0.AM1 > > > We should check the problems got from the EAP team. See linked issues -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 April 2017