|
|
Re: RAP 3.0 Shutdown Problems [message #1705384 is a reply to message #1705380] |
Fri, 14 August 2015 13:01 |
Michael Froeschen Messages: 5 Registered: August 2015 |
Junior Member |
|
|
Yes we are shutting down the Application Server (Wildfly in this case).
That works fine if the RAP Client has never been opened by anyone or if everyone has closed his browsertab before the shutdown.
But it "hangs" when someone still has his tab open (that was what i meant with the active UISession)
The UIThread is not stopped in that case and blocks till the Session timeout (defined in the web.xml of the war) is reached.
The following exception is thrown when the timeout is reached and the shutdown continues:
14:58:49,226 ERROR [stderr] (UIThread [b0e25f6]) Exception in thread "UIThread [b0e25f6]" java.lang.NullPointerException
14:58:49,227 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.rap.ui.internal.preferences.SessionScope.getNode(SessionScope.java:68)
14:58:49,227 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.ui.preferences.ScopedPreferenceStoreCore.getStorePreferences(ScopedPreferenceStoreCore.java:225)
14:58:49,228 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.ui.preferences.ScopedPreferenceStoreCore.getPreferenceNodes(ScopedPreferenceStoreCore.java:267)
14:58:49,229 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.ui.preferences.ScopedPreferenceStoreCore.internalGet(ScopedPreferenceStoreCore.java:458)
14:58:49,230 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.ui.preferences.ScopedPreferenceStoreCore.getBoolean(ScopedPreferenceStoreCore.java:370)
14:58:49,230 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.ui.preferences.ScopedPreferenceStore.getBoolean(ScopedPreferenceStore.java:447)
14:58:49,231 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1097)
14:58:49,231 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.ui.internal.Workbench.access$12(Workbench.java:1071)
14:58:49,232 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.ui.internal.Workbench$21.run(Workbench.java:1337)
14:58:49,233 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.swt.custom.BusyIndicator.showWhile(Unknown Source)
14:58:49,233 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.ui.internal.Workbench.close(Workbench.java:1335)
14:58:49,233 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.ui.internal.Workbench.close(Workbench.java:1297)
14:58:49,234 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.ui.internal.Workbench$ShutdownHandler.handleEvent(Workbench.java:387)
14:58:49,234 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
14:58:49,235 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.swt.widgets.Display.sendEvent(Unknown Source)
14:58:49,235 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.swt.widgets.Display.sendDisposeEvent(Unknown Source)
14:58:49,236 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.swt.widgets.Display.release(Unknown Source)
14:58:49,236 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.swt.graphics.Device.dispose(Unknown Source)
14:58:49,237 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.rap.rwt.internal.lifecycle.UIThread.processShutdown(UIThread.java:176)
14:58:49,237 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.rap.rwt.internal.lifecycle.RWTLifeCycle$UIThreadController.run(Unknown Source)
14:58:49,238 ERROR [stderr] (UIThread [b0e25f6]) at java.lang.Thread.run(Thread.java:745)
14:58:49,238 ERROR [stderr] (UIThread [b0e25f6]) at org.eclipse.rap.rwt.internal.lifecycle.UIThread.run(UIThread.java:111)
Quote:
do you have a reproducible scenario with our Workbench Demo
I will try to reproduce this with the workbench demo
|
|
|
|
|
|
|
Re: RAP 3.0 Shutdown Problems [message #1705709 is a reply to message #1705575] |
Tue, 18 August 2015 13:16 |
Michael Froeschen Messages: 5 Registered: August 2015 |
Junior Member |
|
|
Correct me if i am wrong, but i think a job that is scheduled with a delay should not create a ServerPush, especially a system job, which should not be visible to the user.
The ServerPush should be created when needed and that would be the moment in which the Job changes its state to running.
The problem for us is, that our jobs have to run periodically. That is the reason why these jobs are (re)scheduled right after they finished.
I am not able to stop them at this moment because all mechanisms i know are not working. Both an ApplicationContextListener as well as an UISessionListener are not invoked till the timeout is reached. I do not know another way of getting notified that rap should be shutting down.
[Updated on: Tue, 18 August 2015 13:16] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.03756 seconds