[JBoss JIRA] (JBIDE-22076) Application pod is not visible after build is completed
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22076?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22076:
----------------------------------
Description: When I create a new application on OpenShift from template, e.g. eap template, there is a running build pod. Once this build pod finish successfully, there is spinned up an application pod but it is not visible in OpenShift Explorer automatically. Refresh of a project is necessary. (was: When I create a new application on OpenShift from template, e.g. eap template, there is a running build pod. Once this build pod finish successfully, there is spinned up an application pod but it is not visible in OpenShift Explorer automatically. Refresh of project is necessary. )
> Application pod is not visible after build is completed
> -------------------------------------------------------
>
> Key: JBIDE-22076
> URL: https://issues.jboss.org/browse/JBIDE-22076
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3
>
> When I create a new application on OpenShift from template, e.g. eap template, there is a running build pod. Once this build pod finish successfully, there is spinned up an application pod but it is not visible in OpenShift Explorer automatically. Refresh of a project is necessary.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22075:
----------------------------------
Workaround Description: Stop port forwarding, start it again and use port from port forwarding for debugging.
Workaround: Workaround Exists
> Cannot debug OpenShift application
> ----------------------------------
>
> Key: JBIDE-22075
> URL: https://issues.jboss.org/browse/JBIDE-22075
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3
>
> When I am trying to run remote debugging of an application on OpenShift I get following error
> {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}
> I guess this is something related to port forwarding. Even the port for debugging is forwarded on a free port and it looks like started, it fails. When I stop port forwarding, start it again and use a port, which is used as a forwarded port for remote debug port, in debug configuration, it works.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22075:
-------------------------------------
Summary: Cannot debug OpenShift application
Key: JBIDE-22075
URL: https://issues.jboss.org/browse/JBIDE-22075
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Priority: Critical
When I am trying to run remote debugging of an application on OpenShift I get following error
{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}
I guess this is something related to port forwarding. Even the port for debugging is forwarded on a free port and it looks like started, it fails. When I stop port forwarding, start it again and use a port, which is used as a forwarded port for remote debug port, in debug configuration, it works.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22075:
----------------------------------
Labels: openshift_v3 (was: )
> Cannot debug OpenShift application
> ----------------------------------
>
> Key: JBIDE-22075
> URL: https://issues.jboss.org/browse/JBIDE-22075
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3
>
> When I am trying to run remote debugging of an application on OpenShift I get following error
> {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}
> I guess this is something related to port forwarding. Even the port for debugging is forwarded on a free port and it looks like started, it fails. When I stop port forwarding, start it again and use a port, which is used as a forwarded port for remote debug port, in debug configuration, it works.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22058) Allow termination of remote VM in debug configuration for OpenShift app should be checked by default
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22058?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22058:
---------------------------------------
Slava is right. I should provided more detailed description. This is meant to allow go back from debug mode to normal mode. If termination of remote VM is not necessary for it, I am ok with rejecting this issue.
> Allow termination of remote VM in debug configuration for OpenShift app should be checked by default
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22058
> URL: https://issues.jboss.org/browse/JBIDE-22058
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> The checkbox "Allow termination of remove VM" in debug configuration, which is automatically created and port of forwarder debugging port from pod is set there should be by default enabled to allow user just simply click debug workbench tool item to debug OpenShift application and then when user decides to stop debugging to be able to do that easily.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22041) Exception is thrown when I do not want to open cheatsheet
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22041?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-22041:
---------------------------------------------
should this not be fixed in 4.3 too ?
> Exception is thrown when I do not want to open cheatsheet
> ---------------------------------------------------------
>
> Key: JBIDE-22041
> URL: https://issues.jboss.org/browse/JBIDE-22041
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.1.CR1
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
> Fix For: 4.4.0.Alpha1
>
>
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.OperationCanceledException)
> at org.eclipse.swt.SWT.error(SWT.java:4491)
> at org.eclipse.swt.SWT.error(SWT.java:4406)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3794)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3433)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Caused by: org.eclipse.core.runtime.OperationCanceledException
> at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil.promptToShowCheatsheets(CheatSheetUtil.java:434)
> at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil.access$1(CheatSheetUtil.java:394)
> at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil$1.run(CheatSheetUtil.java:378)
> at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162)
> at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22058) Allow termination of remote VM in debug configuration for OpenShift app should be checked by default
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22058?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22058:
----------------------------------
Description: The checkbox "Allow termination of remove VM" in debug configuration, which is automatically created and port of forwarder debugging port from pod is set there should be by default enabled to allow user just simply click debug workbench tool item to debug OpenShift application and then when user decides to stop debugging to be able to do that easily. (was: The checkbox "Allow termination of remove VM" in debug configuration, which is automatically created and port of forwarder debugging port from pod is set there should be by default enabled to allow user just simply click debug workbench tool item to debug OpenShift application.)
> Allow termination of remote VM in debug configuration for OpenShift app should be checked by default
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22058
> URL: https://issues.jboss.org/browse/JBIDE-22058
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> The checkbox "Allow termination of remove VM" in debug configuration, which is automatically created and port of forwarder debugging port from pod is set there should be by default enabled to allow user just simply click debug workbench tool item to debug OpenShift application and then when user decides to stop debugging to be able to do that easily.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21977) Unexpected JAX-RS validation error for client filters
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21977?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-21977.
-------------------------------
Verified with 4.3.1.CR1a.
> Unexpected JAX-RS validation error for client filters
> -----------------------------------------------------
>
> Key: JBIDE-21977
> URL: https://issues.jboss.org/browse/JBIDE-21977
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs, respin-a
> Fix For: 4.3.1.CR1
>
>
> We are using JAX-RS client filters in our project. One of the classes looks like this:
> ...
> import java.io.IOException;
> import javax.ws.rs.client.ClientRequestContext;
> import javax.ws.rs.client.ClientRequestFilter;
> import javax.ws.rs.ext.Provider;
> ...
> @Provider
> public class ClientFilter implements ClientRequestFilter
> {
> ...
> }
> The class is part of a Dynamic Web Project with JAX-RS support turned on.
> The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error:
> The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver.
> I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years