[JBoss JIRA] (ERT-161) NullPointerException in BuildDockerImageShortcut.getPath [EBZ#491880]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-161?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston reassigned ERT-161:
---------------------------------
Assignee: Jeff Johnston
> NullPointerException in BuildDockerImageShortcut.getPath [EBZ#491880]
> ---------------------------------------------------------------------
>
> Key: ERT-161
> URL: https://issues.jboss.org/browse/ERT-161
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Jeff Johnston
> Labels: Docker, bzira
> Fix For: Neon (4.6) RC3
>
>
> The following incident was reported via the automated error reporting:
> code: 0
> plugin: org.eclipse.ui_3.107.0.v20150507-1945
> message: Unhandled event loop exception
> fingerprint: 18198d9d
> exception class: java.lang.NullPointerException
> exception message: -
> number of children: 0
>
> java.lang.NullPointerException: null
> at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.getPath(BuildDockerImageShortcut.java:150)[REQUIRED, TOPMOST]
> at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.findLaunchConfiguration(BuildDockerImageShortcut.java:104)
> at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.launch(BuildDockerImageShortcut.java:72)
> at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.launch(BuildDockerImageShortcut.java:68)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:420)[REQUIRED]
> at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.run(LaunchShortcutAction.java:71)
> at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.runWithEvent(LaunchShortcutAction.java:123)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> 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.jface.action.ActionContributionItem$9.handleEvent(ActionContributionItem.java:1293)
> 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:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> 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(NativeMethodAccessorImpl.java:-2)
> 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)
>
>
> General Information:
> reported-by:
> anonymous-id: 49ee8b2a-25a2-4fc9-b161-51ae7da464c1
> eclipse-build-id: 4.5.1.M20150904-0015
> eclipse-product: org.eclipse.epp.package.jee.product
> operating system: MacOSX 10.11.4 (x86_64) - cocoa
> jre-version: 1.8.0_65-b17
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.core.databinding.observable_1.5.0.v20150422-0725
> 2. org.eclipse.core.databinding_1.5.0.v20150422-0725
> 3. org.eclipse.core.runtime_3.11.1.v20150903-1804
> 4. org.eclipse.debug.ui_3.11.100.v20150731-1137
> 5. org.eclipse.e4.ui.workbench_1.3.0.v20150531-1948
> 6. org.eclipse.e4.ui.workbench.swt_0.13.0.v20150504-0621
> 7. org.eclipse.equinox.app_1.3.300.v20150423-1356
> 8. org.eclipse.equinox.launcher_1.3.100.v20150511-1540
> 9. org.eclipse.jface_3.11.0.v20150602-1400
> 10. org.eclipse.linuxtools.docker.ui_1.2.0.201512112123
> 11. org.eclipse.swt_3.104.1.v20150825-0743
> 12. org.eclipse.ui_3.107.0.v20150507-1945
> 13. org.eclipse.ui.ide.application_1.1.0.v20150422-0725
> 14. org.eclipse.ui.ide_3.11.0.v20150825-2158
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/571129...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> This bug was created on behalf of xcoulon@xxxxxxxxxxxx.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-161) NullPointerException in BuildDockerImageShortcut.getPath [EBZ#491880]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-161?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston resolved ERT-161.
-------------------------------
Fix Version/s: Neon (4.6) RC3
Resolution: Done
> NullPointerException in BuildDockerImageShortcut.getPath [EBZ#491880]
> ---------------------------------------------------------------------
>
> Key: ERT-161
> URL: https://issues.jboss.org/browse/ERT-161
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Jeff Johnston
> Labels: Docker, bzira
> Fix For: Neon (4.6) RC3
>
>
> The following incident was reported via the automated error reporting:
> code: 0
> plugin: org.eclipse.ui_3.107.0.v20150507-1945
> message: Unhandled event loop exception
> fingerprint: 18198d9d
> exception class: java.lang.NullPointerException
> exception message: -
> number of children: 0
>
> java.lang.NullPointerException: null
> at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.getPath(BuildDockerImageShortcut.java:150)[REQUIRED, TOPMOST]
> at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.findLaunchConfiguration(BuildDockerImageShortcut.java:104)
> at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.launch(BuildDockerImageShortcut.java:72)
> at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.launch(BuildDockerImageShortcut.java:68)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:420)[REQUIRED]
> at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.run(LaunchShortcutAction.java:71)
> at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.runWithEvent(LaunchShortcutAction.java:123)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> 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.jface.action.ActionContributionItem$9.handleEvent(ActionContributionItem.java:1293)
> 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:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> 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(NativeMethodAccessorImpl.java:-2)
> 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)
>
>
> General Information:
> reported-by:
> anonymous-id: 49ee8b2a-25a2-4fc9-b161-51ae7da464c1
> eclipse-build-id: 4.5.1.M20150904-0015
> eclipse-product: org.eclipse.epp.package.jee.product
> operating system: MacOSX 10.11.4 (x86_64) - cocoa
> jre-version: 1.8.0_65-b17
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.core.databinding.observable_1.5.0.v20150422-0725
> 2. org.eclipse.core.databinding_1.5.0.v20150422-0725
> 3. org.eclipse.core.runtime_3.11.1.v20150903-1804
> 4. org.eclipse.debug.ui_3.11.100.v20150731-1137
> 5. org.eclipse.e4.ui.workbench_1.3.0.v20150531-1948
> 6. org.eclipse.e4.ui.workbench.swt_0.13.0.v20150504-0621
> 7. org.eclipse.equinox.app_1.3.300.v20150423-1356
> 8. org.eclipse.equinox.launcher_1.3.100.v20150511-1540
> 9. org.eclipse.jface_3.11.0.v20150602-1400
> 10. org.eclipse.linuxtools.docker.ui_1.2.0.201512112123
> 11. org.eclipse.swt_3.104.1.v20150825-0743
> 12. org.eclipse.ui_3.107.0.v20150507-1945
> 13. org.eclipse.ui.ide.application_1.1.0.v20150422-0725
> 14. org.eclipse.ui.ide_3.11.0.v20150825-2158
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/571129...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> This bug was created on behalf of xcoulon@xxxxxxxxxxxx.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-162) Docker build fails when called via Quick Access menu [EBZ#491999]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-162?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston updated ERT-162:
------------------------------
Sprint: devex #115 May 2016
> Docker build fails when called via Quick Access menu [EBZ#491999]
> -----------------------------------------------------------------
>
> Key: ERT-162
> URL: https://issues.jboss.org/browse/ERT-162
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: Docker, bzira
> Fix For: Neon (4.6) RC3
>
>
> When you call the Docker build command via the quick access menu (Ctrl+3), it will fail:
> An internal error occurred during: "Building Image". java.lang.NullPointerException
> java.lang.NullPointerException
> at org.eclipse.linuxtools.internal.docker.ui.commands.BuildImageCommandHandler$1.run(BuildImageCommandHandler.java:131)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> When you call this command via the build icon in Docker Images view, it will work.
> The reason I think is the fact that the quick access menu doesn't have the context of a docker connection to use for the build.
> One solution for this would be to include Docker connection dropdown menu in the dialog and then when you call this from Docker Images view, the active connection would be selected by default.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-162) Docker build fails when called via Quick Access menu [EBZ#491999]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-162?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston reassigned ERT-162:
---------------------------------
Assignee: Jeff Johnston
> Docker build fails when called via Quick Access menu [EBZ#491999]
> -----------------------------------------------------------------
>
> Key: ERT-162
> URL: https://issues.jboss.org/browse/ERT-162
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Jeff Johnston
> Labels: Docker, bzira
> Fix For: Neon (4.6) RC3
>
>
> When you call the Docker build command via the quick access menu (Ctrl+3), it will fail:
> An internal error occurred during: "Building Image". java.lang.NullPointerException
> java.lang.NullPointerException
> at org.eclipse.linuxtools.internal.docker.ui.commands.BuildImageCommandHandler$1.run(BuildImageCommandHandler.java:131)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> When you call this command via the build icon in Docker Images view, it will work.
> The reason I think is the fact that the quick access menu doesn't have the context of a docker connection to use for the build.
> One solution for this would be to include Docker connection dropdown menu in the dialog and then when you call this from Docker Images view, the active connection would be selected by default.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-162) Docker build fails when called via Quick Access menu [EBZ#491999]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-162?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston resolved ERT-162.
-------------------------------
Fix Version/s: Neon (4.6) RC3
Resolution: Done
> Docker build fails when called via Quick Access menu [EBZ#491999]
> -----------------------------------------------------------------
>
> Key: ERT-162
> URL: https://issues.jboss.org/browse/ERT-162
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Jeff Johnston
> Labels: Docker, bzira
> Fix For: Neon (4.6) RC3
>
>
> When you call the Docker build command via the quick access menu (Ctrl+3), it will fail:
> An internal error occurred during: "Building Image". java.lang.NullPointerException
> java.lang.NullPointerException
> at org.eclipse.linuxtools.internal.docker.ui.commands.BuildImageCommandHandler$1.run(BuildImageCommandHandler.java:131)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> When you call this command via the build icon in Docker Images view, it will work.
> The reason I think is the fact that the quick access menu doesn't have the context of a docker connection to use for the build.
> One solution for this would be to include Docker connection dropdown menu in the dialog and then when you call this from Docker Images view, the active connection would be selected by default.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-153) StandInException in DockerConnection$LogThread.execute [EBZ#485737]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-153?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston resolved ERT-153.
-------------------------------
Fix Version/s: Neon (4.6) RC3
Resolution: Done
> StandInException in DockerConnection$LogThread.execute [EBZ#485737]
> -------------------------------------------------------------------
>
> Key: ERT-153
> URL: https://issues.jboss.org/browse/ERT-153
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Jeff Johnston
> Labels: Docker, bzira
> Fix For: Neon (4.6) RC3
>
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- wrote: ---
> shutting down a wildfly instance (takes a couple seconds) on docker 1.7.1. Not really a bug in my opinion, operation went as expected.
>
> code: 4
> plugin: org.eclipse.linuxtools.docker.core_1.0.0.201506102203
> message: sleep interrupted
> fingerprint: 18dade7c
> exception class: org.eclipse.epp.internal.logging.aeri.ui.log.StandInStacktraceProvider$StandInException
> exception message: Stand-In Stacktrace supplied by the Eclipse Error Reporting
> number of children: 0
>
> org.eclipse.epp.internal.logging.aeri.ui.log.StandInStacktraceProvider$StandInException: Stand-In Stacktrace supplied by the Eclipse Error Reporting
> at org.eclipse.linuxtools.docker.core.Activator.log(Activator.java:52)
> at org.eclipse.linuxtools.docker.core.Activator.logErrorMessage(Activator.java:56)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection$LogThread.execute(DockerConnection.java:798)[REQUIRED, TOPMOST]
> at org.eclipse.linuxtools.internal.docker.core.AbstractKillableThread.run(AbstractKillableThread.java:49)
>
>
> General Information:
> reported-by:
> anonymous-id: 824b7eb7-45b7-49fc-a1e5-a94fcf50da7e
> eclipse-build-id: 4.5.0.I20150603-2000
> eclipse-product: org.eclipse.epp.package.jee.product
> operating system: Linux 3.19.0 (x86_64) - gtk
> jre-version: 1.8.0_51-b16
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.linuxtools.docker.core_1.0.0.201506102203
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/55ca39...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> This bug was created on behalf of xcoulon@xxxxxxxxxxxx.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-153) StandInException in DockerConnection$LogThread.execute [EBZ#485737]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-153?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston reassigned ERT-153:
---------------------------------
Assignee: Jeff Johnston
> StandInException in DockerConnection$LogThread.execute [EBZ#485737]
> -------------------------------------------------------------------
>
> Key: ERT-153
> URL: https://issues.jboss.org/browse/ERT-153
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Jeff Johnston
> Labels: Docker, bzira
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- wrote: ---
> shutting down a wildfly instance (takes a couple seconds) on docker 1.7.1. Not really a bug in my opinion, operation went as expected.
>
> code: 4
> plugin: org.eclipse.linuxtools.docker.core_1.0.0.201506102203
> message: sleep interrupted
> fingerprint: 18dade7c
> exception class: org.eclipse.epp.internal.logging.aeri.ui.log.StandInStacktraceProvider$StandInException
> exception message: Stand-In Stacktrace supplied by the Eclipse Error Reporting
> number of children: 0
>
> org.eclipse.epp.internal.logging.aeri.ui.log.StandInStacktraceProvider$StandInException: Stand-In Stacktrace supplied by the Eclipse Error Reporting
> at org.eclipse.linuxtools.docker.core.Activator.log(Activator.java:52)
> at org.eclipse.linuxtools.docker.core.Activator.logErrorMessage(Activator.java:56)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection$LogThread.execute(DockerConnection.java:798)[REQUIRED, TOPMOST]
> at org.eclipse.linuxtools.internal.docker.core.AbstractKillableThread.run(AbstractKillableThread.java:49)
>
>
> General Information:
> reported-by:
> anonymous-id: 824b7eb7-45b7-49fc-a1e5-a94fcf50da7e
> eclipse-build-id: 4.5.0.I20150603-2000
> eclipse-product: org.eclipse.epp.package.jee.product
> operating system: Linux 3.19.0 (x86_64) - gtk
> jre-version: 1.8.0_51-b16
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.linuxtools.docker.core_1.0.0.201506102203
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/55ca39...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> This bug was created on behalf of xcoulon@xxxxxxxxxxxx.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-153) StandInException in DockerConnection$LogThread.execute [EBZ#485737]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-153?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston updated ERT-153:
------------------------------
Sprint: devex #115 May 2016
> StandInException in DockerConnection$LogThread.execute [EBZ#485737]
> -------------------------------------------------------------------
>
> Key: ERT-153
> URL: https://issues.jboss.org/browse/ERT-153
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: Docker, bzira
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- wrote: ---
> shutting down a wildfly instance (takes a couple seconds) on docker 1.7.1. Not really a bug in my opinion, operation went as expected.
>
> code: 4
> plugin: org.eclipse.linuxtools.docker.core_1.0.0.201506102203
> message: sleep interrupted
> fingerprint: 18dade7c
> exception class: org.eclipse.epp.internal.logging.aeri.ui.log.StandInStacktraceProvider$StandInException
> exception message: Stand-In Stacktrace supplied by the Eclipse Error Reporting
> number of children: 0
>
> org.eclipse.epp.internal.logging.aeri.ui.log.StandInStacktraceProvider$StandInException: Stand-In Stacktrace supplied by the Eclipse Error Reporting
> at org.eclipse.linuxtools.docker.core.Activator.log(Activator.java:52)
> at org.eclipse.linuxtools.docker.core.Activator.logErrorMessage(Activator.java:56)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection$LogThread.execute(DockerConnection.java:798)[REQUIRED, TOPMOST]
> at org.eclipse.linuxtools.internal.docker.core.AbstractKillableThread.run(AbstractKillableThread.java:49)
>
>
> General Information:
> reported-by:
> anonymous-id: 824b7eb7-45b7-49fc-a1e5-a94fcf50da7e
> eclipse-build-id: 4.5.0.I20150603-2000
> eclipse-product: org.eclipse.epp.package.jee.product
> operating system: Linux 3.19.0 (x86_64) - gtk
> jre-version: 1.8.0_51-b16
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.linuxtools.docker.core_1.0.0.201506102203
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/55ca39...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> This bug was created on behalf of xcoulon@xxxxxxxxxxxx.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months