[JBoss JIRA] (JBDS-3604) NoStackTrace below DiscoveryViewer$18.run
by Automated Error Reporting Bot (JIRA)
Automated Error Reporting Bot created JBDS-3604:
---------------------------------------------------
Summary: NoStackTrace below DiscoveryViewer$18.run
Key: JBDS-3604
URL: https://issues.jboss.org/browse/JBDS-3604
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: aeri
Affects Versions: 9.1.0.CR1
Reporter: Automated Error Reporting Bot
The following incident was reported via the automated error reporting:
The user(s) left the following comments:
--- manderse(a)redhat.com wrote: ---
test message - why is this happening.
code: 0
plugin: org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
message: Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' declared in org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2a_v20151006_1928_B438.jar_806886544943382023.jar
fingerprint: dd8fd5fff4740f5c681ba9438f20d2d5
exception class: org.eclipse.epp.logging.aeri.core.util.NoStackTrace
exception message: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
number of children: 0
org.eclipse.epp.logging.aeri.core.util.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
at org.eclipse.mylyn.commons.core.StatusHandler.log(StatusHandler.java:47)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.connectCertificationsToDescriptors(ConnectorDiscovery.java:235)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:128)
at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1189)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
General Information:
reported-by: manderse(a)redhat.com
anonymous-id: 751eebb9-1908-48d7-882a-d109eb3ae47e
eclipse-build-id: 4.5.0.I20150603-2000
eclipse-product: org.eclipse.platform.ide
operating system: MacOSX 10.11.2 (x86_64) - cocoa
jre-version: 1.8.0_20-b26
The following plug-ins were present on the execution stack (*):
1. org.eclipse.jface_3.11.0.v20150602-1400
2. org.eclipse.mylyn.commons.core_3.17.0.v20150625-2042
3. org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
4. org.jboss.tools.central_2.0.0.Final-v20151001-1531-B45
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/56b7dc...
* Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
Thank you for your assistance.
Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3603) NoStackTrace below DiscoveryViewer$18.run
by Automated Error Reporting Bot (JIRA)
Automated Error Reporting Bot created JBDS-3603:
---------------------------------------------------
Summary: NoStackTrace below DiscoveryViewer$18.run
Key: JBDS-3603
URL: https://issues.jboss.org/browse/JBDS-3603
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: aeri
Affects Versions: 9.1.0.CR1
Reporter: Automated Error Reporting Bot
The following incident was reported via the automated error reporting:
The user(s) left the following comments:
--- manderse(a)redhat.com wrote: ---
test message - why is this happening.
code: 0
plugin: org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
message: Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' declared in org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2a_v20151006_1928_B438.jar_806886544943382023.jar
fingerprint: dd8fd5fff4740f5c681ba9438f20d2d5
exception class: org.eclipse.epp.logging.aeri.core.util.NoStackTrace
exception message: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
number of children: 0
org.eclipse.epp.logging.aeri.core.util.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
at org.eclipse.mylyn.commons.core.StatusHandler.log(StatusHandler.java:47)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.connectCertificationsToDescriptors(ConnectorDiscovery.java:235)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:128)
at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1189)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
General Information:
reported-by: manderse(a)redhat.com
anonymous-id: 751eebb9-1908-48d7-882a-d109eb3ae47e
eclipse-build-id: 4.5.0.I20150603-2000
eclipse-product: org.eclipse.platform.ide
operating system: MacOSX 10.11.2 (x86_64) - cocoa
jre-version: 1.8.0_20-b26
The following plug-ins were present on the execution stack (*):
1. org.eclipse.jface_3.11.0.v20150602-1400
2. org.eclipse.mylyn.commons.core_3.17.0.v20150625-2042
3. org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
4. org.jboss.tools.central_2.0.0.Final-v20151001-1531-B45
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/56b7dc...
* Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
Thank you for your assistance.
Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21734) Deploying of a docker image from docker explorer has ambiguous connection
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21734?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21734:
---------------------------------------
That's not the same. In OpenShift Explorer view you have tree items and username is nonstyled text and server is styled text as some additional information. But in wizard and dialogs we have it with dash.
> Deploying of a docker image from docker explorer has ambiguous connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-21734
> URL: https://issues.jboss.org/browse/JBIDE-21734
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: ambiguous_connection.png
>
>
> When I am trying to deploy a docker image to OpenShift from Docker Explorer view, there is a combo box with listed existing OpenShift connections. If there are more than 1 connection to a specific server, it is not possible to know which one I am selecting (not without knowing its projects and even then they have to be different), because there is no username. The combo box with connections contains only list of server URLs. It could be in format e.g. "username - connection" like we have it on other places. See following screenshot
> !ambiguous_connection.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21714) ClassCastException in JBossCentralDropTarget$1.getUrlFromEvent(JBossCentralDropTarget.java:124) when dropping an external file into Editor site
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21714?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-21714:
-----------------------------------------
I'm using Windows 10.
Sure that the fix is not already included in the JDBS 9.1.0.Beta2 build?
> ClassCastException in JBossCentralDropTarget$1.getUrlFromEvent(JBossCentralDropTarget.java:124) when dropping an external file into Editor site
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21714
> URL: https://issues.jboss.org/browse/JBIDE-21714
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Reporter: Aurélien Pupier
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 4.3.1.CR1
>
> Attachments: dndSTack.png
>
>
> 1. DnD an external file onto JBDS Editor site
> {noformat}
> !ENTRY org.eclipse.ui 4 0 2016-02-18 10:50:09.183
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.ClassCastException: [Ljava.lang.String; cannot be cast to java.lang.String
> at org.jboss.tools.central.internal.dnd.JBossCentralDropTarget$1.getUrlFromEvent(JBossCentralDropTarget.java:124)
> at org.jboss.tools.central.internal.dnd.JBossCentralDropTarget$1.drop(JBossCentralDropTarget.java:90)
> at org.eclipse.swt.dnd.DNDListener.handleEvent(DNDListener.java:91)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1137)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1122)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:788)
> at org.eclipse.swt.dnd.DropTarget.Drop(DropTarget.java:456)
> at org.eclipse.swt.dnd.DropTarget.Drop_64(DropTarget.java:392)
> at org.eclipse.swt.dnd.DropTarget$3.method6(DropTarget.java:260)
> at org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:119)
> at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
> at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3767)
> 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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21756) Watch client errors with unknown enum type: ChangeType.ERROR
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21756?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-21756:
----------------------------------------
Assignee: Andre Dietisheim (was: Jeff Cantrill)
> Watch client errors with unknown enum type: ChangeType.ERROR
> ------------------------------------------------------------
>
> Key: JBIDE-21756
> URL: https://issues.jboss.org/browse/JBIDE-21756
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.CR1
>
>
> I dont have a consistent pattern for this so far. It happened when I created a new application from eap-basic-http-s2i template and tried to create a server adapter for it. It didnt happen in my 1st attempt, it only happend on the 2nd and not on any further attempt. Those other attemps errored with a 404 when the wizard tried to get the image stream tags.
> The exact stacktrace (which was repeated n-times in the Eclipse logs) is:
> {code}
> 2016-02-24 17:05:14.767:WARN:coir.WatchClient$WatchEndpoint:WebSocketClient@1099857077-11028: Unhandled Error (closing connection)
> java.lang.IllegalArgumentException: No enum constant com.openshift.restclient.IOpenShiftWatchListener.ChangeType.ERROR
> at java.lang.Enum.valueOf(Enum.java:238)
> at com.openshift.restclient.IOpenShiftWatchListener$ChangeType.valueOf(IOpenShiftWatchListener.java:45)
> at com.openshift.internal.restclient.WatchClient$WatchEndpoint.onWebSocketText(WatchClient.java:102)
> at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextMessage(JettyListenerEventDriver.java:128)
> at org.eclipse.jetty.websocket.common.message.SimpleTextMessage.messageComplete(SimpleTextMessage.java:69)
> at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.appendMessage(AbstractEventDriver.java:64)
> at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextFrame(JettyListenerEventDriver.java:122)
> at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.incomingFrame(AbstractEventDriver.java:160)
> at org.eclipse.jetty.websocket.common.WebSocketSession.incomingFrame(WebSocketSession.java:309)
> at org.eclipse.jetty.websocket.common.extensions.ExtensionStack.incomingFrame(ExtensionStack.java:214)
> at org.eclipse.jetty.websocket.common.Parser.notifyFrame(Parser.java:220)
> at org.eclipse.jetty.websocket.common.Parser.parse(Parser.java:258)
> at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:628)
> at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:476)
> at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21756) Watch client errors with unknown enum type: ChangeType.ERROR
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21756?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21756 at 2/24/16 11:29 AM:
--------------------------------------------------------------------
I dont know the exact cause for it so I think that we can at least provide fixes for the symptoms: * we should provide the enum (even better would be not to use an enum or at least a safe valueOf method) and
* maybe log to INFO or TRACE
was (Author: adietish):
I dont know the exact cause for it. I think that we should provide the enum (even better would be not to use an enum or at least a safe valueOf method) and maybe log to INFO or TRACE
> Watch client errors with unknown enum type: ChangeType.ERROR
> ------------------------------------------------------------
>
> Key: JBIDE-21756
> URL: https://issues.jboss.org/browse/JBIDE-21756
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.CR1
>
>
> I dont have a consistent pattern for this so far. It happened when I created a new application from eap-basic-http-s2i template and tried to create a server adapter for it. It didnt happen in my 1st attempt, it only happend on the 2nd and not on any further attempt. Those other attemps errored with a 404 when the wizard tried to get the image stream tags.
> The exact stacktrace (which was repeated n-times in the Eclipse logs) is:
> {code}
> 2016-02-24 17:05:14.767:WARN:coir.WatchClient$WatchEndpoint:WebSocketClient@1099857077-11028: Unhandled Error (closing connection)
> java.lang.IllegalArgumentException: No enum constant com.openshift.restclient.IOpenShiftWatchListener.ChangeType.ERROR
> at java.lang.Enum.valueOf(Enum.java:238)
> at com.openshift.restclient.IOpenShiftWatchListener$ChangeType.valueOf(IOpenShiftWatchListener.java:45)
> at com.openshift.internal.restclient.WatchClient$WatchEndpoint.onWebSocketText(WatchClient.java:102)
> at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextMessage(JettyListenerEventDriver.java:128)
> at org.eclipse.jetty.websocket.common.message.SimpleTextMessage.messageComplete(SimpleTextMessage.java:69)
> at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.appendMessage(AbstractEventDriver.java:64)
> at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextFrame(JettyListenerEventDriver.java:122)
> at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.incomingFrame(AbstractEventDriver.java:160)
> at org.eclipse.jetty.websocket.common.WebSocketSession.incomingFrame(WebSocketSession.java:309)
> at org.eclipse.jetty.websocket.common.extensions.ExtensionStack.incomingFrame(ExtensionStack.java:214)
> at org.eclipse.jetty.websocket.common.Parser.notifyFrame(Parser.java:220)
> at org.eclipse.jetty.websocket.common.Parser.parse(Parser.java:258)
> at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:628)
> at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:476)
> at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21756) Watch client errors with unknown enum type: ChangeType.ERROR
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21756?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21756 at 2/24/16 11:29 AM:
--------------------------------------------------------------------
I dont know the exact cause for it so I think that we can at least provide fixes for the symptoms:
* we should provide the enum (even better would be not to use an enum or at least a safe valueOf method) and
* maybe log to INFO or TRACE
was (Author: adietish):
I dont know the exact cause for it so I think that we can at least provide fixes for the symptoms: * we should provide the enum (even better would be not to use an enum or at least a safe valueOf method) and
* maybe log to INFO or TRACE
> Watch client errors with unknown enum type: ChangeType.ERROR
> ------------------------------------------------------------
>
> Key: JBIDE-21756
> URL: https://issues.jboss.org/browse/JBIDE-21756
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.CR1
>
>
> I dont have a consistent pattern for this so far. It happened when I created a new application from eap-basic-http-s2i template and tried to create a server adapter for it. It didnt happen in my 1st attempt, it only happend on the 2nd and not on any further attempt. Those other attemps errored with a 404 when the wizard tried to get the image stream tags.
> The exact stacktrace (which was repeated n-times in the Eclipse logs) is:
> {code}
> 2016-02-24 17:05:14.767:WARN:coir.WatchClient$WatchEndpoint:WebSocketClient@1099857077-11028: Unhandled Error (closing connection)
> java.lang.IllegalArgumentException: No enum constant com.openshift.restclient.IOpenShiftWatchListener.ChangeType.ERROR
> at java.lang.Enum.valueOf(Enum.java:238)
> at com.openshift.restclient.IOpenShiftWatchListener$ChangeType.valueOf(IOpenShiftWatchListener.java:45)
> at com.openshift.internal.restclient.WatchClient$WatchEndpoint.onWebSocketText(WatchClient.java:102)
> at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextMessage(JettyListenerEventDriver.java:128)
> at org.eclipse.jetty.websocket.common.message.SimpleTextMessage.messageComplete(SimpleTextMessage.java:69)
> at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.appendMessage(AbstractEventDriver.java:64)
> at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextFrame(JettyListenerEventDriver.java:122)
> at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.incomingFrame(AbstractEventDriver.java:160)
> at org.eclipse.jetty.websocket.common.WebSocketSession.incomingFrame(WebSocketSession.java:309)
> at org.eclipse.jetty.websocket.common.extensions.ExtensionStack.incomingFrame(ExtensionStack.java:214)
> at org.eclipse.jetty.websocket.common.Parser.notifyFrame(Parser.java:220)
> at org.eclipse.jetty.websocket.common.Parser.parse(Parser.java:258)
> at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:628)
> at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:476)
> at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21756) Watch client errors with unknown enum type: ChangeType.ERROR
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21756?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21756:
------------------------------------------
I dont know the exact cause for it. I think that we should provide the enum (even better would be not to use an enum or at least a safe valueOf method) and maybe log to INFO or TRACE
> Watch client errors with unknown enum type: ChangeType.ERROR
> ------------------------------------------------------------
>
> Key: JBIDE-21756
> URL: https://issues.jboss.org/browse/JBIDE-21756
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.CR1
>
>
> I dont have a consistent pattern for this so far. It happened when I created a new application from eap-basic-http-s2i template and tried to create a server adapter for it. It didnt happen in my 1st attempt, it only happend on the 2nd and not on any further attempt. Those other attemps errored with a 404 when the wizard tried to get the image stream tags.
> The exact stacktrace (which was repeated n-times in the Eclipse logs) is:
> {code}
> 2016-02-24 17:05:14.767:WARN:coir.WatchClient$WatchEndpoint:WebSocketClient@1099857077-11028: Unhandled Error (closing connection)
> java.lang.IllegalArgumentException: No enum constant com.openshift.restclient.IOpenShiftWatchListener.ChangeType.ERROR
> at java.lang.Enum.valueOf(Enum.java:238)
> at com.openshift.restclient.IOpenShiftWatchListener$ChangeType.valueOf(IOpenShiftWatchListener.java:45)
> at com.openshift.internal.restclient.WatchClient$WatchEndpoint.onWebSocketText(WatchClient.java:102)
> at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextMessage(JettyListenerEventDriver.java:128)
> at org.eclipse.jetty.websocket.common.message.SimpleTextMessage.messageComplete(SimpleTextMessage.java:69)
> at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.appendMessage(AbstractEventDriver.java:64)
> at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextFrame(JettyListenerEventDriver.java:122)
> at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.incomingFrame(AbstractEventDriver.java:160)
> at org.eclipse.jetty.websocket.common.WebSocketSession.incomingFrame(WebSocketSession.java:309)
> at org.eclipse.jetty.websocket.common.extensions.ExtensionStack.incomingFrame(ExtensionStack.java:214)
> at org.eclipse.jetty.websocket.common.Parser.notifyFrame(Parser.java:220)
> at org.eclipse.jetty.websocket.common.Parser.parse(Parser.java:258)
> at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:628)
> at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:476)
> at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month