-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Chedana,

On 6/18/15 2:09 AM, chedana jayasinghe wrote:
> request goes to a doPost method of a servlet and there it used to
> return some values in the response, and there is a one filter which
> encode request's characters to UTF-8. But how come it effects the
> session last accessed time get updated, because as to my knowledge
> It is monitored by the servlet container and all the filters are
> within the servlet container

I suppose I meant, specifically, how does your servlet (and filters)
interact with the container via the Servlet API. For instance... do
you call getSession()?

> Is there a big change of how tomcat manage sessions, in versions
> before tomcat 6.

Note that I'm aware of.

> still I'm little confused about the behavior of my application

Me, too.

- -chris

> On Tue, Jun 16, 2015 at 12:39 AM, Christopher Schultz < 
> ch...@christopherschultz.net> wrote:
> 
> Chedana,
> 
> On 6/15/15 9:07 AM, chedana jayasinghe wrote:
>>>> Christopher,
>>>> 
>>>> I'm not using "strict servlet compliance", still *I've tried 
>>>> setting *
>>>> org.apache.catalina.core.StandardHostValve.ACCESS_SESSION 
>>>> system property to false in catalina properties but no luck.
>>>> still the problem is same. Javascript heartbeat  keeps the
>>>> session alive only in tomcat 7 and higher versions.
>>>> 
>>>> On Thu, Jun 11, 2015 at 6:59 PM, Christopher Schultz < 
>>>> ch...@christopherschultz.net> wrote:
>>>> 
>>>> Chedana,
>>>> 
>>>> On 6/11/15 12:42 AM, chedana jayasinghe wrote:
>>>>>>> HI, In my web application, in a jsp there is a
>>>>>>> javascript which sends request to a servlet every
>>>>>>> twenty seconds, so it kills my applications user idle
>>>>>>> time tracking by resetting the  lastAccessed time. the
>>>>>>> funny thing is lastAccessed time doesn't get updated in
>>>>>>> tomcat  6 and my applications idle time tracking works
>>>>>>> fine in it, but in 7 it gets updated and kills that
>>>>>>> functionality of the application . so I'm little bit
>>>>>>> confused about the changes in the session tracking of 
>>>>>>> tomcat 6 and tomcat 7
>>>> 
>>>> Are you using "strict servlet compliance"?
>>>> 
>>>> If so, you will want to set the 
>>>> org.apache.catalina.core.StandardHostValve.ACCESS_SESSION
>>>> system property to false and re-try your tests.
>>>> 
>>>> If you are upgrading from Tomcat 6 to Tomcat 7:
>>>> 
>>>> 1. Don't bother going to 7.0.23 (almost 4 years old). Go all
>>>> the way up to 7.0.62.
>>>> 
>>>> 2. You may want to skip Tomcat 7 altogether and go all the
>>>> way up to Tomcat 8.0.23.
>>>> 
>>>> -chris
> 
> What does your application actually do when the heartbeat comes
> in? Don't forget the various Filters that might also be processing
> the request on the way in or out.
> 
> -chris
>> 
>> ---------------------------------------------------------------------
>>
>> 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>> 
>> 
> 
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJVgumsAAoJEBzwKT+lPKRYCJYQAMDcf656uBq+HW8S+5Tg9Kba
FSB1sqVn6YBEQLauojgN7DHRmlQ9U/Z9dWGcvhh8ORq5gxb5V9wHxeuHjvJS8y7a
/jv9wlQdM8wXyDUxDzlBVOkTG+xnsq0EwR6cWJMCnzhx4lxc3p6b/bsQa3pXW6W/
R1C+i1MwI9jS5nkhesn78A+r1VyYL6FvUMTCIm8Ow2GvpbBaJgiY0gyTqpB8vCdG
ynPZ7ThCQNgcO+uUyvjUAIX9y0PSPr9UnIvNhJxeNKpffu+7CEaE1lbLbYkrzzgq
TWmfWSj0NDUluSDyhec24JJz1/8kyv9ehUb3HOC3Pc71byo+1/c+BuHnFu4ic9s3
P6XtrNQ27MAyj88WzlNHQVOcPNMqtbJS+scoqFD1fheG0Ss5Y1StXsveah68l25a
Hjn3GIzAJnoItHovNSh1ohlUKkuJtgLLrga4P3Un3dLPrcaoAevJZ82NcmUAJvR3
pU/oCdNVz9+WltAtTfrBEgauE+FEM6/koF/oqlZHzh0kIMbJ78+u85QHnTSp8CIn
tqP4VFRu4ya2DysrpqudFondIe/VTymwWRvqNgS5FtmSE532PLYAMLW4hdNsDPdx
g/0Sskq4piLSTxSULouEOY4K0QiEzFHuCh/N2vgkKE8TobYG5f8QVwRFEwDvAzR+
l2oqZICA/S+SQHnC0+6s
=wvMS
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to