-
Notifications
You must be signed in to change notification settings - Fork 31
[IDE] Console view not working on trial #595
Comments
@dpanayotov, this have to be related with the Kyma deployment/configuration, as similar deployment on pure Kubernetes where the view is working as expected: https://trial.apps.dirigible.io It has to do with some issues with WebSockets, as the connection is being closed instantly. @krasimirdermendzhiev could give more insights on the both deployments. |
@ThuF on trial https://trial.apps.xsk.io deployment there is Kyma with Istio, but on https://trial.apps.dirigible.io deployment we don't use Istio. I think this is something with configuration of mTLS on Istio. |
Related exception: [ERROR] [http-nio-8080-exec-10] o.e.d.r.i.c.s.ConsoleWebsocketService - [ws:console] Session 0 error null
[ERROR] [http-nio-8080-exec-10] o.e.d.r.i.c.s.ConsoleWebsocketService - [ws:console] Session 0 error java.io.IOException: Broken pipe
[ERROR] [http-nio-8080-exec-10] o.e.d.r.i.c.s.ConsoleWebsocketService - [ws:console] java.io.IOException: Broken pipe
java.io.IOException: java.io.IOException: Broken pipe
at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:315) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:258) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.WsSession.sendCloseMessage(WsSession.java:592) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:480) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:313) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:250) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendString(WsRemoteEndpointImplBase.java:191) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:37) ~[tomcat-websocket.jar:8.5.34]
at org.eclipse.dirigible.runtime.ide.console.service.ConsoleWebsocketService.distribute(ConsoleWebsocketService.java:104) ~[dirigible-ide-service-console-6.1.0.jar:na]
at org.eclipse.dirigible.runtime.ide.console.service.ConsoleLoggingAppender.append(ConsoleLoggingAppender.java:29) ~[dirigible-ide-service-console-6.1.0.jar:na]
at org.eclipse.dirigible.runtime.ide.console.service.ConsoleLoggingAppender.append(ConsoleLoggingAppender.java:20) ~[dirigible-ide-service-console-6.1.0.jar:na]
at ch.qos.logback.core.AppenderBase.doAppend(AppenderBase.java:82) ~[logback-core-1.2.3.jar:na]
at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:51) ~[logback-core-1.2.3.jar:na]
at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:270) ~[logback-classic-1.2.3.jar:na]
at ch.qos.logback.classic.Logger.callAppenders(Logger.java:257) ~[logback-classic-1.2.3.jar:na]
at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:421) ~[logback-classic-1.2.3.jar:na]
at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:383) ~[logback-classic-1.2.3.jar:na]
at ch.qos.logback.classic.Logger.error(Logger.java:522) ~[logback-classic-1.2.3.jar:na]
at org.eclipse.dirigible.runtime.ide.console.service.ConsoleWebsocketService.onError(ConsoleWebsocketService.java:75) ~[dirigible-ide-service-console-6.1.0.jar:na]
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:na]
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
at java.base/java.lang.reflect.Method.invoke(Method.java:567) ~[na:na]
at org.apache.tomcat.websocket.pojo.PojoEndpointBase.onError(PojoEndpointBase.java:133) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.onError(WsHttpUpgradeHandler.java:216) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:152) ~[tomcat-websocket.jar:8.5.34]
at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:54) ~[tomcat-coyote.jar:8.5.34]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:53) ~[tomcat-coyote.jar:8.5.34]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:806) ~[tomcat-coyote.jar:8.5.34]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498) ~[tomcat-coyote.jar:8.5.34]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) ~[tomcat-coyote.jar:8.5.34]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[na:na]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) ~[tomcat-util.jar:8.5.34]
at java.base/java.lang.Thread.run(Thread.java:830) ~[na:na]
Caused by: java.io.IOException: Broken pipe
at java.base/sun.nio.ch.FileDispatcherImpl.write0(Native Method) ~[na:na]
at java.base/sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:62) ~[na:na]
at java.base/sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:113) ~[na:na]
at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:79) ~[na:na]
at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:50) ~[na:na]
at java.base/sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:484) ~[na:na]
at org.apache.tomcat.util.net.NioChannel.write(NioChannel.java:134) ~[tomcat-coyote.jar:8.5.34]
at org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSelector.java:101) ~[tomcat-coyote.jar:8.5.34]
at org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.java:157) ~[tomcat-coyote.jar:8.5.34]
at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.doWrite(NioEndpoint.java:1306) ~[tomcat-coyote.jar:8.5.34]
at org.apache.tomcat.util.net.SocketWrapperBase.doWrite(SocketWrapperBase.java:726) ~[tomcat-coyote.jar:8.5.34]
at org.apache.tomcat.util.net.SocketWrapperBase.flushBlocking(SocketWrapperBase.java:679) ~[tomcat-coyote.jar:8.5.34]
at org.apache.tomcat.util.net.SocketWrapperBase.flush(SocketWrapperBase.java:669) ~[tomcat-coyote.jar:8.5.34]
at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doWrite(WsRemoteEndpointImplServer.java:96) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:494) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:309) ~[tomcat-websocket.jar:8.5.34]
... 34 common frames omitted
java.io.IOException: Broken pipe
[ERROR] [http-nio-8080-exec-10] o.e.d.r.i.c.s.ConsoleWebsocketService - [ws:console] null
java.io.EOFException: null
at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1289) ~[tomcat-coyote.jar:8.5.34]
at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.read(NioEndpoint.java:1223) ~[tomcat-coyote.jar:8.5.34]
at org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:72) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.server.WsFrameServer.doOnDataAvailable(WsFrameServer.java:171) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.server.WsFrameServer.notifyDataAvailable(WsFrameServer.java:151) ~[tomcat-websocket.jar:8.5.34]
at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:148) ~[tomcat-websocket.jar:8.5.34]
at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:54) ~[tomcat-coyote.jar:8.5.34]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:53) ~[tomcat-coyote.jar:8.5.34]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:806) ~[tomcat-coyote.jar:8.5.34]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498) ~[tomcat-coyote.jar:8.5.34]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) ~[tomcat-coyote.jar:8.5.34]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[na:na]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) ~[tomcat-util.jar:8.5.34]
at java.base/java.lang.Thread.run(Thread.java:830) ~[na:na] |
It seems that the issue is related to session storage and the way we are doing OAuth authentication: |
The issue is blocked for the time being. More investigation needs to be done in order to determine the exact reason for the issue. It seems that it's related to the way authentication is done in the OAuthFilter and maybe the lack of HttpSession? |
Possibly related to #597 |
Issue cloned to eclipse/dirigible#1478 |
Fixed with eclipse/dirigible#1480, will be available with the next released version of Eclipse Dirigible. |
Describe the bug
Console view on trial returns an error
[ERROR] Connection problem! Check security roles assignments.
In the network tab web socket connection is immediately closed
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Logs are streamed and no error is shown
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: