[JBoss JIRA] (JBIDE-22066) Stopping debugging of OpenShift application should get application back to normal state.
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22066:
-------------------------------------
Summary: 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
This is follow up on JBIDE-21699. 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
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21699) Enable debug mode on deployment config
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21699?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21699.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin build B260.
> Enable debug mode on deployment config
> --------------------------------------
>
> Key: JBIDE-21699
> URL: https://issues.jboss.org/browse/JBIDE-21699
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.3.1.CR1
>
> Attachments: Screenshot 2016-03-25 12.07.45.png
>
>
> When clicking on the Debug button of the server adapter, the Debug variables should be set, if necessary.
> The remote debug port could be read from server adapter preferences, default to 8787
> {code}
> {
> "name" : "debug",
> "containerPort" : 8787,
> "protocol" : "TCP"
> }
> {code}
> * and to spec.containers.env:
> {code}
> {
> "name" : "DEBUG",
> "value" : "true"
> },
> {
> "name" : "DEBUG_PORT",
> "value" : "8787"
> }
> {code}
> If the remote debug port was already set (possibly to another value), then it should be returned
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21351) Error during "Update Maven projects configuration"
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21351?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-21351:
------------------------------------
Yep:
{noformat:title=An internal error occurred during: "Update Maven projects configuration".}
java.lang.IllegalStateException: Cannot add projects when processing is started
at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$CumulativeMappingDiscoveryJob.addProjects(MavenProjectConfigurator.java:97)
at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$UpdateMavenConfigurationJob.run(MavenProjectConfigurator.java:161)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{noformat}
> Error during "Update Maven projects configuration"
> --------------------------------------------------
>
> Key: JBIDE-21351
> URL: https://issues.jboss.org/browse/JBIDE-21351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Affects Versions: 4.3.1.Beta1
> Reporter: Radim Hopp
> Assignee: Mickael Istria
> Fix For: 4.3.1.CR1
>
>
> Sometimes I get
> {noformat}
> An internal error occurred during: "Update Maven projects configuration".
> Cannot add projects when processing is started{noformat}
> when I'm importing maven project using easymport.
> Full stacktrace:
> {noformat}
> java.lang.IllegalStateException: Cannot add projects when processing is started
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$CumulativeMappingDiscoveryJob.addProjects(MavenProjectConfigurator.java:97)
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$UpdateMavenConfigurationJob.run(MavenProjectConfigurator.java:161)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21982) OpenShift Websocket reconnects on timeout, even when the OpenShift connection is deleted
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21982?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21982:
---------------------------------------
This might require you to observe behavior before and after the change to confirm.
# Expand a connection and project
# Note the logs display traffic
# Delete the connection
# Wait the amount of time for a watch to usually drop and reconnect
# Note the logs indicate the watch is trying to reconnect.
After the change, nothing should appear in the logs for the last few steps and you should have seen a log message upon connection deletion that the watch stopped.
> OpenShift Websocket reconnects on timeout, even when the OpenShift connection is deleted
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-21982
> URL: https://issues.jboss.org/browse/JBIDE-21982
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.3.1.CR1
>
>
> OpenShift Websocket reconnects on timeout, even when the OpenShift connection is deleted
> Is shows in the logs, when running the openshift plugin from source
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21986) Error when opening the "Deploy Docker Image" wizard if no valid Docker connection exists
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21986?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21986.
---------------------------------
Closing as out of dated.
> Error when opening the "Deploy Docker Image" wizard if no valid Docker connection exists
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-21986
> URL: https://issues.jboss.org/browse/JBIDE-21986
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> When opening the {{Deploy Docker Image}} wizard, I got an error as below:
> {code}
> !ENTRY org.eclipse.core.databinding.observable 4 2 2016-03-29 10:52:05.197
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.databinding.observable".
> !STACK 0
> java.lang.RuntimeException: java.lang.NullPointerException
> at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.readProperty(BeanPropertyHelper.java:102)
> at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doGetValue(BeanValueProperty.java:49)
> at org.eclipse.core.databinding.property.value.ValueProperty.getValue(ValueProperty.java:58)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$2.run(SimplePropertyObservableValue.java:84)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.firstListenerAdded(SimplePropertyObservableValue.java:81)
> at org.eclipse.core.databinding.observable.ChangeManager.addListener(ChangeManager.java:70)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.addValueChangeListener(AbstractObservableValue.java:47)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.firstListenerAdded(DecoratingObservableValue.java:76)
> at org.eclipse.core.databinding.observable.ChangeManager.addListener(ChangeManager.java:70)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.addValueChangeListener(DecoratingObservableValue.java:45)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.firstListenerAdded(DecoratingObservableValue.java:76)
> at org.eclipse.core.databinding.observable.ChangeManager.addListener(ChangeManager.java:70)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.addValueChangeListener(DecoratingObservableValue.java:45)
> at org.eclipse.core.databinding.ValueBinding.<init>(ValueBinding.java:81)
> at org.eclipse.core.databinding.DataBindingContext.bindValue(DataBindingContext.java:164)
> at org.jboss.tools.common.ui.databinding.ValueBindingBuilder.bind(ValueBindingBuilder.java:36)
> at org.jboss.tools.common.ui.databinding.ValueBindingBuilder.access$0(ValueBindingBuilder.java:34)
> at org.jboss.tools.common.ui.databinding.ValueBindingBuilder$ModelDefinition.in(ValueBindingBuilder.java:69)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage.createDockerConnectionControl(DeployImagePage.java:226)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage.doCreateControls(DeployImagePage.java:158)
> at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage.createControl(AbstractOpenShiftWizardPage.java:70)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.jboss.tools.common.ui.WizardUtils.createWizardDialog(WizardUtils.java:262)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:255)
> at org.jboss.tools.openshift.internal.ui.handler.DeployImageHandler.execute(DeployImageHandler.java:58)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> 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: java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.setDockerConnection(DeployImageWizardModel.java:465)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.getDockerConnection(DeployImageWizardModel.java:116)
> 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.core.internal.databinding.beans.BeanPropertyHelper.readProperty(BeanPropertyHelper.java:96)
> ... 80 more
> {code}
> I had a single Docker connection, but it was not reachable:
> {code}
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:244)
> at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
> ... 29 more
> {code}
> so the list of images could not be retrieved.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21972) Improve initialization of Configure Service Ports dialog
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21972?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21972.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin build B260.
> Improve initialization of Configure Service Ports dialog
> --------------------------------------------------------
>
> Key: JBIDE-21972
> URL: https://issues.jboss.org/browse/JBIDE-21972
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> When "Add..." is run on page 'Services & Routing Settings, if list of service ports is not empty, dialog is pre-filled with integers. Some errors should be fixed:
> Case #1
> # ASSERT: have a project in OpenShift
> # EXEC: in Explorer: choose "Deploy Docker Image..." in context menu of your project
> # EXEC: in deploy docker image wizard: pick an image (ex. php),
> # EXEC: confirm the 2nd wizard page ("Deployment Configuration & Scalability") and get to the 3rd wizard page
> # ASSERT: no ports are defined yet
> # EXEC: Create service port=65535, pod port=2000
> # EXEC: Run "Add..." second time.
> Result:
> Service port is filled with 65535 and causes error message.
> Pod port is filled with 65536 also causing error.
> Case #2
> # ASSERT: no ports are defined yet.
> # EXEC: Create service port=2000, pod port=2001
> # EXEC: Run "Add..." second time.
> Result:
> Service port is filled with 2001 - it is ok.
> Pod port is filled with 2001 causing error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20998) Application wizard: Validation error description in Resource Labels page is cut off
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20998?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-20998.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin build B260.
> Application wizard: Validation error description in Resource Labels page is cut off
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-20998
> URL: https://issues.jboss.org/browse/JBIDE-20998
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Final
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: resource_label_complete.png, resource_label_incomplete.png
>
>
> In Resource Label dialog there is a validation error description about correct format of a label. But the validation error description is cut off. On first sight it does not look like like cut off, but after resizing a shell more text is showed. See following image of cut off description:
> !resource_label_incomplete.png!
> And following image contains full description after resizing to "long enough" width:
> !resource_label_complete.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22065) Application wizard: Validation error description in Resource Labels page is cut off
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22065?page=com.atlassian.jira.plugi... ]
Marián Labuda resolved JBIDE-22065.
-----------------------------------
Resolution: Done
> Application wizard: Validation error description in Resource Labels page is cut off
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-22065
> URL: https://issues.jboss.org/browse/JBIDE-22065
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Final
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: resource_label_complete.png, resource_label_incomplete.png
>
>
> In Resource Label dialog there is a validation error description about correct format of a label. But the validation error description is cut off. On first sight it does not look like like cut off, but after resizing a shell more text is showed. See following image of cut off description:
> !resource_label_incomplete.png!
> And following image contains full description after resizing to "long enough" width:
> !resource_label_complete.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20998) Application wizard: Validation error description in Resource Labels page is cut off
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20998?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-20998:
----------------------------------
Fix Version/s: (was: 4.4.0.Alpha1)
> Application wizard: Validation error description in Resource Labels page is cut off
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-20998
> URL: https://issues.jboss.org/browse/JBIDE-20998
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Final
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: resource_label_complete.png, resource_label_incomplete.png
>
>
> In Resource Label dialog there is a validation error description about correct format of a label. But the validation error description is cut off. On first sight it does not look like like cut off, but after resizing a shell more text is showed. See following image of cut off description:
> !resource_label_incomplete.png!
> And following image contains full description after resizing to "long enough" width:
> !resource_label_complete.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years