|
| Re: Session Issues [message #47461 is a reply to message #47371] |
Tue, 18 September 2007 06:57   |
Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
we are currently doing some internal work for performance and memory
optimizations - maybe we did cause this problem. we will check that. Does
the stacktrace ends at window.close or is there some more information about
who is closing the window?
Ciao
Frank
"Roberto S
|
|
|
| Re: Session Issues [message #47521 is a reply to message #47461] |
Tue, 18 September 2007 07:17 |
 Roberto Sanchez
Messages: 82
Registered: July 2009 |
Member |
|
|
Hi Frank, this is the exact StackTrace, I got reproduce it when I call
/rap and then /rap=startup=controls:
org.eclipse.swt.SWTException: Invalid thread access
at org.eclipse.swt.SWT.error(SWT.java:704)
at org.eclipse.swt.SWT.error(SWT.java:650)
at org.eclipse.swt.SWT.error(SWT.java:646)
at org.eclipse.swt.widgets.Widget.error(Widget.java:725)
at org.eclipse.swt.widgets.Widget.dispose(Widget.java:557)
at org.eclipse.jface.window.Window.close(Window.java:321)
at
org.eclipse.jface.window.ApplicationWindow.close(Application Window.java:287)
at
org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchW indow.java:1512)
at
org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchW indow.java:610)
at
org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWi ndow.java:586)
at org.eclipse.ui.internal.WorkbenchWindow$2.run(WorkbenchWindo w.java:701)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:66)
at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindo w.java:699)
at org.eclipse.jface.window.WindowManager.close(WindowManager.j ava:106)
at org.eclipse.ui.internal.Workbench$10.run(Workbench.java:830)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:8 27)
at org.eclipse.ui.internal.Workbench.access$6(Workbench.java:75 1)
at org.eclipse.ui.internal.Workbench$14.run(Workbench.java:1010 )
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:66)
at org.eclipse.ui.internal.Workbench.close(Workbench.java:1008)
at org.eclipse.ui.internal.Workbench.close(Workbench.java:979)
at org.eclipse.ui.internal.Workbench$2.run(Workbench.java:93)
at
org.eclipse.rwt.internal.lifecycle.UICallBackServiceHandler. runNonUIThreadWithFakeContext(UICallBackServiceHandler.java: 409)
at
org.eclipse.ui.internal.Workbench$ShutdownHandler.beforeDest roy(Workbench.java:97)
at
org.eclipse.rwt.internal.service.SessionStoreImpl.valueUnbou nd(SessionStoreImpl.java:130)
at
org.mortbay.jetty.servlet.AbstractSessionManager$Session.unb indValue(AbstractSessionManager.java:923)
at
org.mortbay.jetty.servlet.AbstractSessionManager$Session.rem oveAttribute(AbstractSessionManager.java:843)
at
org.eclipse.equinox.http.servlet.internal.HttpSessionAdaptor .removeAttribute(HttpSessionAdaptor.java:87)
at
org.eclipse.rwt.internal.service.LifeCycleServiceHandler.cle arSession(LifeCycleServiceHandler.java:227)
at
org.eclipse.rwt.internal.service.LifeCycleServiceHandler.che ckRequest(LifeCycleServiceHandler.java:215)
at
org.eclipse.rwt.internal.service.LifeCycleServiceHandler.int ernalService(LifeCycleServiceHandler.java:173)
at
org.eclipse.rwt.internal.service.LifeCycleServiceHandler.acc ess$1(LifeCycleServiceHandler.java:170)
at
org.eclipse.rwt.internal.service.LifeCycleServiceHandler$Lif eCycleServiceHandlerSync.doService(LifeCycleServiceHandler.j ava:135)
at
org.eclipse.rwt.internal.lifecycle.RWTLifeCycleServiceHandle rSync.access$1(RWTLifeCycleServiceHandlerSync.java:1)
at
org.eclipse.rwt.internal.lifecycle.RWTLifeCycleServiceHandle rSync$ServiceRunnable.run(RWTLifeCycleServiceHandlerSync.jav a:71)
at java.lang.Thread.run(Thread.java:613)
Cheers.
Roberto.
Frank Appel escribió:
> Hi,
>
> we are currently doing some internal work for performance and memory
> optimizations - maybe we did cause this problem. we will check that. Does
> the stacktrace ends at window.close or is there some more information about
> who is closing the window?
>
> Ciao
> Frank
>
>
> "Roberto Sá‡nchez" <roberto@autonomind.com> schrieb im Newsbeitrag
> news:fcmerf$66s$1@build.eclipse.org...
>> Hello, with latest changes about session behaviour, sometimes, when I
>> change between entrypoints this error appears on console (This problem
>> also occurs in DEMO App, changing between /tea and /rap servlets ):
>>
>> org.eclipse.swt.SWTException: Invalid thread access
>> at org.eclipse.swt.SWT.error(SWT.java:704)
>> at org.eclipse.swt.SWT.error(SWT.java:650)
>> at org.eclipse.swt.SWT.error(SWT.java:646)
>> at org.eclipse.swt.widgets.Widget.error(Widget.java:725)
>> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:557)
>> at org.eclipse.jface.window.Window.close(Window.java:321)
>>
>>
>> I'm not sure about what is the correct way to manage session, should I
>> invalidate it when workbench is closed ? how ?
>>
>> I'm using a class that extends from SessionSingletonBase, How can I remove
>> it from SessionStore ?
>>
>> Regards.
>> Roberto.
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04070 seconds
] 
Search
Help
Register
Login
Home
