Session expired message

> Hi all,
>
>
>
> We have integrated orbeon with our Java app via a separate deployment
> scheme.  Our users log into our site, and we set the JSESSIONID cookie to
> expire in 1 year, to make it more convenient for our users so they don’t
> have to log in each time after they close their browser.  Sometimes however,
> our users log in and get a “Session has expired. Unable to process incoming
> request” message from the xforms.  This usually lasts until they clear their
> cookies so they can’t do anything until then.
>
>
>
> Does anyone know why this is occurring?  I’ve read that due to this
> heartbeat thing, orbeon shouldn’t be losing track of the sessions, but it
> seems like it is.   It only started occurring when we decided to up the
> cookie’s expiration time from its default (when browser closes).
>
>
>
> Any help would be greatly appreciated!
>
>
>
> Thanks,
>
> Stephanie
>
> --
> You receive this message as a subscriber of the [hidden email] mailing
> list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

> Hi all,
>
>
>
> We have integrated orbeon with our Java app via a separate deployment
> scheme.  Our users log into our site, and we set the JSESSIONID cookie
> to expire in 1 year, to make it more convenient for our users so they
> don't have to log in each time after they close their browser.  
> Sometimes however, our users log in and get a "Session has expired.
> Unable to process incoming request" message from the xforms.  This
> usually lasts until they clear their cookies so they can't do anything until then.
>
>
>
> Does anyone know why this is occurring?  I've read that due to this
> heartbeat thing, orbeon shouldn't be losing track of the sessions, but
> it seems like it is.   It only started occurring when we decided to up
> the cookie's expiration time from its default (when browser closes).
>
>
>
> Any help would be greatly appreciated!
>
>
>
> Thanks,
>
> Stephanie
>
> --
> You receive this message as a subscriber of the [hidden email]
> mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

> Hi Erik,
>
> The application server is tomcat 5.5 on windows. Initially I tried setting the expiration of any cookies we found in the response.getCookies(), but that didn't seem to help the issue either.
>
> Thanks,
> Stephanie
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Erik Bruchez
> Sent: Monday, November 15, 2010 6:11 PM
> To: [hidden email]
> Subject: [ops-users] Re: Session expired message
>
> Stephanie,
>
> That might depend on the app server.
>
> In separate deployment, there might be internally two sessions: one per webapp. Do you configure expiration for both?
>
> -Erik
>
> On Wed, Nov 10, 2010 at 11:49 AM, Stephanie Hall (TT) <[hidden email]> wrote:
>> Hi all,
>>
>>
>>
>> We have integrated orbeon with our Java app via a separate deployment
>> scheme.  Our users log into our site, and we set the JSESSIONID cookie
>> to expire in 1 year, to make it more convenient for our users so they
>> don't have to log in each time after they close their browser.
>> Sometimes however, our users log in and get a "Session has expired.
>> Unable to process incoming request" message from the xforms.  This
>> usually lasts until they clear their cookies so they can't do anything until then.
>>
>>
>>
>> Does anyone know why this is occurring?  I've read that due to this
>> heartbeat thing, orbeon shouldn't be losing track of the sessions, but
>> it seems like it is.   It only started occurring when we decided to up
>> the cookie's expiration time from its default (when browser closes).
>>
>>
>>
>> Any help would be greatly appreciated!
>>
>>
>>
>> Thanks,
>>
>> Stephanie
>>
>> --
>> You receive this message as a subscriber of the [hidden email]
>> mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> OW2 mailing lists service home page: http://www.ow2.org/wws
>>
>>
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

