Home » Eclipse Projects » Remote Application Platform (RAP) » Context Disposed Problem
| Context Disposed Problem [message #128418] |
Fri, 17 April 2009 06:41  |
 Hasan Ceylan
Messages: 198
Registered: July 2009 |
Senior Member |
|
|
Bump...
Hello,
We have been experiencing exactly the same problem against 1.2M6 release
java.lang.IllegalStateException: The context has been disposed.
at
org.eclipse.rwt.internal.service.ServiceContext.checkState(S erviceContext.java:154)
at
org.eclipse.rwt.internal.service.ServiceContext.getStateInfo (ServiceContext.java:104)
at
org.eclipse.rwt.internal.service.ContextProvider.getStateInf o(ContextProvider.java:166)
at
org.eclipse.rwt.internal.lifecycle.CurrentPhase.get(CurrentP hase.java:48)
at
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.readAndDispa tch(RWTLifeCycle.java:236)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :721)
at
org.eclipse.ui.application.WorkbenchAdvisor.openWindows(Work benchAdvisor.java:807)
at
org.eclipse.ui.internal.Workbench$25.runWithException(Workbe nch.java:1430)
at
org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.java:32)
at
org.eclipse.rwt.internal.lifecycle.UICallBackManager.addSync (UICallBackManager.java:119)
at org.eclipse.swt.widgets.Display$2.run(Display.java:649)
at
org.eclipse.rwt.internal.lifecycle.UICallBackServiceHandler. runNonUIThreadWithFakeContext(UICallBackServiceHandler.java: 455)
at
org.eclipse.rwt.lifecycle.UICallBack.runNonUIThreadWithFakeC ontext(UICallBack.java:44)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:647)
at
org.eclipse.ui.internal.StartupThreading.runWithoutException s(StartupThreading.java:110)
at org.eclipse.ui.internal.Workbench.init(Workbench.java:1425)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2404)
at org.eclipse.ui.internal.Workbench.access$5(Workbench.java:22 95)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:514)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:332)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:497)
at
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:157)
at
com.turquality.server.rap.Application.createUI(Application.j ava:60)
at
org.eclipse.rwt.internal.lifecycle.EntryPointManager.createU I(EntryPointManager.java:92)
at
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.createUI(RWT LifeCycle.java:228)
at
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run(RWTLifeCycle.java:116)
at java.lang.Thread.run(Thread.java:636)
Exception in thread "UIThread [79F5701409C7E6F2FCF5B12D127B16AD]"
java.lang.IllegalStateException: The context has been disposed.
at
org.eclipse.rwt.internal.service.ServiceContext.checkState(S erviceContext.java:154)
at
org.eclipse.rwt.internal.service.ServiceContext.getRequest(S erviceContext.java:82)
at
org.eclipse.rwt.internal.service.ContextProvider.getRequest( ContextProvider.java:129)
at
org.eclipse.rwt.internal.service.ContextProvider.getSession( ContextProvider.java:148)
at
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.setShutdownA dapter(RWTLifeCycle.java:345)
at
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.access$0(RWT LifeCycle.java:342)
at
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run(RWTLifeCycle.java:130)
at java.lang.Thread.run(Thread.java:636)
Any hints?
Hasan Ceylan
Roberto Sá‡nchez wrote:
> Hi Frank, now It works fine, I would like to test it a bit more, but all
> seems to be OK.
>
> Thank you.
>
> Bye
> Roberto.
>
>
> Frank Appel escribió:
>> Hi,
>>
>> please update against the latest CVS versions and tell me whether the
>> situation has improved. Sorry for your inconvenience.
>>
>> Ciao
>> Frank
>>
>>
>> "Roberto Sá‡nchez" <roberto@autonomind.com> schrieb im Newsbeitrag
>> news:fd0gpg$mt8$1@build.eclipse.org...
>>> Hi all, I've found this problem with new CVS updates, When you launch
>>> Demo app and close workbench, If you try to refresh page, to entry into
>>> application again, an exception is thrown:
>>>
>>> java.lang.IllegalStateException: The context has been disposed.
>>> at
>>>
org.eclipse.rwt.internal.service.ServiceContext.checkState(S erviceContext.java:154)
>>> at
>>>
org.eclipse.rwt.internal.service.ServiceContext.getRequest(S erviceContext.java:82)
>>> at
>>>
org.eclipse.rwt.internal.service.ContextProvider.getRequest( ContextProvider.java:128)
>>> at
>>>
org.eclipse.rwt.internal.service.ContextProvider.getSession( ContextProvider.java:147)
>>> at
>>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycleBlockControl$ ServiceHandlerProcessor.bufferThrowable(RWTLifeCycleBlockCon trol.java:90)
>>> at
>>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycleBlockControl$ ServiceHandlerProcessor.run(RWTLifeCycleBlockControl.java:70 )
>>> at
>>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycleThreadPool$Po olRunnable.run(RWTLifeCycleThreadPool.java:38)
>>> at
>>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycleThreadPool$Po olWorker.run(RWTLifeCycleThreadPool.java:66)
>>>
>>>
>>> I've created this bug:
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=204076 there are several
>>> situations when this problem happens.
>>>
>>> I was waiting for new performance improvements planned for this week,
>>> but with this problem I'm blocked, My new application release will have
>>> to await.
>>>
>>> I'm not an expert in RAP Lifecycle but I think that Context should be
>>> re-created when Entrypoint is called, but I don't know...
>>>
>>> Please, a patch/workaround will be welcome.
>>>
>>> Thanks in advance.
>>> Roberto.
>>
>>
|
|
|
| Re: Context Disposed Problem [message #128471 is a reply to message #128418] |
Fri, 17 April 2009 14:16  |
Rüdiger Herrmann
Messages: 581
Registered: July 2009 |
Senior Member |
|
|
Hasan,
please provide more information on how to reproduce the exception.
Cheers,
Rüdiger
Hasan Ceylan wrote:
> Bump...
>
> Hello,
>
> We have been experiencing exactly the same problem against 1.2M6 release
>
> java.lang.IllegalStateException: The context has been disposed.
>
>
> at
> org.eclipse.rwt.internal.service.ServiceContext.checkState(S erviceContext.java:154)
>
> at
> org.eclipse.rwt.internal.service.ServiceContext.getStateInfo (ServiceContext.java:104)
>
> at
> org.eclipse.rwt.internal.service.ContextProvider.getStateInf o(ContextProvider.java:166)
>
> at
> org.eclipse.rwt.internal.lifecycle.CurrentPhase.get(CurrentP hase.java:48)
>
> at
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.readAndDispa tch(RWTLifeCycle.java:236)
>
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :721)
>
>
> at
> org.eclipse.ui.application.WorkbenchAdvisor.openWindows(Work benchAdvisor.java:807)
>
> at
> org.eclipse.ui.internal.Workbench$25.runWithException(Workbe nch.java:1430)
>
> at
> org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.java:32)
>
> at
> org.eclipse.rwt.internal.lifecycle.UICallBackManager.addSync (UICallBackManager.java:119)
>
> at org.eclipse.swt.widgets.Display$2.run(Display.java:649)
>
>
> at
> org.eclipse.rwt.internal.lifecycle.UICallBackServiceHandler. runNonUIThreadWithFakeContext(UICallBackServiceHandler.java: 455)
>
> at
> org.eclipse.rwt.lifecycle.UICallBack.runNonUIThreadWithFakeC ontext(UICallBack.java:44)
>
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:647)
>
>
> at
> org.eclipse.ui.internal.StartupThreading.runWithoutException s(StartupThreading.java:110)
>
> at org.eclipse.ui.internal.Workbench.init(Workbench.java:1425)
>
>
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2404)
>
>
> at org.eclipse.ui.internal.Workbench.access$5(Workbench.java:22 95)
>
>
> at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:514)
>
>
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:332)
>
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:497)
>
> at
> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:157)
>
> at
> com.turquality.server.rap.Application.createUI(Application.j ava:60)
>
> at
> org.eclipse.rwt.internal.lifecycle.EntryPointManager.createU I(EntryPointManager.java:92)
>
> at
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.createUI(RWT LifeCycle.java:228)
>
> at
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run(RWTLifeCycle.java:116)
>
> at java.lang.Thread.run(Thread.java:636)
>
>
> Exception in thread "UIThread [79F5701409C7E6F2FCF5B12D127B16AD]"
> java.lang.IllegalStateException: The context has been disposed.
>
> at
> org.eclipse.rwt.internal.service.ServiceContext.checkState(S erviceContext.java:154)
>
> at
> org.eclipse.rwt.internal.service.ServiceContext.getRequest(S erviceContext.java:82)
>
> at
> org.eclipse.rwt.internal.service.ContextProvider.getRequest( ContextProvider.java:129)
>
> at
> org.eclipse.rwt.internal.service.ContextProvider.getSession( ContextProvider.java:148)
>
> at
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.setShutdownA dapter(RWTLifeCycle.java:345)
>
> at
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.access$0(RWT LifeCycle.java:342)
>
> at
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run(RWTLifeCycle.java:130)
>
> at java.lang.Thread.run(Thread.java:636)
>
> Any hints?
>
> Hasan Ceylan
>
> Roberto Sá‡nchez wrote:
>
>> Hi Frank, now It works fine, I would like to test it a bit more, but all
>> seems to be OK.
>>
>> Thank you.
>>
>> Bye
>> Roberto.
>>
>>
>> Frank Appel escribió:
>>> Hi,
>>>
>>> please update against the latest CVS versions and tell me whether the
>>> situation has improved. Sorry for your inconvenience.
>>>
>>> Ciao
>>> Frank
>>>
>>>
>>> "Roberto Sá‡nchez" <roberto@autonomind.com> schrieb im Newsbeitrag
>>> news:fd0gpg$mt8$1@build.eclipse.org...
>>>> Hi all, I've found this problem with new CVS updates, When you launch
>>>> Demo app and close workbench, If you try to refresh page, to entry into
>>>> application again, an exception is thrown:
>>>>
>>>> java.lang.IllegalStateException: The context has been disposed.
>>>> at
>>>>
> org.eclipse.rwt.internal.service.ServiceContext.checkState(S erviceContext.java:154)
>>>> at
>>>>
> org.eclipse.rwt.internal.service.ServiceContext.getRequest(S erviceContext.java:82)
>>>> at
>>>>
> org.eclipse.rwt.internal.service.ContextProvider.getRequest( ContextProvider.java:128)
>>>> at
>>>>
> org.eclipse.rwt.internal.service.ContextProvider.getSession( ContextProvider.java:147)
>>>> at
>>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycleBlockControl$ ServiceHandlerProcessor.bufferThrowable(RWTLifeCycleBlockCon trol.java:90)
>>>> at
>>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycleBlockControl$ ServiceHandlerProcessor.run(RWTLifeCycleBlockControl.java:70 )
>>>> at
>>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycleThreadPool$Po olRunnable.run(RWTLifeCycleThreadPool.java:38)
>>>> at
>>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycleThreadPool$Po olWorker.run(RWTLifeCycleThreadPool.java:66)
>>>>
>>>> I've created this bug:
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=204076 there are several
>>>> situations when this problem happens.
>>>>
>>>> I was waiting for new performance improvements planned for this week,
>>>> but with this problem I'm blocked, My new application release will have
>>>> to await.
>>>>
>>>> I'm not an expert in RAP Lifecycle but I think that Context should be
>>>> re-created when Entrypoint is called, but I don't know...
>>>>
>>>> Please, a patch/workaround will be welcome.
>>>>
>>>> Thanks in advance.
>>>> Roberto.
>>>
>
>
|
|
|
| Re: Context Disposed Problem [message #128509 is a reply to message #128471] |
Fri, 17 April 2009 17:49 |
Hasan Ceylan
Messages: 198
Registered: July 2009 |
Senior Member |
|
|
It looks to me like it has something to do with the long startup.
We have an OSGI application that has a large hibernate base. I suspect if
there are more then one request before all the plugins have been activated,
then this problem occurrs.
Hasan
Rüdiger Herrmann wrote:
> Hasan,
>
> please provide more information on how to reproduce the exception.
>
> Cheers,
> Rüdiger
>
> Hasan Ceylan wrote:
>> Bump...
>>
>> Hello,
>>
>> We have been experiencing exactly the same problem against 1.2M6 release
>>
>> java.lang.IllegalStateException: The context has been disposed.
>>
>>
>> at
>>
org.eclipse.rwt.internal.service.ServiceContext.checkState(S erviceContext.java:154)
>>
>> at
>>
org.eclipse.rwt.internal.service.ServiceContext.getStateInfo (ServiceContext.java:104)
>>
>> at
>>
org.eclipse.rwt.internal.service.ContextProvider.getStateInf o(ContextProvider.java:166)
>>
>> at
>> org.eclipse.rwt.internal.lifecycle.CurrentPhase.get(CurrentP hase.java:48)
>>
>> at
>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.readAndDispa tch(RWTLifeCycle.java:236)
>>
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :721)
>>
>>
>> at
>>
org.eclipse.ui.application.WorkbenchAdvisor.openWindows(Work benchAdvisor.java:807)
>>
>> at
>>
org.eclipse.ui.internal.Workbench$25.runWithException(Workbe nch.java:1430)
>>
>> at
>>
org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.java:32)
>>
>> at
>>
org.eclipse.rwt.internal.lifecycle.UICallBackManager.addSync (UICallBackManager.java:119)
>>
>> at org.eclipse.swt.widgets.Display$2.run(Display.java:649)
>>
>>
>> at
>>
org.eclipse.rwt.internal.lifecycle.UICallBackServiceHandler. runNonUIThreadWithFakeContext(UICallBackServiceHandler.java: 455)
>>
>> at
>>
org.eclipse.rwt.lifecycle.UICallBack.runNonUIThreadWithFakeC ontext(UICallBack.java:44)
>>
>> at org.eclipse.swt.widgets.Display.syncExec(Display.java:647)
>>
>>
>> at
>>
org.eclipse.ui.internal.StartupThreading.runWithoutException s(StartupThreading.java:110)
>>
>> at org.eclipse.ui.internal.Workbench.init(Workbench.java:1425)
>>
>>
>> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2404)
>>
>>
>> at
>> org.eclipse.ui.internal.Workbench.access$5(Workbench.java:22 95)
>>
>>
>> at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:514)
>>
>>
>> at
>>
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:332)
>>
>> at
>>
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:497)
>>
>> at
>> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:157)
>>
>> at
>> com.turquality.server.rap.Application.createUI(Application.j ava:60)
>>
>> at
>>
org.eclipse.rwt.internal.lifecycle.EntryPointManager.createU I(EntryPointManager.java:92)
>>
>> at
>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.createUI(RWT LifeCycle.java:228)
>>
>> at
>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run(RWTLifeCycle.java:116)
>>
>> at java.lang.Thread.run(Thread.java:636)
>>
>>
>> Exception in thread "UIThread [79F5701409C7E6F2FCF5B12D127B16AD]"
>> java.lang.IllegalStateException: The context has been disposed.
>>
>> at
>>
org.eclipse.rwt.internal.service.ServiceContext.checkState(S erviceContext.java:154)
>>
>> at
>>
org.eclipse.rwt.internal.service.ServiceContext.getRequest(S erviceContext.java:82)
>>
>> at
>>
org.eclipse.rwt.internal.service.ContextProvider.getRequest( ContextProvider.java:129)
>>
>> at
>>
org.eclipse.rwt.internal.service.ContextProvider.getSession( ContextProvider.java:148)
>>
>> at
>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.setShutdownA dapter(RWTLifeCycle.java:345)
>>
>> at
>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.access$0(RWT LifeCycle.java:342)
>>
>> at
>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run(RWTLifeCycle.java:130)
>>
>> at java.lang.Thread.run(Thread.java:636)
>>
>> Any hints?
>>
>> Hasan Ceylan
>>
>> Roberto Sá‡nchez wrote:
>>
>>> Hi Frank, now It works fine, I would like to test it a bit more, but all
>>> seems to be OK.
>>>
>>> Thank you.
>>>
>>> Bye
>>> Roberto.
>>>
>>>
>>> Frank Appel escribió:
>>>> Hi,
>>>>
>>>> please update against the latest CVS versions and tell me whether the
>>>> situation has improved. Sorry for your inconvenience.
>>>>
>>>> Ciao
>>>> Frank
>>>>
>>>>
>>>> "Roberto Sá‡nchez" <roberto@autonomind.com> schrieb im Newsbeitrag
>>>> news:fd0gpg$mt8$1@build.eclipse.org...
>>>>> Hi all, I've found this problem with new CVS updates, When you launch
>>>>> Demo app and close workbench, If you try to refresh page, to entry
>>>>> into application again, an exception is thrown:
>>>>>
>>>>> java.lang.IllegalStateException: The context has been disposed.
>>>>> at
>>>>>
>>
org.eclipse.rwt.internal.service.ServiceContext.checkState(S erviceContext.java:154)
>>>>> at
>>>>>
>>
org.eclipse.rwt.internal.service.ServiceContext.getRequest(S erviceContext.java:82)
>>>>> at
>>>>>
>>
org.eclipse.rwt.internal.service.ContextProvider.getRequest( ContextProvider.java:128)
>>>>> at
>>>>>
>>
org.eclipse.rwt.internal.service.ContextProvider.getSession( ContextProvider.java:147)
>>>>> at
>>>>>
>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycleBlockControl$ ServiceHandlerProcessor.bufferThrowable(RWTLifeCycleBlockCon trol.java:90)
>>>>> at
>>>>>
>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycleBlockControl$ ServiceHandlerProcessor.run(RWTLifeCycleBlockControl.java:70 )
>>>>> at
>>>>>
>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycleThreadPool$Po olRunnable.run(RWTLifeCycleThreadPool.java:38)
>>>>> at
>>>>>
>>
org.eclipse.rwt.internal.lifecycle.RWTLifeCycleThreadPool$Po olWorker.run(RWTLifeCycleThreadPool.java:66)
>>>>>
>>>>> I've created this bug:
>>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=204076 there are several
>>>>> situations when this problem happens.
>>>>>
>>>>> I was waiting for new performance improvements planned for this week,
>>>>> but with this problem I'm blocked, My new application release will
>>>>> have to await.
>>>>>
>>>>> I'm not an expert in RAP Lifecycle but I think that Context should be
>>>>> re-created when Entrypoint is called, but I don't know...
>>>>>
>>>>> Please, a patch/workaround will be welcome.
>>>>>
>>>>> Thanks in advance.
>>>>> Roberto.
>>>>
>>
>>
|
|
|
| Re: Context Disposed Problem [message #128733 is a reply to message #128509] |
Mon, 20 April 2009 09:57 |
Rüdiger Herrmann
Messages: 581
Registered: July 2009 |
Senior Member |
|
|
Hasan,
there is room for improvement regarding the thread-safety of the RAP
startup process. For now, it is safest to run the first request on
its own, wait until it is delivered and only then issue further
requests.
Cheers,
Rüdiger
Hasan Ceylan wrote:
> It looks to me like it has something to do with the long startup.
> We have an OSGI application that has a large hibernate base. I suspect if
> there are more then one request before all the plugins have been activated,
> then this problem occurrs.
>
> Hasan
> Rüdiger Herrmann wrote:
>
>> Hasan,
>>
>> please provide more information on how to reproduce the exception.
>>
>> Cheers,
>> Rüdiger
>>
>> Hasan Ceylan wrote:
>>> Bump...
>>>
>>> Hello,
>>>
>>> We have been experiencing exactly the same problem against 1.2M6 release
>>>
>>> java.lang.IllegalStateException: The context has been disposed.
>>>
>>>
>>> at
>>>
> org.eclipse.rwt.internal.service.ServiceContext.checkState(S erviceContext.java:154)
>>>
>>> at
>>>
> org.eclipse.rwt.internal.service.ServiceContext.getStateInfo (ServiceContext.java:104)
>>>
>>> at
>>>
> org.eclipse.rwt.internal.service.ContextProvider.getStateInf o(ContextProvider.java:166)
>>>
>>> at
>>> org.eclipse.rwt.internal.lifecycle.CurrentPhase.get(CurrentP hase.java:48)
>>>
>>> at
>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.readAndDispa tch(RWTLifeCycle.java:236)
>>>
>>> at
>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :721)
>>>
>>>
>>> at
>>>
> org.eclipse.ui.application.WorkbenchAdvisor.openWindows(Work benchAdvisor.java:807)
>>>
>>> at
>>>
> org.eclipse.ui.internal.Workbench$25.runWithException(Workbe nch.java:1430)
>>>
>>> at
>>>
> org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.java:32)
>>>
>>> at
>>>
> org.eclipse.rwt.internal.lifecycle.UICallBackManager.addSync (UICallBackManager.java:119)
>>>
>>> at org.eclipse.swt.widgets.Display$2.run(Display.java:649)
>>>
>>>
>>> at
>>>
> org.eclipse.rwt.internal.lifecycle.UICallBackServiceHandler. runNonUIThreadWithFakeContext(UICallBackServiceHandler.java: 455)
>>>
>>> at
>>>
> org.eclipse.rwt.lifecycle.UICallBack.runNonUIThreadWithFakeC ontext(UICallBack.java:44)
>>>
>>> at org.eclipse.swt.widgets.Display.syncExec(Display.java:647)
>>>
>>>
>>> at
>>>
> org.eclipse.ui.internal.StartupThreading.runWithoutException s(StartupThreading.java:110)
>>>
>>> at org.eclipse.ui.internal.Workbench.init(Workbench.java:1425)
>>>
>>>
>>> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2404)
>>>
>>>
>>> at
>>> org.eclipse.ui.internal.Workbench.access$5(Workbench.java:22 95)
>>>
>>>
>>> at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:514)
>>>
>>>
>>> at
>>>
> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:332)
>>>
>>> at
>>>
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:497)
>>>
>>> at
>>> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:157)
>>>
>>> at
>>> com.turquality.server.rap.Application.createUI(Application.j ava:60)
>>>
>>> at
>>>
> org.eclipse.rwt.internal.lifecycle.EntryPointManager.createU I(EntryPointManager.java:92)
>>>
>>> at
>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.createUI(RWT LifeCycle.java:228)
>>>
>>> at
>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run(RWTLifeCycle.java:116)
>>>
>>> at java.lang.Thread.run(Thread.java:636)
>>>
>>>
>>> Exception in thread "UIThread [79F5701409C7E6F2FCF5B12D127B16AD]"
>>> java.lang.IllegalStateException: The context has been disposed.
>>>
>>> at
>>>
> org.eclipse.rwt.internal.service.ServiceContext.checkState(S erviceContext.java:154)
>>>
>>> at
>>>
> org.eclipse.rwt.internal.service.ServiceContext.getRequest(S erviceContext.java:82)
>>>
>>> at
>>>
> org.eclipse.rwt.internal.service.ContextProvider.getRequest( ContextProvider.java:129)
>>>
>>> at
>>>
> org.eclipse.rwt.internal.service.ContextProvider.getSession( ContextProvider.java:148)
>>>
>>> at
>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.setShutdownA dapter(RWTLifeCycle.java:345)
>>>
>>> at
>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.access$0(RWT LifeCycle.java:342)
>>>
>>> at
>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run(RWTLifeCycle.java:130)
>>>
>>> at java.lang.Thread.run(Thread.java:636)
>>>
>>> Any hints?
>>>
>>> Hasan Ceylan
>>>
>>> Roberto Sá‡nchez wrote:
>>>
>>>> Hi Frank, now It works fine, I would like to test it a bit more, but all
>>>> seems to be OK.
>>>>
>>>> Thank you.
>>>>
>>>> Bye
>>>> Roberto.
>>>>
>>>>
>>>> Frank Appel escribió:
>>>>> Hi,
>>>>>
>>>>> please update against the latest CVS versions and tell me whether the
>>>>> situation has improved. Sorry for your inconvenience.
>>>>>
>>>>> Ciao
>>>>> Frank
>>>>>
>>>>>
>>>>> "Roberto Sá‡nchez" <roberto@autonomind.com> schrieb im Newsbeitrag
>>>>> news:fd0gpg$mt8$1@build.eclipse.org...
>>>>>> Hi all, I've found this problem with new CVS updates, When you launch
>>>>>> Demo app and close workbench, If you try to refresh page, to entry
>>>>>> into application again, an exception is thrown:
>>>>>>
>>>>>> java.lang.IllegalStateException: The context has been disposed.
>>>>>> at
>>>>>>
> org.eclipse.rwt.internal.service.ServiceContext.checkState(S erviceContext.java:154)
>>>>>> at
>>>>>>
> org.eclipse.rwt.internal.service.ServiceContext.getRequest(S erviceContext.java:82)
>>>>>> at
>>>>>>
> org.eclipse.rwt.internal.service.ContextProvider.getRequest( ContextProvider.java:128)
>>>>>> at
>>>>>>
> org.eclipse.rwt.internal.service.ContextProvider.getSession( ContextProvider.java:147)
>>>>>> at
>>>>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycleBlockControl$ ServiceHandlerProcessor.bufferThrowable(RWTLifeCycleBlockCon trol.java:90)
>>>>>> at
>>>>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycleBlockControl$ ServiceHandlerProcessor.run(RWTLifeCycleBlockControl.java:70 )
>>>>>> at
>>>>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycleThreadPool$Po olRunnable.run(RWTLifeCycleThreadPool.java:38)
>>>>>> at
>>>>>>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycleThreadPool$Po olWorker.run(RWTLifeCycleThreadPool.java:66)
>>>>>> I've created this bug:
>>>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=204076 there are several
>>>>>> situations when this problem happens.
>>>>>>
>>>>>> I was waiting for new performance improvements planned for this week,
>>>>>> but with this problem I'm blocked, My new application release will
>>>>>> have to await.
>>>>>>
>>>>>> I'm not an expert in RAP Lifecycle but I think that Context should be
>>>>>> re-created when Entrypoint is called, but I don't know...
>>>>>>
>>>>>> Please, a patch/workaround will be welcome.
>>>>>>
>>>>>> Thanks in advance.
>>>>>> Roberto.
>>>
>
>
|
|
|
Goto Forum:
Current Time: Tue Mar 28 09:48:16 GMT 2023
Powered by FUDForum. Page generated in 0.01501 seconds |
] 
Search
Help
Register
Login
Home
