Home » Eclipse Projects » Remote Application Platform (RAP) » Hanged sessions
| Hanged sessions [message #660883] |
Tue, 22 March 2011 08:40  |
|
Hi all,
I have some problems with RAP in my productive enviroment.
I'm using RAP 1.2 in productive and 1.3 in test envir.
App server is JBoss 5.1, OS RedHat, java 1.6.0_07
I look at the tomcat status page and i see many hanged sessions, some
with a Callback others without.
See http://ge.tt/3QuToD1
In my test environment I have tried to add the parameter
-Dorg.eclipse.equinox.http.jetty.context.sessioninactiveinte rval=1200
but the sessions aren't invalidated (in test i have only 1 request of
type GET /rap/xlnet?
nocache=1300729646192&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
HTTP/1.1)
Any hints here?
Thank you very much
--
kindly Elvis Dominguez
|
|
| |
| Re: Hanged sessions [message #660891 is a reply to message #660884] |
Tue, 22 March 2011 09:13  |
|
Hi Ivan,
thank you for your response.
I haven't explicit opened a UICallback.
My application is single-sourced with the RCP one.
I have many Jobs and UIJobs for client operations.
I have a JobFactory implemented in my RAP fragment that runs my jobs as
follows http://paste.ubuntu.com/583710/
Kindly
On Tue, 22 Mar 2011 11:00:50 +0200, Ivan Furnadjiev wrote:
> Hi Elvis,
> the blocked UICallBack request will prevent the session from
> invalidation (timeout). This happens if you have a running UICallBack
> all the time (enabled on application start up and never deactivated).
> That's why we suggest to activate the UICallBack only when you really
> needed and deactivate it afterwards.
> HTH,
> Ivan
>
> On 3/22/2011 10:40 AM, Elvis Dominguez wrote:
>> Hi all,
>>
>> I have some problems with RAP in my productive enviroment. I'm using
>> RAP 1.2 in productive and 1.3 in test envir. App server is JBoss 5.1,
>> OS RedHat, java 1.6.0_07
>>
>> I look at the tomcat status page and i see many hanged sessions, some
>> with a Callback others without.
>>
>> See http://ge.tt/3QuToD1
>>
>> In my test environment I have tried to add the parameter
>> -Dorg.eclipse.equinox.http.jetty.context.sessioninactiveinte rval=1200
>>
>> but the sessions aren't invalidated (in test i have only 1 request of
>> type GET /rap/xlnet?
>>
nocache=1300729646192&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
>> HTTP/1.1)
>>
>> Any hints here?
>> Thank you very much
>>
>>
--
kindly Elvis Dominguez
|
|
|
| Re: Hanged sessions [message #660902 is a reply to message #660891] |
Tue, 22 March 2011 09:50 |
 Ivan Furnadjiev
Messages: 2426
Registered: July 2009
Location: Sofia, Bulgaria |
Senior Member |
|
|
Hi Elvis,
could you try with 1.4 M6 too?
Best,
Ivan
On 3/22/2011 11:13 AM, Elvis Dominguez wrote:
> Hi Ivan,
>
> thank you for your response.
> I haven't explicit opened a UICallback.
>
> My application is single-sourced with the RCP one.
> I have many Jobs and UIJobs for client operations.
>
> I have a JobFactory implemented in my RAP fragment that runs my jobs as
> follows http://paste.ubuntu.com/583710/
>
>
> Kindly
>
>
> On Tue, 22 Mar 2011 11:00:50 +0200, Ivan Furnadjiev wrote:
>
>> Hi Elvis,
>> the blocked UICallBack request will prevent the session from
>> invalidation (timeout). This happens if you have a running UICallBack
>> all the time (enabled on application start up and never deactivated).
>> That's why we suggest to activate the UICallBack only when you really
>> needed and deactivate it afterwards.
>> HTH,
>> Ivan
>>
>> On 3/22/2011 10:40 AM, Elvis Dominguez wrote:
>>> Hi all,
>>>
>>> I have some problems with RAP in my productive enviroment. I'm using
>>> RAP 1.2 in productive and 1.3 in test envir. App server is JBoss 5.1,
>>> OS RedHat, java 1.6.0_07
>>>
>>> I look at the tomcat status page and i see many hanged sessions, some
>>> with a Callback others without.
>>>
>>> See http://ge.tt/3QuToD1
>>>
>>> In my test environment I have tried to add the parameter
>>> -Dorg.eclipse.equinox.http.jetty.context.sessioninactiveinte rval=1200
>>>
>>> but the sessions aren't invalidated (in test i have only 1 request of
>>> type GET /rap/xlnet?
>>>
> nocache=1300729646192&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
>>> HTTP/1.1)
>>>
>>> Any hints here?
>>> Thank you very much
>>>
>>>
>
>
>
>
|
|
|
| Re: Hanged sessions [message #660916 is a reply to message #660902] |
Tue, 22 March 2011 10:26 |
|
1.4 is not an option at the moment... :(
It's a productive environment.
Any other hint?
On Tue, 22 Mar 2011 11:50:56 +0200, Ivan Furnadjiev wrote:
> Hi Elvis,
> could you try with 1.4 M6 too?
> Best,
> Ivan
>
> On 3/22/2011 11:13 AM, Elvis Dominguez wrote:
>> Hi Ivan,
>>
>> thank you for your response.
>> I haven't explicit opened a UICallback.
>>
>> My application is single-sourced with the RCP one. I have many Jobs and
>> UIJobs for client operations.
>>
>> I have a JobFactory implemented in my RAP fragment that runs my jobs as
>> follows http://paste.ubuntu.com/583710/
>>
>>
>> Kindly
>>
>>
>> On Tue, 22 Mar 2011 11:00:50 +0200, Ivan Furnadjiev wrote:
>>
>>> Hi Elvis,
>>> the blocked UICallBack request will prevent the session from
>>> invalidation (timeout). This happens if you have a running UICallBack
>>> all the time (enabled on application start up and never deactivated).
>>> That's why we suggest to activate the UICallBack only when you really
>>> needed and deactivate it afterwards.
>>> HTH,
>>> Ivan
>>>
>>> On 3/22/2011 10:40 AM, Elvis Dominguez wrote:
>>>> Hi all,
>>>>
>>>> I have some problems with RAP in my productive enviroment. I'm using
>>>> RAP 1.2 in productive and 1.3 in test envir. App server is JBoss 5.1,
>>>> OS RedHat, java 1.6.0_07
>>>>
>>>> I look at the tomcat status page and i see many hanged sessions, some
>>>> with a Callback others without.
>>>>
>>>> See http://ge.tt/3QuToD1
>>>>
>>>> In my test environment I have tried to add the parameter
>>>> -Dorg.eclipse.equinox.http.jetty.context.sessioninactiveinte rval=1200
>>>>
>>>> but the sessions aren't invalidated (in test i have only 1 request of
>>>> type GET /rap/xlnet?
>>>>
>>
nocache=1300729646192&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
>>>> HTTP/1.1)
>>>>
>>>> Any hints here?
>>>> Thank you very much
>>>>
>>>>
>>>>
>>
>>
>>
--
kindly Elvis Dominguez
|
|
|
| Re: Hanged sessions [message #660919 is a reply to message #660884] |
Tue, 22 March 2011 11:03 |
|
Is there a possibility to set a timeout to this callbacks?
Can i kill this callbacks?
On Tue, 22 Mar 2011 11:00:50 +0200, Ivan Furnadjiev wrote:
> Hi Elvis,
> the blocked UICallBack request will prevent the session from
> invalidation (timeout). This happens if you have a running UICallBack
> all the time (enabled on application start up and never deactivated).
> That's why we suggest to activate the UICallBack only when you really
> needed and deactivate it afterwards.
> HTH,
> Ivan
>
> On 3/22/2011 10:40 AM, Elvis Dominguez wrote:
>> Hi all,
>>
>> I have some problems with RAP in my productive enviroment. I'm using
>> RAP 1.2 in productive and 1.3 in test envir. App server is JBoss 5.1,
>> OS RedHat, java 1.6.0_07
>>
>> I look at the tomcat status page and i see many hanged sessions, some
>> with a Callback others without.
>>
>> See http://ge.tt/3QuToD1
>>
>> In my test environment I have tried to add the parameter
>> -Dorg.eclipse.equinox.http.jetty.context.sessioninactiveinte rval=1200
>>
>> but the sessions aren't invalidated (in test i have only 1 request of
>> type GET /rap/xlnet?
>>
nocache=1300729646192&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
>> HTTP/1.1)
>>
>> Any hints here?
>> Thank you very much
>>
>>
--
kindly Elvis Dominguez
|
|
|
| Re: Hanged sessions [message #660922 is a reply to message #660919] |
Tue, 22 March 2011 11:31 |
Ivan Furnadjiev
Messages: 2426
Registered: July 2009
Location: Sofia, Bulgaria |
Senior Member |
|
|
Hi Elvis,
maybe you ran into this bug:
319224: [UICallback] Hanging UICallback request at startup
https://bugs.eclipse.org/bugs/show_bug.cgi?id=319224
It will be good if you provide a snippet to reliable reproduce this
UICallBack hang. If you have such, please attach it to the bug above.
Thanks,
Ivan
On 3/22/2011 1:03 PM, Elvis Dominguez wrote:
> Is there a possibility to set a timeout to this callbacks?
> Can i kill this callbacks?
>
> On Tue, 22 Mar 2011 11:00:50 +0200, Ivan Furnadjiev wrote:
>
>> Hi Elvis,
>> the blocked UICallBack request will prevent the session from
>> invalidation (timeout). This happens if you have a running UICallBack
>> all the time (enabled on application start up and never deactivated).
>> That's why we suggest to activate the UICallBack only when you really
>> needed and deactivate it afterwards.
>> HTH,
>> Ivan
>>
>> On 3/22/2011 10:40 AM, Elvis Dominguez wrote:
>>> Hi all,
>>>
>>> I have some problems with RAP in my productive enviroment. I'm using
>>> RAP 1.2 in productive and 1.3 in test envir. App server is JBoss 5.1,
>>> OS RedHat, java 1.6.0_07
>>>
>>> I look at the tomcat status page and i see many hanged sessions, some
>>> with a Callback others without.
>>>
>>> See http://ge.tt/3QuToD1
>>>
>>> In my test environment I have tried to add the parameter
>>> -Dorg.eclipse.equinox.http.jetty.context.sessioninactiveinte rval=1200
>>>
>>> but the sessions aren't invalidated (in test i have only 1 request of
>>> type GET /rap/xlnet?
>>>
> nocache=1300729646192&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
>>> HTTP/1.1)
>>>
>>> Any hints here?
>>> Thank you very much
>>>
>>>
>
>
>
>
|
|
|
| Re: Hanged sessions [message #660942 is a reply to message #660922] |
Tue, 22 March 2011 12:46 |
|
Hi Ivan,
i can't reproduce exactly the bug (for now).
it seems a random situation.
the uicallback hanged isn't started at startup... i'm trying to
invenstigate better.
What i can say for sure is that the problem exists in 1.2 and 1.3.
what situations could cause an uicallback?
maybe accessing ui resources in a non-ui job?
can be something i'm doing wrong?
On Tue, 22 Mar 2011 13:31:57 +0200, Ivan Furnadjiev wrote:
> Hi Elvis,
> maybe you ran into this bug:
> 319224: [UICallback] Hanging UICallback request at startup
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=319224 It will be good if
> you provide a snippet to reliable reproduce this UICallBack hang. If you
> have such, please attach it to the bug above. Thanks,
> Ivan
>
> On 3/22/2011 1:03 PM, Elvis Dominguez wrote:
>> Is there a possibility to set a timeout to this callbacks? Can i kill
>> this callbacks?
>>
>> On Tue, 22 Mar 2011 11:00:50 +0200, Ivan Furnadjiev wrote:
>>
>>> Hi Elvis,
>>> the blocked UICallBack request will prevent the session from
>>> invalidation (timeout). This happens if you have a running UICallBack
>>> all the time (enabled on application start up and never deactivated).
>>> That's why we suggest to activate the UICallBack only when you really
>>> needed and deactivate it afterwards.
>>> HTH,
>>> Ivan
>>>
>>> On 3/22/2011 10:40 AM, Elvis Dominguez wrote:
>>>> Hi all,
>>>>
>>>> I have some problems with RAP in my productive enviroment. I'm using
>>>> RAP 1.2 in productive and 1.3 in test envir. App server is JBoss 5.1,
>>>> OS RedHat, java 1.6.0_07
>>>>
>>>> I look at the tomcat status page and i see many hanged sessions, some
>>>> with a Callback others without.
>>>>
>>>> See http://ge.tt/3QuToD1
>>>>
>>>> In my test environment I have tried to add the parameter
>>>> -Dorg.eclipse.equinox.http.jetty.context.sessioninactiveinte rval=1200
>>>>
>>>> but the sessions aren't invalidated (in test i have only 1 request of
>>>> type GET /rap/xlnet?
>>>>
>>
nocache=1300729646192&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
>>>> HTTP/1.1)
>>>>
>>>> Any hints here?
>>>> Thank you very much
>>>>
>>>>
>>>>
>>
>>
>>
--
kindly Elvis Dominguez
|
|
|
| Re: Hanged sessions [message #660952 is a reply to message #660922] |
Tue, 22 March 2011 13:28 |
|
Hi Ivan,
I have news here!
I have hanged a session ;)
I have a File > Exit menu entry created as
ActionFactory.QUIT.create(window);
After doing my tests I select File > Exit and the session hanged with:
709070 ms 0 KB 0 KB 192.168.x.xx server901 GET /rap/
xlnet?
nocache=1300800007775&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
HTTP/1.1
In the broswer after a F5 press i have the following:
org.eclipse.swt.SWTException: Invalid thread access
org.eclipse.swt.SWT.error(SWT.java:3199)
org.eclipse.swt.SWT.error(SWT.java:3119)
org.eclipse.swt.SWT.error(SWT.java:3090)
org.eclipse.swt.widgets.Display.error(Display.java:1616)
org.eclipse.swt.widgets.Display.checkDevice(Display.java:210 1)
org.eclipse.swt.widgets.Display.getBounds(Display.java:260)
org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readB ounds
(DisplayLCA.java:499)
org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readD ata
(DisplayLCA.java:315)
org.eclipse.rwt.internal.lifecycle.ReadData.execute(ReadData .java:26)
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.continueLife Cycle
(RWTLifeCycle.java:223)
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run
(RWTLifeCycle.java:113)
java.lang.Thread.run(Thread.java:619)
org.eclipse.rwt.internal.lifecycle.UIThread.run(UIThread.jav a:102)
On the server:
2011-03-22 14:20:50,521 ERROR [org.apache.catalina.core.ContainerBase.
[jboss.web].[localhost].[/rap].[equinoxbridgeservlet]]
(http-172.30.119.1-8080-18) Servlet.service() for servlet
equinoxbridgeservlet threw exception
org.eclipse.swt.SWTException: Invalid thread access
at org.eclipse.swt.SWT.error(SWT.java:3199)
at org.eclipse.swt.SWT.error(SWT.java:3119)
at org.eclipse.swt.SWT.error(SWT.java:3090)
at org.eclipse.swt.widgets.Display.error(Display.java:1616)
at org.eclipse.swt.widgets.Display.checkDevice(Display.java:210 1)
at org.eclipse.swt.widgets.Display.getBounds(Display.java:260)
at
org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readB ounds
(DisplayLCA.java:499)
at org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readD ata
(DisplayLCA.java:315)
at org.eclipse.rwt.internal.lifecycle.ReadData.execute
(ReadData.java:26)
at
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.continueLife Cycle
(RWTLifeCycle.java:223)
at org.eclipse.rwt.internal.lifecycle.RWTLifeCycle
$UIThreadController.run(RWTLifeCycle.java:113)
at java.lang.Thread.run(Thread.java:619)
at org.eclipse.rwt.internal.lifecycle.UIThread.run
(UIThread.java:102)
Is really required a File > Exit menu entry for RAP clients?
Hope this helps.
On Tue, 22 Mar 2011 13:31:57 +0200, Ivan Furnadjiev wrote:
> Hi Elvis,
> maybe you ran into this bug:
> 319224: [UICallback] Hanging UICallback request at startup
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=319224 It will be good if
> you provide a snippet to reliable reproduce this UICallBack hang. If you
> have such, please attach it to the bug above. Thanks,
> Ivan
>
> On 3/22/2011 1:03 PM, Elvis Dominguez wrote:
>> Is there a possibility to set a timeout to this callbacks? Can i kill
>> this callbacks?
>>
>> On Tue, 22 Mar 2011 11:00:50 +0200, Ivan Furnadjiev wrote:
>>
>>> Hi Elvis,
>>> the blocked UICallBack request will prevent the session from
>>> invalidation (timeout). This happens if you have a running UICallBack
>>> all the time (enabled on application start up and never deactivated).
>>> That's why we suggest to activate the UICallBack only when you really
>>> needed and deactivate it afterwards.
>>> HTH,
>>> Ivan
>>>
>>> On 3/22/2011 10:40 AM, Elvis Dominguez wrote:
>>>> Hi all,
>>>>
>>>> I have some problems with RAP in my productive enviroment. I'm using
>>>> RAP 1.2 in productive and 1.3 in test envir. App server is JBoss 5.1,
>>>> OS RedHat, java 1.6.0_07
>>>>
>>>> I look at the tomcat status page and i see many hanged sessions, some
>>>> with a Callback others without.
>>>>
>>>> See http://ge.tt/3QuToD1
>>>>
>>>> In my test environment I have tried to add the parameter
>>>> -Dorg.eclipse.equinox.http.jetty.context.sessioninactiveinte rval=1200
>>>>
>>>> but the sessions aren't invalidated (in test i have only 1 request of
>>>> type GET /rap/xlnet?
>>>>
>>
nocache=1300729646192&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
>>>> HTTP/1.1)
>>>>
>>>> Any hints here?
>>>> Thank you very much
>>>>
>>>>
>>>>
>>
>>
>>
--
kindly Elvis Dominguez
|
|
|
| Re: Hanged sessions [message #660966 is a reply to message #660952] |
Tue, 22 March 2011 13:55 |
Ivan Furnadjiev
Messages: 2426
Registered: July 2009
Location: Sofia, Bulgaria |
Senior Member |
|
|
Hi Elvis,
this will really help us to debug it. Please file a bugzilla with a
self-running snippet to reproduce it.
Thanks,
Ivan
On 3/22/2011 3:28 PM, Elvis Dominguez wrote:
> Hi Ivan,
>
> I have news here!
> I have hanged a session ;)
>
> I have a File> Exit menu entry created as
> ActionFactory.QUIT.create(window);
>
> After doing my tests I select File> Exit and the session hanged with:
> 709070 ms 0 KB 0 KB 192.168.x.xx server901 GET /rap/
> xlnet?
> nocache=1300800007775&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
> HTTP/1.1
>
> In the broswer after a F5 press i have the following:
> org.eclipse.swt.SWTException: Invalid thread access
> org.eclipse.swt.SWT.error(SWT.java:3199)
> org.eclipse.swt.SWT.error(SWT.java:3119)
> org.eclipse.swt.SWT.error(SWT.java:3090)
> org.eclipse.swt.widgets.Display.error(Display.java:1616)
> org.eclipse.swt.widgets.Display.checkDevice(Display.java:210 1)
> org.eclipse.swt.widgets.Display.getBounds(Display.java:260)
> org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readB ounds
> (DisplayLCA.java:499)
> org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readD ata
> (DisplayLCA.java:315)
> org.eclipse.rwt.internal.lifecycle.ReadData.execute(ReadData .java:26)
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.continueLife Cycle
> (RWTLifeCycle.java:223)
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run
> (RWTLifeCycle.java:113)
> java.lang.Thread.run(Thread.java:619)
> org.eclipse.rwt.internal.lifecycle.UIThread.run(UIThread.jav a:102)
>
> On the server:
> 2011-03-22 14:20:50,521 ERROR [org.apache.catalina.core.ContainerBase.
> [jboss.web].[localhost].[/rap].[equinoxbridgeservlet]]
> (http-172.30.119.1-8080-18) Servlet.service() for servlet
> equinoxbridgeservlet threw exception
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:3199)
> at org.eclipse.swt.SWT.error(SWT.java:3119)
> at org.eclipse.swt.SWT.error(SWT.java:3090)
> at org.eclipse.swt.widgets.Display.error(Display.java:1616)
> at org.eclipse.swt.widgets.Display.checkDevice(Display.java:210 1)
> at org.eclipse.swt.widgets.Display.getBounds(Display.java:260)
> at
> org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readB ounds
> (DisplayLCA.java:499)
> at org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readD ata
> (DisplayLCA.java:315)
> at org.eclipse.rwt.internal.lifecycle.ReadData.execute
> (ReadData.java:26)
> at
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.continueLife Cycle
> (RWTLifeCycle.java:223)
> at org.eclipse.rwt.internal.lifecycle.RWTLifeCycle
> $UIThreadController.run(RWTLifeCycle.java:113)
> at java.lang.Thread.run(Thread.java:619)
> at org.eclipse.rwt.internal.lifecycle.UIThread.run
> (UIThread.java:102)
>
> Is really required a File> Exit menu entry for RAP clients?
>
> Hope this helps.
>
> On Tue, 22 Mar 2011 13:31:57 +0200, Ivan Furnadjiev wrote:
>
>> Hi Elvis,
>> maybe you ran into this bug:
>> 319224: [UICallback] Hanging UICallback request at startup
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=319224 It will be good if
>> you provide a snippet to reliable reproduce this UICallBack hang. If you
>> have such, please attach it to the bug above. Thanks,
>> Ivan
>>
>> On 3/22/2011 1:03 PM, Elvis Dominguez wrote:
>>> Is there a possibility to set a timeout to this callbacks? Can i kill
>>> this callbacks?
>>>
>>> On Tue, 22 Mar 2011 11:00:50 +0200, Ivan Furnadjiev wrote:
>>>
>>>> Hi Elvis,
>>>> the blocked UICallBack request will prevent the session from
>>>> invalidation (timeout). This happens if you have a running UICallBack
>>>> all the time (enabled on application start up and never deactivated).
>>>> That's why we suggest to activate the UICallBack only when you really
>>>> needed and deactivate it afterwards.
>>>> HTH,
>>>> Ivan
>>>>
>>>> On 3/22/2011 10:40 AM, Elvis Dominguez wrote:
>>>>> Hi all,
>>>>>
>>>>> I have some problems with RAP in my productive enviroment. I'm using
>>>>> RAP 1.2 in productive and 1.3 in test envir. App server is JBoss 5.1,
>>>>> OS RedHat, java 1.6.0_07
>>>>>
>>>>> I look at the tomcat status page and i see many hanged sessions, some
>>>>> with a Callback others without.
>>>>>
>>>>> See http://ge.tt/3QuToD1
>>>>>
>>>>> In my test environment I have tried to add the parameter
>>>>> -Dorg.eclipse.equinox.http.jetty.context.sessioninactiveinte rval=1200
>>>>>
>>>>> but the sessions aren't invalidated (in test i have only 1 request of
>>>>> type GET /rap/xlnet?
>>>>>
> nocache=1300729646192&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
>>>>> HTTP/1.1)
>>>>>
>>>>> Any hints here?
>>>>> Thank you very much
>>>>>
>>>>>
>>>>>
>>>
>>>
>
>
>
>
|
|
|
| Re: Hanged sessions [message #660968 is a reply to message #660966] |
Tue, 22 March 2011 14:05 |
|
Ok, Ivan. I'll open a bug and report the number here.
What would you suggest me as workaround?
Removing the File > Exit menu option is good practice?
Can I catch the exception in some manner and avoiding the uicallback hang?
I ask you cause if i have many sessions hanging the server crashes... :(
Kindly
On Tue, 22 Mar 2011 15:55:26 +0200, Ivan Furnadjiev wrote:
> Hi Elvis,
> this will really help us to debug it. Please file a bugzilla with a
> self-running snippet to reproduce it. Thanks,
> Ivan
>
> On 3/22/2011 3:28 PM, Elvis Dominguez wrote:
>> Hi Ivan,
>>
>> I have news here!
>> I have hanged a session ;)
>>
>> I have a File> Exit menu entry created as
>> ActionFactory.QUIT.create(window);
>>
>> After doing my tests I select File> Exit and the session hanged with:
>> 709070 ms 0 KB 0 KB 192.168.x.xx server901 GET /rap/
xlnet?
>>
nocache=1300800007775&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
>> HTTP/1.1
>>
>> In the broswer after a F5 press i have the following:
>> org.eclipse.swt.SWTException: Invalid thread access
>> org.eclipse.swt.SWT.error(SWT.java:3199)
>> org.eclipse.swt.SWT.error(SWT.java:3119)
>> org.eclipse.swt.SWT.error(SWT.java:3090)
>> org.eclipse.swt.widgets.Display.error(Display.java:1616)
>> org.eclipse.swt.widgets.Display.checkDevice(Display.java:210 1)
>> org.eclipse.swt.widgets.Display.getBounds(Display.java:260)
>> org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readB ounds
>> (DisplayLCA.java:499)
>> org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readD ata
>> (DisplayLCA.java:315)
>> org.eclipse.rwt.internal.lifecycle.ReadData.execute(ReadData .java:26)
>> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.continueLife Cycle
>> (RWTLifeCycle.java:223)
>> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run
>> (RWTLifeCycle.java:113)
>> java.lang.Thread.run(Thread.java:619)
>> org.eclipse.rwt.internal.lifecycle.UIThread.run(UIThread.jav a:102)
>>
>> On the server:
>> 2011-03-22 14:20:50,521 ERROR [org.apache.catalina.core.ContainerBase.
>> [jboss.web].[localhost].[/rap].[equinoxbridgeservlet]]
>> (http-172.30.119.1-8080-18) Servlet.service() for servlet
>> equinoxbridgeservlet threw exception
>> org.eclipse.swt.SWTException: Invalid thread access
>> at org.eclipse.swt.SWT.error(SWT.java:3199) at
>> org.eclipse.swt.SWT.error(SWT.java:3119) at
>> org.eclipse.swt.SWT.error(SWT.java:3090) at
>> org.eclipse.swt.widgets.Display.error(Display.java:1616) at
>> org.eclipse.swt.widgets.Display.checkDevice(Display.java:210 1) at
>> org.eclipse.swt.widgets.Display.getBounds(Display.java:260) at
>> org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readB ounds
>> (DisplayLCA.java:499)
>> at org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readD ata
>> (DisplayLCA.java:315)
>> at org.eclipse.rwt.internal.lifecycle.ReadData.execute
>> (ReadData.java:26)
>> at
>> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.continueLife Cycle
>> (RWTLifeCycle.java:223)
>> at org.eclipse.rwt.internal.lifecycle.RWTLifeCycle
>> $UIThreadController.run(RWTLifeCycle.java:113)
>> at java.lang.Thread.run(Thread.java:619) at
>> org.eclipse.rwt.internal.lifecycle.UIThread.run
>> (UIThread.java:102)
>>
>> Is really required a File> Exit menu entry for RAP clients?
>>
>> Hope this helps.
>>
>> On Tue, 22 Mar 2011 13:31:57 +0200, Ivan Furnadjiev wrote:
>>
>>> Hi Elvis,
>>> maybe you ran into this bug:
>>> 319224: [UICallback] Hanging UICallback request at startup
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=319224 It will be good
>>> if you provide a snippet to reliable reproduce this UICallBack hang.
>>> If you have such, please attach it to the bug above. Thanks, Ivan
>>>
>>> On 3/22/2011 1:03 PM, Elvis Dominguez wrote:
>>>> Is there a possibility to set a timeout to this callbacks? Can i kill
>>>> this callbacks?
>>>>
>>>> On Tue, 22 Mar 2011 11:00:50 +0200, Ivan Furnadjiev wrote:
>>>>
>>>>> Hi Elvis,
>>>>> the blocked UICallBack request will prevent the session from
>>>>> invalidation (timeout). This happens if you have a running
>>>>> UICallBack all the time (enabled on application start up and never
>>>>> deactivated). That's why we suggest to activate the UICallBack only
>>>>> when you really needed and deactivate it afterwards.
>>>>> HTH,
>>>>> Ivan
>>>>>
>>>>> On 3/22/2011 10:40 AM, Elvis Dominguez wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> I have some problems with RAP in my productive enviroment. I'm
>>>>>> using RAP 1.2 in productive and 1.3 in test envir. App server is
>>>>>> JBoss 5.1, OS RedHat, java 1.6.0_07
>>>>>>
>>>>>> I look at the tomcat status page and i see many hanged sessions,
>>>>>> some with a Callback others without.
>>>>>>
>>>>>> See http://ge.tt/3QuToD1
>>>>>>
>>>>>> In my test environment I have tried to add the parameter
>>>>>> -
Dorg.eclipse.equinox.http.jetty.context.sessioninactiveinter val=1200
>>>>>>
>>>>>> but the sessions aren't invalidated (in test i have only 1 request
>>>>>> of type GET /rap/xlnet?
>>>>>>
>>
nocache=1300729646192&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
>>>>>> HTTP/1.1)
>>>>>>
>>>>>> Any hints here?
>>>>>> Thank you very much
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>
>>
>>
--
kindly Elvis Dominguez
|
|
|
| Re: Hanged sessions [message #660977 is a reply to message #660968] |
Tue, 22 March 2011 14:24 |
Ivan Furnadjiev
Messages: 2426
Registered: July 2009
Location: Sofia, Bulgaria |
Senior Member |
|
|
Elvis, without an investigation of the problem I couldn't say anything.
But for a good investigation we need a way to reproduce it :-)
Best,
Ivan
On 3/22/2011 4:05 PM, Elvis Dominguez wrote:
> Ok, Ivan. I'll open a bug and report the number here.
> What would you suggest me as workaround?
>
> Removing the File> Exit menu option is good practice?
> Can I catch the exception in some manner and avoiding the uicallback hang?
>
> I ask you cause if i have many sessions hanging the server crashes... :(
>
> Kindly
>
>
> On Tue, 22 Mar 2011 15:55:26 +0200, Ivan Furnadjiev wrote:
>
>> Hi Elvis,
>> this will really help us to debug it. Please file a bugzilla with a
>> self-running snippet to reproduce it. Thanks,
>> Ivan
>>
>> On 3/22/2011 3:28 PM, Elvis Dominguez wrote:
>>> Hi Ivan,
>>>
>>> I have news here!
>>> I have hanged a session ;)
>>>
>>> I have a File> Exit menu entry created as
>>> ActionFactory.QUIT.create(window);
>>>
>>> After doing my tests I select File> Exit and the session hanged with:
>>> 709070 ms 0 KB 0 KB 192.168.x.xx server901 GET /rap/
> xlnet?
> nocache=1300800007775&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
>>> HTTP/1.1
>>>
>>> In the broswer after a F5 press i have the following:
>>> org.eclipse.swt.SWTException: Invalid thread access
>>> org.eclipse.swt.SWT.error(SWT.java:3199)
>>> org.eclipse.swt.SWT.error(SWT.java:3119)
>>> org.eclipse.swt.SWT.error(SWT.java:3090)
>>> org.eclipse.swt.widgets.Display.error(Display.java:1616)
>>> org.eclipse.swt.widgets.Display.checkDevice(Display.java:210 1)
>>> org.eclipse.swt.widgets.Display.getBounds(Display.java:260)
>>> org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readB ounds
>>> (DisplayLCA.java:499)
>>> org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readD ata
>>> (DisplayLCA.java:315)
>>> org.eclipse.rwt.internal.lifecycle.ReadData.execute(ReadData .java:26)
>>> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.continueLife Cycle
>>> (RWTLifeCycle.java:223)
>>> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run
>>> (RWTLifeCycle.java:113)
>>> java.lang.Thread.run(Thread.java:619)
>>> org.eclipse.rwt.internal.lifecycle.UIThread.run(UIThread.jav a:102)
>>>
>>> On the server:
>>> 2011-03-22 14:20:50,521 ERROR [org.apache.catalina.core.ContainerBase.
>>> [jboss.web].[localhost].[/rap].[equinoxbridgeservlet]]
>>> (http-172.30.119.1-8080-18) Servlet.service() for servlet
>>> equinoxbridgeservlet threw exception
>>> org.eclipse.swt.SWTException: Invalid thread access
>>> at org.eclipse.swt.SWT.error(SWT.java:3199) at
>>> org.eclipse.swt.SWT.error(SWT.java:3119) at
>>> org.eclipse.swt.SWT.error(SWT.java:3090) at
>>> org.eclipse.swt.widgets.Display.error(Display.java:1616) at
>>> org.eclipse.swt.widgets.Display.checkDevice(Display.java:210 1) at
>>> org.eclipse.swt.widgets.Display.getBounds(Display.java:260) at
>>> org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readB ounds
>>> (DisplayLCA.java:499)
>>> at org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readD ata
>>> (DisplayLCA.java:315)
>>> at org.eclipse.rwt.internal.lifecycle.ReadData.execute
>>> (ReadData.java:26)
>>> at
>>> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.continueLife Cycle
>>> (RWTLifeCycle.java:223)
>>> at org.eclipse.rwt.internal.lifecycle.RWTLifeCycle
>>> $UIThreadController.run(RWTLifeCycle.java:113)
>>> at java.lang.Thread.run(Thread.java:619) at
>>> org.eclipse.rwt.internal.lifecycle.UIThread.run
>>> (UIThread.java:102)
>>>
>>> Is really required a File> Exit menu entry for RAP clients?
>>>
>>> Hope this helps.
>>>
>>> On Tue, 22 Mar 2011 13:31:57 +0200, Ivan Furnadjiev wrote:
>>>
>>>> Hi Elvis,
>>>> maybe you ran into this bug:
>>>> 319224: [UICallback] Hanging UICallback request at startup
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=319224 It will be good
>>>> if you provide a snippet to reliable reproduce this UICallBack hang.
>>>> If you have such, please attach it to the bug above. Thanks, Ivan
>>>>
>>>> On 3/22/2011 1:03 PM, Elvis Dominguez wrote:
>>>>> Is there a possibility to set a timeout to this callbacks? Can i kill
>>>>> this callbacks?
>>>>>
>>>>> On Tue, 22 Mar 2011 11:00:50 +0200, Ivan Furnadjiev wrote:
>>>>>
>>>>>> Hi Elvis,
>>>>>> the blocked UICallBack request will prevent the session from
>>>>>> invalidation (timeout). This happens if you have a running
>>>>>> UICallBack all the time (enabled on application start up and never
>>>>>> deactivated). That's why we suggest to activate the UICallBack only
>>>>>> when you really needed and deactivate it afterwards.
>>>>>> HTH,
>>>>>> Ivan
>>>>>>
>>>>>> On 3/22/2011 10:40 AM, Elvis Dominguez wrote:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I have some problems with RAP in my productive enviroment. I'm
>>>>>>> using RAP 1.2 in productive and 1.3 in test envir. App server is
>>>>>>> JBoss 5.1, OS RedHat, java 1.6.0_07
>>>>>>>
>>>>>>> I look at the tomcat status page and i see many hanged sessions,
>>>>>>> some with a Callback others without.
>>>>>>>
>>>>>>> See http://ge.tt/3QuToD1
>>>>>>>
>>>>>>> In my test environment I have tried to add the parameter
>>>>>>> -
> Dorg.eclipse.equinox.http.jetty.context.sessioninactiveinter val=1200
>>>>>>> but the sessions aren't invalidated (in test i have only 1 request
>>>>>>> of type GET /rap/xlnet?
>>>>>>>
> nocache=1300729646192&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
>>>>>>> HTTP/1.1)
>>>>>>>
>>>>>>> Any hints here?
>>>>>>> Thank you very much
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>
>>>
>
>
>
>
|
|
|
| Re: Hanged sessions [message #661126 is a reply to message #660884] |
Wed, 23 March 2011 09:31 |
|
Hi Ivan,
I have resolved my issue :D (therefore virtually marking this thread as
[SOLVED]!)
I try to explain here as reference (sorry for bad english).
My single-sourced app is based on persectives (one function is a
perspective, i.ex. customers management is a perspective, orders
management another and so on).
The user switches perspectives using menu items.
The standard éperspective switcher is disabled.
Before opening the requested perspective I save and close the perspective
using the method:
(...).getActiveWorkbenchWindow().getActivePage().close()
This throwed an exception (cannot dispose active part, if i correctly
remember) that I have always ignored (blame on me).
That situation caused another exception when closing the application, the
Widget disposed too early exception (always ignored too).
In RAP that caused the UICallback to hang infinitely.
Ihave changed the 'Switch perspective action' in
(...).getActiveWorkbenchWindow().getActivePage().closeAllPer spectives
(true,true);
and now I haven't exceptions in switching perspective nor exiting from my
app, thus no uicallback hanging there.
HTH someone else, thank you Ivan for your time
Kindly
Elvis Dominguez
On Tue, 22 Mar 2011 11:00:50 +0200, Ivan Furnadjiev wrote:
> Hi Elvis,
> the blocked UICallBack request will prevent the session from
> invalidation (timeout). This happens if you have a running UICallBack
> all the time (enabled on application start up and never deactivated).
> That's why we suggest to activate the UICallBack only when you really
> needed and deactivate it afterwards.
> HTH,
> Ivan
>
> On 3/22/2011 10:40 AM, Elvis Dominguez wrote:
>> Hi all,
>>
>> I have some problems with RAP in my productive enviroment. I'm using
>> RAP 1.2 in productive and 1.3 in test envir. App server is JBoss 5.1,
>> OS RedHat, java 1.6.0_07
>>
>> I look at the tomcat status page and i see many hanged sessions, some
>> with a Callback others without.
>>
>> See http://ge.tt/3QuToD1
>>
>> In my test environment I have tried to add the parameter
>> -Dorg.eclipse.equinox.http.jetty.context.sessioninactiveinte rval=1200
>>
>> but the sessions aren't invalidated (in test i have only 1 request of
>> type GET /rap/xlnet?
>>
nocache=1300729646192&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
>> HTTP/1.1)
>>
>> Any hints here?
>> Thank you very much
>>
>>
--
kindly Elvis Dominguez
|
|
|
| Re: Hanged sessions [message #661152 is a reply to message #660883] |
Wed, 23 March 2011 11:29 |
|
After some test I have always the problem...
I have opened a bug #340742
https://bugs.eclipse.org/bugs/show_bug.cgi?id=340742
with an example project.
Waiting your comments ;)
Thank you, kindly
On Tue, 22 Mar 2011 08:40:55 +0000, Elvis Dominguez wrote:
> Hi all,
>
> I have some problems with RAP in my productive enviroment. I'm using RAP
> 1.2 in productive and 1.3 in test envir. App server is JBoss 5.1, OS
> RedHat, java 1.6.0_07
>
> I look at the tomcat status page and i see many hanged sessions, some
> with a Callback others without.
>
> See http://ge.tt/3QuToD1
>
> In my test environment I have tried to add the parameter
> -Dorg.eclipse.equinox.http.jetty.context.sessioninactiveinte rval=1200
>
> but the sessions aren't invalidated (in test i have only 1 request of
> type GET /rap/xlnet?
>
nocache=1300729646192&custom_service_handler=org.eclipse .rwt.internal.lifecycle.UICallBackServiceHandler
> HTTP/1.1)
>
> Any hints here?
> Thank you very much
--
kindly Elvis Dominguez
|
|
|
Goto Forum:
Current Time: Sat Apr 20 01:34:25 GMT 2024
Powered by FUDForum. Page generated in 0.03729 seconds |
] 
Search
Help
Register
Login
Home
