| Summary: | NullPointerException in SessionSingletonBase.getInstanceLock() on browser reload if UICallBack activated | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Timo Rohrberg <timo.rohrberg> | ||||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | timo.rohrberg | ||||||
| Version: | 1.4 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 7 | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Timo Rohrberg
Created attachment 202652 [details]
Demo RAP project to reproduce bug.
Created attachment 202653 [details]
RAP Plugins' versions overview.
Timo, could you post the NPE stack trace? (In reply to comment #3) > Timo, could you post the NPE stack trace? Yes, of course. Sorry, I forgot about this. Here it is: java.lang.NullPointerException at org.eclipse.rwt.SessionSingletonBase.getInstanceLock(SessionSingletonBase.java:106) at org.eclipse.rwt.SessionSingletonBase.getInstance(SessionSingletonBase.java:88) at org.eclipse.rwt.internal.lifecycle.UICallBackServiceHandler$IdManager.getInstance(UICallBackServiceHandler.java:53) at org.eclipse.rwt.internal.lifecycle.UICallBackServiceHandler.isUICallBackActive(UICallBackServiceHandler.java:170) at org.eclipse.rwt.internal.lifecycle.UICallBackServiceHandler.jsUICallBack(UICallBackServiceHandler.java:149) at org.eclipse.rwt.internal.lifecycle.UICallBackServiceHandler.writeResponse(UICallBackServiceHandler.java:143) at org.eclipse.rwt.internal.lifecycle.UICallBackServiceHandler.service(UICallBackServiceHandler.java:91) at org.eclipse.rwt.internal.service.ServiceManager$HandlerDispatcher.service(ServiceManager.java:33) at org.eclipse.rwt.internal.engine.RWTDelegate.doPost(RWTDelegate.java:46) at org.eclipse.rwt.internal.engine.RWTDelegate.doGet(RWTDelegate.java:35) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:317) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:924) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) Timo, why do you attempt to deactivate the UICallback at session shutdown in the first place? If the session is terminated, the UICallback is released anyway. In 1.5, we reworked the UI Callback code (bug 344989, bug 351961) and the code for session singleton management (bug 345702). Can you reproduce the issue with 1.5? Hello Rüdiger, in fact, the problem seems to be solved with the 1.5 nightly build RAP target components - at least, I could not reproduce the bug with it... Should I close the issue then? Concerning the UICallBack deactivation: Is it really correct to not deactivate it at all and just leave that to the shutdown of the session? Maybe we should relocate a discussion about this back into my original forum entry (http://www.eclipse.org/forums/index.php/t/238002/)? Greetings, Timo (In reply to comment #6) > in fact, the problem seems to be solved with the 1.5 nightly build RAP target > components - at least, I could not reproduce the bug with it... > Should I close the issue then? Closing as WONTFIX for 1.4, works in 1.5 > Concerning the UICallBack deactivation: Is it really correct to not deactivate > it at all and just leave that to the shutdown of the session? Maybe we should > relocate a discussion about this back into my original forum entry > (http://www.eclipse.org/forums/index.php/t/238002/)? I added a note to the JavaDoc of UICallBack#activate() and to the server push wiki (http://wiki.eclipse.org/RAP/UI_Callback). Fell free to reference these in the foum if you like. |