[jbosstools-issues] [JBoss JIRA] (JBIDE-21756) Watch client errors with unknown enum type: ChangeType.ERROR
Andre Dietisheim (JIRA)
issues at jboss.org
Wed Feb 24 11:28:00 EST 2016
Andre Dietisheim created JBIDE-21756:
----------------------------------------
Summary: 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 at 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)
More information about the jbosstools-issues
mailing list