> Hi Erik,
>
> The application server is tomcat 5.5 on windows. Initially I tried setting the expiration of any cookies we found in the response.getCookies(), but that didn't seem to help the issue either.
>
> Thanks,
> Stephanie
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Erik
> Bruchez
> Sent: Monday, November 15, 2010 6:11 PM
> To: [hidden email]
> Subject: [ops-users] Re: Session expired message
>
> Stephanie,
>
> That might depend on the app server.
>
> In separate deployment, there might be internally two sessions: one per webapp. Do you configure expiration for both?
>
> -Erik
>
> On Wed, Nov 10, 2010 at 11:49 AM, Stephanie Hall (TT) <[hidden email]> wrote:
>> Hi all,
>>
>>
>>
>> We have integrated orbeon with our Java app via a separate deployment
>> scheme.  Our users log into our site, and we set the JSESSIONID
>> cookie to expire in 1 year, to make it more convenient for our users
>> so they don't have to log in each time after they close their browser.
>> Sometimes however, our users log in and get a "Session has expired.
>> Unable to process incoming request" message from the xforms.  This
>> usually lasts until they clear their cookies so they can't do anything until then.
>>
>>
>>
>> Does anyone know why this is occurring?  I've read that due to this
>> heartbeat thing, orbeon shouldn't be losing track of the sessions,
>> but it seems like it is.   It only started occurring when we decided
>> to up the cookie's expiration time from its default (when browser closes).
>>
>>
>>
>> Any help would be greatly appreciated!
>>
>>
>>
>> Thanks,
>>
>> Stephanie
>>
>> --
>> You receive this message as a subscriber of the [hidden email]
>> mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> OW2 mailing lists service home page: http://www.ow2.org/wws
>>
>>
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

> Hi Erik,
>
> Yes, they are the same - 1 year.
>
> Thanks,
> Stephanie
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Erik Bruchez
> Sent: Friday, November 26, 2010 4:31 AM
> To: [hidden email]
> Subject: [ops-users] Re: RE: Re: Session expired message
>
> But what about the duration of the session in both web apps? Did you set a specific duration for both of them, for example in the web.xml of your web app as well as the Orbeon Forms web app?
>
> -Erik
>
> On Tue, Nov 16, 2010 at 3:47 PM, Stephanie Hall (TT) <[hidden email]> wrote:
>> Hi Erik,
>>
>> The application server is tomcat 5.5 on windows. Initially I tried setting the expiration of any cookies we found in the response.getCookies(), but that didn't seem to help the issue either.
>>
>> Thanks,
>> Stephanie
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]] On Behalf Of Erik
>> Bruchez
>> Sent: Monday, November 15, 2010 6:11 PM
>> To: [hidden email]
>> Subject: [ops-users] Re: Session expired message
>>
>> Stephanie,
>>
>> That might depend on the app server.
>>
>> In separate deployment, there might be internally two sessions: one per webapp. Do you configure expiration for both?
>>
>> -Erik
>>
>> On Wed, Nov 10, 2010 at 11:49 AM, Stephanie Hall (TT) <[hidden email]> wrote:
>>> Hi all,
>>>
>>>
>>>
>>> We have integrated orbeon with our Java app via a separate deployment
>>> scheme.  Our users log into our site, and we set the JSESSIONID
>>> cookie to expire in 1 year, to make it more convenient for our users
>>> so they don't have to log in each time after they close their browser.
>>> Sometimes however, our users log in and get a "Session has expired.
>>> Unable to process incoming request" message from the xforms.  This
>>> usually lasts until they clear their cookies so they can't do anything until then.
>>>
>>>
>>>
>>> Does anyone know why this is occurring?  I've read that due to this
>>> heartbeat thing, orbeon shouldn't be losing track of the sessions,
>>> but it seems like it is.   It only started occurring when we decided
>>> to up the cookie's expiration time from its default (when browser closes).
>>>
>>>
>>>
>>> Any help would be greatly appreciated!
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Stephanie
>>>
>>> --
>>> You receive this message as a subscriber of the [hidden email]
>>> mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> OW2 mailing lists service home page: http://www.ow2.org/wws
>>>
>>>
>>
>>
>> --
>> You receive this message as a subscriber of the [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> OW2 mailing lists service home page: http://www.ow2.org/wws
>>
>>
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>