[JBoss JIRA] (JBIDE-22114) Server Wizard ignores selected project
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-22114:
-----------------------------------
Summary: Server Wizard ignores selected project
Key: JBIDE-22114
URL: https://issues.jboss.org/browse/JBIDE-22114
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Fred Bricon
Priority: Blocker
Say you have 2 webapp projects in the workspace.
When you create an openshift server adapter, a default project is selected, if you switch to another project,
the source path is not updated. Even if you set the source path manually, the selected project is ignored when creating the project (as seen in the server editor)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22111) OpenShift logging is too chatty on stdout
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22111?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22111:
------------------------------------------
[~ldimaggio] All this chatty client output should and is put to the tracing facility. The problem is that the log4j properties also had stdout and not only the Eclipse log appender that we have (which redirects client messages to the tracing facility)
> OpenShift logging is too chatty on stdout
> -----------------------------------------
>
> Key: JBIDE-22111
> URL: https://issues.jboss.org/browse/JBIDE-22111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.CR1
>
>
> In stdout (e.g. when running IDE from command line) there is a lot of [DEBUG] messages from OpenShift. Most of them are WatchClient related, websockets, some jsons. It is too much chatty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22111) OpenShift logging is too chatty on stdout
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22111?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-22111:
--------------------------------------
Can we pipe this information someplace - log file? - instead of droping it?
It can be useful in debugging problems:
{code}
[DEBUG] 2016-04-05 12:10:03,731 com.openshift.internal.restclient.URLBuilder - Built url: https://console.qe.openshift.com/oapi/v1/projectrequests
[DEBUG] 2016-04-05 12:10:03,731 com.openshift.internal.restclient.http.UrlConnectionHttpClient - Request Properties: {Accept=[application/json], Content-Type=[application/json]}
[DEBUG] 2016-04-05 12:10:03,731 com.openshift.internal.restclient.http.UrlConnectionHttpClient - Request Method: POST
[DEBUG] 2016-04-05 12:10:03,731 com.openshift.internal.restclient.http.UrlConnectionHttpClient - {
"apiVersion" : "v1",
"kind" : "ProjectRequest",
"metadata" : {"name" : "april5project"},
"description" : "april5project",
"displayName" : "april5project"
}
[DEBUG] 2016-04-05 12:10:04,628 com.openshift.internal.restclient.DefaultClient - {"kind":"Project","apiVersion":"v1","metadata":{"name":"april5project","selfLink":"/oapi/v1/projectrequests/april5project","uid":"db42daf6-fb48-11e5-9e72-1278fc6659bb","resourceVersion":"29862572","creationTimestamp":"2016-04-05T16:10:03Z","annotations":{"openshift.io/description":"april5project","openshift.io/display-name":"april5project","openshift.io/sa.scc.mcs":"s0:c302,c24","openshift.io/sa.scc.supplemental-groups":"1090950000/10000","openshift.io/sa.scc.uid-range":"1090950000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Active"}}
[DEBUG] 2016-04-05 12:10:04,629 com.openshift.internal.restclient.URLBuilder - Built url: https://console.qe.openshift.com/oapi/v1/projects/april5project
[DEBUG] 2016-04-05 12:10:04,745 com.openshift.internal.restclient.DefaultClient - {"kind":"Project","apiVersion":"v1","metadata":{"name":"april5project","selfLink":"/oapi/v1/projects/april5project","uid":"db42daf6-fb48-11e5-9e72-1278fc6659bb","resourceVersion":"29862572","creationTimestamp":"2016-04-05T16:10:03Z","annotations":{"openshift.io/description":"april5project","openshift.io/display-name":"april5project","openshift.io/sa.scc.mcs":"s0:c302,c24","openshift.io/sa.scc.supplemental-groups":"1090950000/10000","openshift.io/sa.scc.uid-range":"1090950000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Active"}}
{code}
> OpenShift logging is too chatty on stdout
> -----------------------------------------
>
> Key: JBIDE-22111
> URL: https://issues.jboss.org/browse/JBIDE-22111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.CR1
>
>
> In stdout (e.g. when running IDE from command line) there is a lot of [DEBUG] messages from OpenShift. Most of them are WatchClient related, websockets, some jsons. It is too much chatty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22113) CDK shutdown always goes to Forcing shutdown of VM on Windows
by Martin Malina (JIRA)
Martin Malina created JBIDE-22113:
-------------------------------------
Summary: CDK shutdown always goes to Forcing shutdown of VM on Windows
Key: JBIDE-22113
URL: https://issues.jboss.org/browse/JBIDE-22113
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdk
Affects Versions: 4.3.1.CR1
Reporter: Martin Malina
Assignee: Rob Stryker
On OS X, when I stop CDK in JBDS, I get this in the console:
==> default: Unregistering box with vagrant-registration...
==> default: Attempting graceful shutdown of VM...
And a few seconds later, the server adapter shows "Stopped".
Today while testing on Windows I noticed that it behaves differently.
It first displays these two lines, but it keeps "Stopping". And eventually there is another line in the console which says:
==> default: Forcing shutdown of VM...
After this, the server adapter shows "Stopped".
So for some unknown reason, on Windows the graceful shutdown fails to work.
This is JBDS+CDK installed from the latest windows installer (built April 4th).
It would be good to see if others see this on Windows as well or not.
Interestingly, when I just tried "vagrant halt" from cygwin instead of in JBDS, it stops normally - graceful shutdown.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22075:
-------------------------------------
Description:
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.
was:
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.
> Cannot debug OpenShift application
> ----------------------------------
>
> 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: Fred Bricon
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, 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
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22075:
-------------------------------------
Description:
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.
was:
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
{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}
> Cannot debug OpenShift application
> ----------------------------------
>
> 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: Fred Bricon
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, 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
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22075:
-------------------------------------
Issue Type: Enhancement (was: Bug)
Description:
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
{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}
was:
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.
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.
!error-in-launching-remote-debugger.png!
EXPECTED RESULT: The error should tell you that there already is an entry that's running.
was:
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.
EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging.
RESULT: Error is shown.
!error-in-launching-remote-debugger.png!
EXPECTED RESULT: Debugger works.
> Cannot debug OpenShift application
> ----------------------------------
>
> 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: Fred Bricon
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, 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
> {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}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years