[JBoss JIRA] (JBIDE-21746) Too much info shown in log when deploying a docker image to OpenShift
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21746?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21746:
---------------------------------------
I don't recall how we enabled logging, but I agree it probably makes more sense to tie it to the TRACE messaging so people can enable or disable to their hart's content.
> Too much info shown in log when deploying a docker image to OpenShift
> ---------------------------------------------------------------------
>
> Key: JBIDE-21746
> URL: https://issues.jboss.org/browse/JBIDE-21746
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> When deploying a docker image to OpenShift 3 server, there is too much logging in eclipse .log (in error log with severity info). For every created resource there is a message "Trying to create resource:" followed up by json of a resource. So for a deployed docker image it creates such info message for a new image stream, service, routing (if was checked) and deployment config.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-22128:
---------------------------------------
You will receive a 403 regardless is the project exists or not. As [~fbricon] surmised, 401 and 404 is not returned for security reasons.
> Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22128
> URL: https://issues.jboss.org/browse/JBIDE-22128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Fred Bricon
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> I have a Java project with an "openshift" maven profile that creates a ROOT.war
> When I create a "Server Adapter", the openshift plugins deploys the name of the project.war
> The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22153) Closing log of a pod throws an exception
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22153?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22153:
----------------------------------
Labels: openshift_v3 (was: )
> Closing log of a pod throws an exception
> ----------------------------------------
>
> Key: JBIDE-22153
> URL: https://issues.jboss.org/browse/JBIDE-22153
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3
>
> When I am trying to close log of a pod (build pod or application pod, does not matter which one) by clicking on gray view tool item Close, I get following exception
> {code}
> Exception reading pod log inputstream
> java.io.IOException: Stream closed
> at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:336)
> at java.io.SequenceInputStream.read(SequenceInputStream.java:207)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:284)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> at java.io.FilterInputStream.read(FilterInputStream.java:107)
> at org.jboss.tools.openshift.internal.ui.job.PodLogsJob$ConsoleStreamPipe.runOCBinary(PodLogsJob.java:166)
> at org.jboss.tools.openshift.internal.core.OCBinaryOperation.run(OCBinaryOperation.java:34)
> at org.jboss.tools.openshift.internal.ui.job.PodLogsJob$ConsoleStreamPipe.run(PodLogsJob.java:153)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21673) JBoss Runtime Detection preference page throws StackOverflowError
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21673?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-21673.
------------------------------
Verified in JBDS 9.1.0.GA-v20160410-1849-B495. Closing.
> JBoss Runtime Detection preference page throws StackOverflowError
> -----------------------------------------------------------------
>
> Key: JBIDE-21673
> URL: https://issues.jboss.org/browse/JBIDE-21673
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, runtime-detection
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> 1. Start Eclipse.
> 2. Open Preferences.
> 3. Select JBoss Runtime Detection.
> Exception:
> {code}
> !ENTRY org.eclipse.ui 4 0 2016-02-10 19:18:24.266
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.StackOverflowError)
> at org.eclipse.swt.SWT.error(SWT.java:4503)
> at org.eclipse.swt.SWT.error(SWT.java:4418)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211)
> at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:564)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:396)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4482)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3820)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3431)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1132)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1023)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:651)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:595)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
> Caused by: java.lang.StackOverflowError
> at org.eclipse.swt.internal.gtk.OS._gtk_widget_size_allocate(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_widget_size_allocate(OS.java:14919)
> ----infinitle repeated part begin----
> at org.eclipse.swt.custom.TableEditor$1.controlMoved(TableEditor.java:95)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:224)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4482)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1334)
> at org.eclipse.swt.widgets.TableColumn.gtk_size_allocate(TableColumn.java:395)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1991)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4718)
> at org.eclipse.swt.internal.gtk.OS._gtk_widget_size_allocate(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_widget_size_allocate(OS.java:14919)
> at org.eclipse.swt.widgets.Control.forceResize(Control.java:780)
> at org.eclipse.swt.widgets.Table.getClientArea(Table.java:1154)
> at org.eclipse.swt.custom.TableEditor.computeBounds(TableEditor.java:120)
> at org.eclipse.swt.custom.ControlEditor.layout(ControlEditor.java:223)
> at org.eclipse.swt.custom.TableEditor.layout(TableEditor.java:265)
> at org.eclipse.swt.custom.TableEditor$1.controlMoved(TableEditor.java:95)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:224)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4482)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1334)
> at org.eclipse.swt.widgets.TableColumn.gtk_size_allocate(TableColumn.java:395)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1991)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4718)
> at org.eclipse.swt.internal.gtk.OS._gtk_widget_size_allocate(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_widget_size_allocate(OS.java:14919)
> at org.eclipse.swt.widgets.Control.forceResize(Control.java:780)
> at org.eclipse.swt.widgets.Table.getClientArea(Table.java:1154)
> at org.eclipse.swt.custom.TableEditor.computeBounds(TableEditor.java:120)
> at org.eclipse.swt.custom.ControlEditor.layout(ControlEditor.java:223)
> at org.eclipse.swt.custom.TableEditor.layout(TableEditor.java:265)
> ----infinitle repeated part end----
> at org.eclipse.swt.custom.ControlEditor.setEditor(ControlEditor.java:251)
> at org.eclipse.swt.custom.TableEditor.setEditor(TableEditor.java:240)
> at org.eclipse.swt.custom.TableEditor.setEditor(TableEditor.java:256)
> at org.jboss.tools.runtime.ui.internal.preferences.RuntimePreferencePage.createDetectorViewer(RuntimePreferencePage.java:208)
> at org.jboss.tools.runtime.ui.internal.preferences.RuntimePreferencePage.createContents(RuntimePreferencePage.java:140)
> at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241)
> at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1429)
> at org.eclipse.jface.preference.PreferenceDialog$9.run(PreferenceDialog.java:1196)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1188)
> at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:608)
> at org.eclipse.jface.preference.PreferenceDialog$5.lambda$0(PreferenceDialog.java:655)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.preference.PreferenceDialog$5.selectionChanged(PreferenceDialog.java:652)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:876)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:873)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1242)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1268)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1.lambda$1(OpenStrategy.java:431)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 36 more
> {code}
> 4. Select another preference page.
> 5. Again try to select JBoss Runtime Detection.
> Now, it opens successfully.
> 6. Try to adjust split between the tree of pages and the page.
> Preferences dialog window starts uncontrollably expand until it fills the entire screen width.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22152:
----------------------------------
Steps to Reproduce:
ASSERT: Have an OS3 connection with an application and Eclipse project.
EXEC: Create a server adapter for Eclipse project and the application on OpenShift.
ASSERT: There is a launch in Debug view with label of OS3 server adapter.
EXEC: Delete the OS3 server adapter from Servers view.
RESULT: There is an unknown launch in Debug view.
EXPECTED RESULT: Launch in Debug view is removed as well.
was:
ASSERT: Have a OS3 connection with an application and Eclipse project.
EXEC: Create a server adapter for Eclipse project and the application on OpenShift.
ASSERT: There is a launch in Debug view with label of OS3 server adapter.
EXEC: Delete the OS3 server adapter from Servers view.
RESULT: There is an unknown launch in Debug view.
EXPECTED RESULT: Launch in Debug view is removed as well.
> Unknown launch is left in Debug view after deletion of an OS 3 server adapter
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22152
> URL: https://issues.jboss.org/browse/JBIDE-22152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Attachments: launches.png
>
>
> When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
> !launches.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22152:
----------------------------------
Description:
When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
!launches.png!
was:
When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on a OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
!launches.png!
> Unknown launch is left in Debug view after deletion of an OS 3 server adapter
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22152
> URL: https://issues.jboss.org/browse/JBIDE-22152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Attachments: launches.png
>
>
> When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
> !launches.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22153) Closing log of a pod throws an exception
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22153:
-------------------------------------
Summary: Closing log of a pod throws an exception
Key: JBIDE-22153
URL: https://issues.jboss.org/browse/JBIDE-22153
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
When I am trying to close log of a pod (build pod or application pod, does not matter which one) by clicking on gray view tool item Close, I get following exception
{code}
Exception reading pod log inputstream
java.io.IOException: Stream closed
at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
at java.io.BufferedInputStream.read(BufferedInputStream.java:336)
at java.io.SequenceInputStream.read(SequenceInputStream.java:207)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:284)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
at java.io.FilterInputStream.read(FilterInputStream.java:107)
at org.jboss.tools.openshift.internal.ui.job.PodLogsJob$ConsoleStreamPipe.runOCBinary(PodLogsJob.java:166)
at org.jboss.tools.openshift.internal.core.OCBinaryOperation.run(OCBinaryOperation.java:34)
at org.jboss.tools.openshift.internal.ui.job.PodLogsJob$ConsoleStreamPipe.run(PodLogsJob.java:153)
at java.lang.Thread.run(Thread.java:745)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-656) Create import DDL test
by Matej Kralik (JIRA)
Matej Kralik created JBTIS-656:
----------------------------------
Summary: Create import DDL test
Key: JBTIS-656
URL: https://issues.jboss.org/browse/JBTIS-656
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: QE, teiid
Affects Versions: 4.3.0.Beta1
Reporter: Matej Kralik
Assignee: Matej Kralik
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22152:
-------------------------------------
Summary: Unknown launch is left in Debug view after deletion of an OS 3 server adapter
Key: JBIDE-22152
URL: https://issues.jboss.org/browse/JBIDE-22152
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Attachments: launches.png
When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on a OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
!launches.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22152:
----------------------------------
Labels: openshift_v3 server_adapter (was: )
> Unknown launch is left in Debug view after deletion of an OS 3 server adapter
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22152
> URL: https://issues.jboss.org/browse/JBIDE-22152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Attachments: launches.png
>
>
> When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on a OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
> !launches.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years