Re: I'm using jdk1.6 + tomcat 7.0.23
Can you put my E-mail account deleted from the mailing list, thank you！ 2015-06-11 12:42 GMT+08:00 chedana jayasinghe chedanajayasin...@gmail.com: 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
Re: I'm using jdk1.6 + tomcat 7.0.23
On Saturday, June 20, 2015 11:17 PM, hao huang huanghao...@gmail.com wrote: Can you put my E-mail account deleted from the mailing list, thank you Hao, as indicated here: Apache Tomcat - Mailing Lists you should send a blank email to users-unsubscr...@tomcat.apache.org to unsubscribe from the Tomcat users list. - Bob
Re: I'm using jdk1.6 + tomcat 7.0.23
Chris,
I really appreciate your quick responses.
In the servlet it just calls some values through request.getParameter( )
and then it binds an array variable of a sychronized method that's all.
below is the whole filter class
public class UTF8Filter implements Filter{
public void destroy() {}
public void doFilter(ServletRequest request, ServletResponse response,
FilterChain chain)throws IOException, ServletException{
request.setCharacterEncoding(UTF-8);
chain.doFilter(request, response);
}
public void init(FilterConfig filterConfig) throws ServletException {}
}
On Thu, Jun 18, 2015 at 9:24 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
-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
Re: I'm using jdk1.6 + tomcat 7.0.23
-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
Re: I'm using jdk1.6 + tomcat 7.0.23
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 . On Tue, Jun 16, 2015 at 12:39 AM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 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 -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVfyMBAAoJEBzwKT+lPKRYXsYP/0osrijFMEDL4HW/H6zZiCyC brpPG5HCLr9BT8zNGzj9r4iMCp10w8smTtQDbpyX73UNKfxKtX119myJLDuoJOlV nYv3UCn5g8apNwylFGl59KSCtmpytW1kNinP0D/iQWhUdnbDOZnWczlGW6QupNr0 I4+NTizUu7t77Ba60uLM78jf2R2J1ujRL4+epXXS0IKPuOmUvU8AJWWQtbXwS+Wu JbAw1OYpffcHJSNZWLYTB4q9NKE3of65Cs4LPAHtJ8lOlauhLiYC1Qc2jjMeiWlu Ho0FKyCvkns2Rqay/wqJrmhJJNfeAwtvAhMQIz8PbY5jPl2FF8YAvaCju6/17LyC uOVVHyoUhmvF4LdOS55ut7XO+LE0pTQzwOoN5kKk4opsomHLd32icBFzrQU+TH3b Pa3MTJKONIocoh/DNSA0dVvTaGeeGDDdwEmcjZHfPPHY57IZEmqtLsCuVUlf4m7Q xNWa9+Yoas53Oe4T/S2s3FnPiH3kT3bS1MCqaXDQwUcVc+BwpcsBWkCdgsJxn7DC 3zzLrEB/Wiw+xdQhYIhIKwUytV5HLPU1wwZzqFgIJqnVfzx/keSbXwsszkk2TUz8 iRx2yGdy8bxAkYncTJKd/0hBwKcVm/kz2AKQYYo1txITRORP+Wu+c8xwhlNIQuS9 dhvquvV3qsoJ8H1xZvEu =oyiY -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: I'm using jdk1.6 + tomcat 7.0.23
Christopher, *Is there a big change of how tomcat manage sessions, in versions before tomcat 6. still I'm little confused about the behavior of my application * On Thu, Jun 18, 2015 at 11:39 AM, chedana jayasinghe chedanajayasin...@gmail.com 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 . On Tue, Jun 16, 2015 at 12:39 AM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 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 -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVfyMBAAoJEBzwKT+lPKRYXsYP/0osrijFMEDL4HW/H6zZiCyC brpPG5HCLr9BT8zNGzj9r4iMCp10w8smTtQDbpyX73UNKfxKtX119myJLDuoJOlV nYv3UCn5g8apNwylFGl59KSCtmpytW1kNinP0D/iQWhUdnbDOZnWczlGW6QupNr0 I4+NTizUu7t77Ba60uLM78jf2R2J1ujRL4+epXXS0IKPuOmUvU8AJWWQtbXwS+Wu JbAw1OYpffcHJSNZWLYTB4q9NKE3of65Cs4LPAHtJ8lOlauhLiYC1Qc2jjMeiWlu Ho0FKyCvkns2Rqay/wqJrmhJJNfeAwtvAhMQIz8PbY5jPl2FF8YAvaCju6/17LyC uOVVHyoUhmvF4LdOS55ut7XO+LE0pTQzwOoN5kKk4opsomHLd32icBFzrQU+TH3b Pa3MTJKONIocoh/DNSA0dVvTaGeeGDDdwEmcjZHfPPHY57IZEmqtLsCuVUlf4m7Q xNWa9+Yoas53Oe4T/S2s3FnPiH3kT3bS1MCqaXDQwUcVc+BwpcsBWkCdgsJxn7DC 3zzLrEB/Wiw+xdQhYIhIKwUytV5HLPU1wwZzqFgIJqnVfzx/keSbXwsszkk2TUz8 iRx2yGdy8bxAkYncTJKd/0hBwKcVm/kz2AKQYYo1txITRORP+Wu+c8xwhlNIQuS9 dhvquvV3qsoJ8H1xZvEu =oyiY -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: I'm using jdk1.6 + tomcat 7.0.23
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: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 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 -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVeY0sAAoJEBzwKT+lPKRYm+EP/jSazTxJiLm3oAMbZjiLaHuw W3KLkJlaSZnbLEbUYxZuXjzZTCNcYtDSwLN9lH4GoLMjtyPJ1w8kF+zhl3KNslV5 lY8FgX+5+pDQAbTktvazTdH7fHRDPFSGzwh1TU0O79U2ylPLLnbsZjbkEFKPS+xN J7JcoMTeZUVDmjtDAV5rritWBtnM+BoYT1P1DAvGHbb/LK3aansZLyhsUT3Bs4Mq z7sROsd8qANrUXcq5nN8tU+AJVuQ4OWUSuCZ56CrU80Dl+ebvhEPBWaQvved7n0E h2cozrNV34Ru6P788xFNO2wgw4YXEbYoHLpZbPxMwKhQM8104TRpwRNKOBAck1ad TrdZe6jIKl4Uq25A7n6s3e8PQJ5/kj795LYgaHCtDMaYNXZhGP6p3XVGEXrI4Tbh agNY1g/4sQrgI0FaGaoIhrl8FwAKxeqn+sp7XU/FbxIEmB0NRPPFJQSSGfQVTFVm 5AgjE01t8VbvCUo9NNpYkbZFBvskh+d/wulJfXHDoEMIlaFhHRsv+WkEwp7PTZOQ 6TecTlOY5X6t/pke4Yk84GtS5RH6Lpd7C9+45rrBPR9Ew4/qJf/c9oWp2gzu9S99 icAmQTcKmSOz4kCMxE4eGCPTQwQXfYkWPvoDlp6WuXusKOicRI90LXlHeA7+oeNg X2or96Uy6Io+PIn3WtmW =QmEw -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: I'm using jdk1.6 + tomcat 7.0.23
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 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 -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVfyMBAAoJEBzwKT+lPKRYXsYP/0osrijFMEDL4HW/H6zZiCyC brpPG5HCLr9BT8zNGzj9r4iMCp10w8smTtQDbpyX73UNKfxKtX119myJLDuoJOlV nYv3UCn5g8apNwylFGl59KSCtmpytW1kNinP0D/iQWhUdnbDOZnWczlGW6QupNr0 I4+NTizUu7t77Ba60uLM78jf2R2J1ujRL4+epXXS0IKPuOmUvU8AJWWQtbXwS+Wu JbAw1OYpffcHJSNZWLYTB4q9NKE3of65Cs4LPAHtJ8lOlauhLiYC1Qc2jjMeiWlu Ho0FKyCvkns2Rqay/wqJrmhJJNfeAwtvAhMQIz8PbY5jPl2FF8YAvaCju6/17LyC uOVVHyoUhmvF4LdOS55ut7XO+LE0pTQzwOoN5kKk4opsomHLd32icBFzrQU+TH3b Pa3MTJKONIocoh/DNSA0dVvTaGeeGDDdwEmcjZHfPPHY57IZEmqtLsCuVUlf4m7Q xNWa9+Yoas53Oe4T/S2s3FnPiH3kT3bS1MCqaXDQwUcVc+BwpcsBWkCdgsJxn7DC 3zzLrEB/Wiw+xdQhYIhIKwUytV5HLPU1wwZzqFgIJqnVfzx/keSbXwsszkk2TUz8 iRx2yGdy8bxAkYncTJKd/0hBwKcVm/kz2AKQYYo1txITRORP+Wu+c8xwhlNIQuS9 dhvquvV3qsoJ8H1xZvEu =oyiY -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: I'm using jdk1.6 + tomcat 7.0.23
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 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 -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVeY0sAAoJEBzwKT+lPKRYm+EP/jSazTxJiLm3oAMbZjiLaHuw W3KLkJlaSZnbLEbUYxZuXjzZTCNcYtDSwLN9lH4GoLMjtyPJ1w8kF+zhl3KNslV5 lY8FgX+5+pDQAbTktvazTdH7fHRDPFSGzwh1TU0O79U2ylPLLnbsZjbkEFKPS+xN J7JcoMTeZUVDmjtDAV5rritWBtnM+BoYT1P1DAvGHbb/LK3aansZLyhsUT3Bs4Mq z7sROsd8qANrUXcq5nN8tU+AJVuQ4OWUSuCZ56CrU80Dl+ebvhEPBWaQvved7n0E h2cozrNV34Ru6P788xFNO2wgw4YXEbYoHLpZbPxMwKhQM8104TRpwRNKOBAck1ad TrdZe6jIKl4Uq25A7n6s3e8PQJ5/kj795LYgaHCtDMaYNXZhGP6p3XVGEXrI4Tbh agNY1g/4sQrgI0FaGaoIhrl8FwAKxeqn+sp7XU/FbxIEmB0NRPPFJQSSGfQVTFVm 5AgjE01t8VbvCUo9NNpYkbZFBvskh+d/wulJfXHDoEMIlaFhHRsv+WkEwp7PTZOQ 6TecTlOY5X6t/pke4Yk84GtS5RH6Lpd7C9+45rrBPR9Ew4/qJf/c9oWp2gzu9S99 icAmQTcKmSOz4kCMxE4eGCPTQwQXfYkWPvoDlp6WuXusKOicRI90LXlHeA7+oeNg X2or96Uy6Io+PIn3WtmW =QmEw -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
I'm using jdk1.6 + tomcat 7.0.23
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
