I also saw it. Can you file a new JIRA issue for it?
On Thu, Aug 4, 2016 at 1:37 PM, Sachin Janani <sjan...@snappydata.io> wrote: > I also saw the same bug.It occurs when shiro authentication was enabled and > someone tries to change interpreter settings.This stacktrace is more > frequent and never stops.In spite of this everything works fine.It seems > like a bug > > On Thu, Aug 4, 2016 at 5:09 AM, Weipu Zhao <zhaoweipu....@gmail.com> > wrote: > > > Hi, > > > > When I play around with Zeppelin 0.6.0 release with Shiro following > > instructions in here > > <http://zeppelin.apache.org/docs/0.6.0/security/shiroauthentication.html > >, > > if > > I just open the home page but don't login, I see the following ERROR > > message keep show up periodically (every 10s) in zeppelin log, which > could > > potentially fill up this log file with this same error and make it really > > hard to trace the real error message: > > > > > > ERROR [2016-08-03 16:34:09,471] ({qtp636329330-37} > > NotebookServer.java[onMessage]:211) - Can't handle message > > java.lang.Exception: Invalid ticket != > > 5d56af6b-a49c-4dc1-9723-abf47876c389 > > at > > > > > org.apache.zeppelin.socket.NotebookServer.onMessage(NotebookServer.java:117) > > at > > > > > org.apache.zeppelin.socket.NotebookSocket.onWebSocketText(NotebookSocket.java:56) > > 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:65) > > at > > > > > org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextFrame(JettyListenerEventDriver.java:122) > > at > > > > > org.eclipse.jetty.websocket.common.events.AbstractEventDriver.incomingFrame(AbstractEventDriver.java:161) > > 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:632) > > at > > > > > org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:480) > > at > > > org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544) > > 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) > > > > > > Am I missing some configurations? Is this expected? I'm happy to file a > bug > > for this. > > > > Thanks, > > Weipu > > > -- 이종열, Jongyoul Lee, 李宗烈 http://madeng.net