Re: [rap-dev] Session Timeout immediately with RAP 3.0

[Ralf Sternberg <rsternberg@xxxxxxxxxxxxxxxxx>]

You know that RAP supports multiple tabs since 2.1, don't you? ;-) You
don't have to disable cookies anymore.

Cheers,
Ralf

On Wed, May 6, 2015 at 2:51 PM, Gunnar Wagenknecht
<gunnar@xxxxxxxxxxxxxxx> wrote:
> Apparently I am ....
>
> final HashSessionManager sessionManager = new HashSessionManager();
> sessionManager.setMaxInactiveInterval(1200);
> sessionManager.setUsingCookies(false); // allows to use RAP in multiple tabs
>
> :)
>
> -Gunnar
>
> --
> Gunnar Wagenknecht
> gunnar@xxxxxxxxxxxxxxx, http://guw.io/
>
>
>
>
>
>
>> Am 06.05.2015 um 14:30 schrieb Ralf Sternberg <rsternberg@xxxxxxxxxxxxxxxxx>:
>>
>> Interesting. Did you run Jetty with cookies disabled?
>>
>> On Wed, May 6, 2015 at 12:47 PM, Gunnar Wagenknecht
>> <gunnar@xxxxxxxxxxxxxxx> wrote:
>>> Thanks for the link.
>>>
>>> The behavior I observed looks extremely similar. I would argue it is the same issue. However, I was running with embedded Jetty 9.2.9. Thus, it might indicated that the behavior observed there also applies to Jetty.
>>>
>>> -Gunnar
>>>
>>> --
>>> Gunnar Wagenknecht
>>> gunnar@xxxxxxxxxxxxxxx, http://guw.io/
>>>
>>>
>>>
>>>
>>>
>>>
>>>> Am 06.05.2015 um 11:49 schrieb Ralf Sternberg <rsternberg@xxxxxxxxxxxxxxxxx>:
>>>>
>>>> Thanks for the update Gunnar! Maybe you were running into
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=463467
>>>>
>>>> Cheers,
>>>> Ralf
>>>>
>>>> On Wed, May 6, 2015 at 11:30 AM, Gunnar Wagenknecht
>>>> <gunnar@xxxxxxxxxxxxxxx> wrote:
>>>>> Sorry for the noise. This has been fixed in M7. I was still consuming M6 (because M7 is not added to the composite repo yet).
>>>>>
>>>>> -Gunnar
>>>>>
>>>>> --
>>>>> Gunnar Wagenknecht
>>>>> gunnar@xxxxxxxxxxxxxxx, http://guw.io/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Am 06.05.2015 um 11:07 schrieb Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>:
>>>>>>
>>>>>> Greetings RAP Committers,
>>>>>>
>>>>>> I migrated from 2.3 to 3.0 today. There weren't any compile errors because we weren't using deprecated apis anymore. :) However, my application now does not come up anymore. Immediately after navigating to it in the browser I get the "The server session timed out." dialog from RAP. Any ideas what change in 3.0 could be triggering that?
>>>>>>
>>>>>> Note, I'm not using the workbench but ApplicationRunner and RWTServlet directly. The app should not be running in SWT Compatibility mode.
>>>>>>
>>>>>> -Gunnar
>>>>>>
>>>>>> --
>>>>>> Gunnar Wagenknecht
>>>>>> gunnar@xxxxxxxxxxxxxxx, http://guw.io/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> rap-dev mailing list
>>>>> rap-dev@xxxxxxxxxxx
>>>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>>>> https://dev.eclipse.org/mailman/listinfo/rap-dev
>>>> _______________________________________________
>>>> rap-dev mailing list
>>>> rap-dev@xxxxxxxxxxx
>>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>>> https://dev.eclipse.org/mailman/listinfo/rap-dev
>>>
>>> _______________________________________________
>>> rap-dev mailing list
>>> rap-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/rap-dev
>> _______________________________________________
>> rap-dev mailing list
>> rap-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/rap-dev
>
> _______________________________________________
> rap-dev mailing list
> rap-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/rap-dev