Tribes mcast address
Hi all, I'm implementing Tribes in my project. In the server xml I have the following cluster configuration: Cluster className=org.apache.cataline.ha.tcp.SimpleTcpCluster Channel className=org.apache.cataline.tribes.group.GroupChannel Membership className=org.apache.cataline.tribes.membership.McastService address=230.0.0.5/ /Channel /Cluster In the application I instance the Channel as following: Channel channel = new GroupChannel(); channel.addChannelListener(myClistener); channel.addMembershipListener(myMSlistener); channel.start(Channel.DEFAULT) And send messages as: channel.send( channel.getMembers(), message, Channel.SEND_OPTIONS_DEFAULT); What I don't understand is that the Channel is instantiated correctly but the default mcast address is applied (228.0.0.4) instead of the configured one (in the server.xml) As workaround I'm setting explicitly at runtime my desired address, but I'd like to configure this address in one place (server.xml). Any hint? Thank you -- Elvis Dominguez el...@oasinformatica.ch OASI informatica s.a. Via Carvina 5 6807 Taverne Switzerland Web: http://www.oasinformatica.ch Tel: +41 91 945 4630 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Settings when SSL terminates on the front-end
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jeffrey,
On 6/17/15 2:08 PM, Jeffrey Janner wrote:
I’ve been deploying letting Tomcat do it all when it came to
connectors and SSL, with the app forcing everything to SSL in the
security-constraints section. Now I’m setting up a haproxy
front-end that will both terminate the SSL and take care of the
redirect from HTTP to HTTPS for me and tomcat only running a
standard HTTP port on 8080.
So my question is, Is it still important for the app to know that
it operating “secure”, and if so, what settings are a must?
I would say that Tomcat knowing that it's in secure mode is
important. If for no other reason than the URLs your webapp generates
ought to be sensitive to the protocol being used.
Here is the old setup:
SERVER.XML:
Service name=Catalina
Connector address=${IP_ADDRESS} port=80
maxHttpHeaderSize=8192
maxThreads=50 enableLookups=false redirectPort=443
acceptCount=100
connectionTimeout=2 disableUploadTimeout=true
compression=on
compressableMimeType=text/html,text/xml,text/plain,text/css,text/csv,
text/javascript,text/rtf,text/richtext
/
Connector address=${IP_ADDRESS} port=443
maxHttpHeaderSize=8192
maxThreads=150 enableLookups=false acceptCount=100
connectionTimeout=2 disableUploadTimeout=true
compression=on
compressableMimeType=text/html,text/xml,text/plain,text/css,text/csv,
text/javascript,text/rtf,text/richtext
scheme=https secure=true SSLEnabled=true
If you are still going to connect haproxy - Tomcat using port 443,
then this configuration should still work. Tomcat will be in secure
mode, but you won't have access to the original SSL information, at
least not directly in the usual ways.
Here is the new setup:
SERVER.XML:
Service name=Catalina
Connector port=${tomcatPort} protocol=HTTP/1.1
connectionTimeout=2
redirectPort=8443 /
You should probably set protocol=https and secure=true. You don't
need redirectPort if this is the connector that handles incoming
connections from haproxy.
- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCAAGBQJVgs6iAAoJEBzwKT+lPKRYM2sQAKej40Cx4Wfc54ZJaHH7qRaC
c4cgV/fJqh4ylB8LBsmwIUO1N9SSavIiDQLc04816OfKw69Jg3CBh6vK0qyDhN0+
l8guZV51AyHgwRPewZ3n79zwWRFeJ9tjhAKC39DOo2URZcTPpwVcTJL3UN1OuouV
FWYbw9kufe0gZsmonrI8ki2Tj1m+PZ1LcBdsSMFSCGFKVVSPuR41UuoJ+GZCG6WZ
bLUyMQ3k0pPBdQ0CUXYUHHafddHCiVZzY/r1rC05zyVZ+z9X0LL0Q91okbo8TUvh
BrQOM7Qt5qBqJV4P+Bb+CtMEyAj9cIK1OJZpAaWVdlBIddiOXimkEh6JNWBToCdo
k3WjmMWQ4CDDIzBoycGOq8Jax8hR8U3Gbiae9/2nuBRTUtaSqw7ijiO9xqMrZ6gT
MzW0vKzp1+seo7UEejBucWRDu/s2LNoHTc410BTBI4KQlko3mNbrI0eDAwVR8/I8
i2PiCLRGbo2l/uPvsoJ6/fj33BUM1zxwGimIssYVZqW8b3AFsDTktoO437KRfiOw
9crNPP0FYzsE6lMrrdn7V560hVRqxoqfX3cfIqp09fJXEjOdpI/75UREihiOSv9L
CqjbrY2YUtb4Lt/DK7j2En5ZBMTF6iChn8YbulrZYzXwkTM20k2Nj8irM1SfUc/E
Q0TgwYeow6Kf3Geb1yyM
=xBvF
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: logging input and output HTTP message payload
Hi Christopher, On 06/18/2015 05:55 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frederik, On 6/17/15 8:10 AM, Frederik Nosi wrote: It helps only with HTTP though, no HTTPS or at least not easily. All you need is the server's TLS key and Wireshark will look directly at the HTTP conversation. This is a skill worth developing, especially since it takes such little effort. Been there done that, with mildly recent versions of openssl / https (PFS) you cant do that: https://ask.wireshark.org/questions/34393/how-to-decrypt-ssl-traffic-using-wireshark - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVguoGAAoJEBzwKT+lPKRYp/IP/jlJ8sLXsf0hxL/NE/dZmE/h rq4kFb3/9itszwJnL7vnaQHetml+JZNAk7fsCvk8wGx4JIX/aYVpmmyJ+A1KsQ+Q 1nZeJ2uSef6iTEtYsypMxUasabguc8LI7KG0QMRyBYSLICcbp/36SLgJmUVLCuvw ErClKJIlFDetd7r0dUuBIvlixThQ0emSOPRAgutNauiUCb2m6CCFAnFWmmW7Z01/ yLV+AUGHp3b77Yq3jJlKGtlmNmTuJ/tdnY0N7VwYlnA644DkUpetykFZZ/pdLa5p wYRHXz5qv/tmVT383SAeK3FgSVYIp9EnxVHs44ImZ42XwCnkoHLK9TdzjkS6Cxrs WHQJcP6vfSWQ7WIGLNpJzUclEkCaJRCLktGcA8SE4aNIg0JvVe2Y25RVWOdYX//E RHiZxrDJxctoK6zmTuCOpd7DFx1cxSp2s1xXfghl80lFouMryoqwL7vui8/V/8u/ PsxT6/kupsTFTGoTv1RvJdk0rPVhrQnpHneOpQcKyoH/1lJoTswO8j7T6suLACqL /K1HCVO8E+tu49Mn5bsr9rUb0uUo/qtYUu/cPp4Pv6CkNxLxYw48T1t82HSGkQHr g7qCt1aWltsfc6O6yx07Zfdair8Hvy/QmOifcnpWlHn01wF6phSjrXhN3t5M7pnt ScsjQVvlQoi7ATLm+4/a =f8p5 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: logging input and output HTTP message payload
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Milinda, On 6/17/15 5:10 AM, Milinda Perera wrote: I need to log HTTP payload content for debugging purposes. Following are my findings: 1. Using HTTP message content Access Log Valve [1] and Extended Access Log Valve [2] But it does not provide functionality to log HTTP payload 2. Then I tried by changing *org.apache.coyote.level=FINE* With this it logs the entire HTTP request (header + payload). But does not log response Since in my 2nd method it logged the request, Is it possible to log response also? http://markmail.org/thread/fumpfuspt7a3nesz - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVguqpAAoJEBzwKT+lPKRYBjgP/jHRe/l712AgiJ8xiEmeuwHn GaDVYK/RaZ0xEnsgFjCyFPDJnji3fa7T11BuklL1sEnQV+7QovdSEfYstu6yij+M WIQah/h+fOI4xytp8/vO6AvAah0lBUKJMuGPzJYfUUugGE7w293uzyL15BIUpGM1 WFvbsUMGQO07i2mTnoK60CY7dfiDau9CBALqTZDWBxNofYGj4kSXgT5qhQsc8eUI x0CMVNUUeYNUL62e+OXYzYbAzMUAG1zkXVbZsP/IajXLHFLpxHcxwu++oTg+Pode SwemM50ABQYqx4k0iTnR9UJHZeq4WcLhXzd7q9e4chL4OTo3KytFxb1s9FV6p96X WT6JWG2riBN86vVDnL8w4FeK6ORV/vAtfwHNxHUv+HQNd5AcE/Ls0H019yhK3UC1 OEneSe2tQyPOucTOuQLCn3z5b2AjflRcdJqtJxUH71mc5fzKawDMKHLY93ilIf2N 3QXW/PiI8cK97z+4oTqVKozwcaKckWFV67VQEcyXReIdf1SAUOjiOW0hhCPrqNLi zu6+2EOzODgTgGsLM0ca4vAwFb035Um91dpxXC+l0LaVtdjnCGbKlaqpHiwBnehz 3KibFSzYr2D0qcY5eAPFDUEMmZGv1Rg7fi7vuruoXQll7Iu1hsLONfeaH0l434mO anlb6DLXYOWBPdhJpqqD =stly -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: logging input and output HTTP message payload
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frederik, On 6/17/15 8:10 AM, Frederik Nosi wrote: It helps only with HTTP though, no HTTPS or at least not easily. All you need is the server's TLS key and Wireshark will look directly at the HTTP conversation. This is a skill worth developing, especially since it takes such little effort. - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVguoGAAoJEBzwKT+lPKRYp/IP/jlJ8sLXsf0hxL/NE/dZmE/h rq4kFb3/9itszwJnL7vnaQHetml+JZNAk7fsCvk8wGx4JIX/aYVpmmyJ+A1KsQ+Q 1nZeJ2uSef6iTEtYsypMxUasabguc8LI7KG0QMRyBYSLICcbp/36SLgJmUVLCuvw ErClKJIlFDetd7r0dUuBIvlixThQ0emSOPRAgutNauiUCb2m6CCFAnFWmmW7Z01/ yLV+AUGHp3b77Yq3jJlKGtlmNmTuJ/tdnY0N7VwYlnA644DkUpetykFZZ/pdLa5p wYRHXz5qv/tmVT383SAeK3FgSVYIp9EnxVHs44ImZ42XwCnkoHLK9TdzjkS6Cxrs WHQJcP6vfSWQ7WIGLNpJzUclEkCaJRCLktGcA8SE4aNIg0JvVe2Y25RVWOdYX//E RHiZxrDJxctoK6zmTuCOpd7DFx1cxSp2s1xXfghl80lFouMryoqwL7vui8/V/8u/ PsxT6/kupsTFTGoTv1RvJdk0rPVhrQnpHneOpQcKyoH/1lJoTswO8j7T6suLACqL /K1HCVO8E+tu49Mn5bsr9rUb0uUo/qtYUu/cPp4Pv6CkNxLxYw48T1t82HSGkQHr g7qCt1aWltsfc6O6yx07Zfdair8Hvy/QmOifcnpWlHn01wF6phSjrXhN3t5M7pnt ScsjQVvlQoi7ATLm+4/a =f8p5 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: logging input and output HTTP message payload
Some more info, On 06/18/2015 06:00 PM, Frederik Nosi wrote: Hi Christopher, On 06/18/2015 05:55 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frederik, On 6/17/15 8:10 AM, Frederik Nosi wrote: It helps only with HTTP though, no HTTPS or at least not easily. All you need is the server's TLS key and Wireshark will look directly at the HTTP conversation. This is a skill worth developing, especially since it takes such little effort. Been there done that, with mildly recent versions of openssl / https (PFS) you cant do that: https://ask.wireshark.org/questions/34393/how-to-decrypt-ssl-traffic-using-wireshark Till some years ago I used tihs technique for troubleshooting. But after a webserver upgrade or such, i found that this was no more possible (i'm noit going into details now). So the quick and dirty way i had to use was with apache mod_bumpio, or strace -fe trace=network -s 1024 -p `pidof tomcat`, you got the idea. With another product i had to put a HTTP/HTTPS proxy in the middle. That's why i said it's not so quick :-) - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVguoGAAoJEBzwKT+lPKRYp/IP/jlJ8sLXsf0hxL/NE/dZmE/h rq4kFb3/9itszwJnL7vnaQHetml+JZNAk7fsCvk8wGx4JIX/aYVpmmyJ+A1KsQ+Q 1nZeJ2uSef6iTEtYsypMxUasabguc8LI7KG0QMRyBYSLICcbp/36SLgJmUVLCuvw ErClKJIlFDetd7r0dUuBIvlixThQ0emSOPRAgutNauiUCb2m6CCFAnFWmmW7Z01/ yLV+AUGHp3b77Yq3jJlKGtlmNmTuJ/tdnY0N7VwYlnA644DkUpetykFZZ/pdLa5p wYRHXz5qv/tmVT383SAeK3FgSVYIp9EnxVHs44ImZ42XwCnkoHLK9TdzjkS6Cxrs WHQJcP6vfSWQ7WIGLNpJzUclEkCaJRCLktGcA8SE4aNIg0JvVe2Y25RVWOdYX//E RHiZxrDJxctoK6zmTuCOpd7DFx1cxSp2s1xXfghl80lFouMryoqwL7vui8/V/8u/ PsxT6/kupsTFTGoTv1RvJdk0rPVhrQnpHneOpQcKyoH/1lJoTswO8j7T6suLACqL /K1HCVO8E+tu49Mn5bsr9rUb0uUo/qtYUu/cPp4Pv6CkNxLxYw48T1t82HSGkQHr g7qCt1aWltsfc6O6yx07Zfdair8Hvy/QmOifcnpWlHn01wF6phSjrXhN3t5M7pnt ScsjQVvlQoi7ATLm+4/a =f8p5 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
SSL configuration using PFX as keystore
Hi there,
I'm trying to get the above working using Tomcat 8.0, previously working with
7.0. This is part of a WebDAV connector in Confluence.
It seems I can connect from anything other than a Windows Mini Redirector
client (Windows 7 or 8.1, x86 or x64). Using a web browser or 3rd party client
(CyberDuck for instance) connects OK.
There are some registry keys in Windows one needs to enable to get this working
first:
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\Internet]
BasicAuthLevel=dword:0001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters]
BasicAuthLevel=dword:0001
UseBasicAuth=dword:0001
Server.xml
Connector port=9443 maxHttpHeaderSize=8192
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
protocol=org.apache.coyote.http11.Http11NioProtocol
enableLookups=false disableUploadTimeout=true
acceptCount=100 scheme=https secure=true
clientAuth=false sslProtocols=TLS SSLEnabled=true
URIEncoding=UTF-8
keystoreType=PKCS12
keystoreFile=${catalina.base}/conf/certname.pfx
keystorePass=keypassword/
I'm fairly new to this, but have done a fair bit of reading to get it working
previously in Tomcat7...so any help would be greatly appreciated.
Kind regards
Michael Salisbury
Senior Systems Architect | P 07 960 7011 | E
mich...@skypoint.co.nzmailto:mich...@skypoint.co.nz | W skypoint.co.nz
Waikato Innovation Park, Ruakura Rd, PO Box 9466, Hamilton 3240, NZ
[cid:image001.png@01CF0265.772EC520]
Please send any support enquiries to E
supp...@skypoint.co.nzmailto:supp...@skypoint.co.nz
[MCSA_2013(rgb)_14802] [HP Accredited Technical Professional]
回覆︰ Tomcat 8 webapp failed to start on Windows reboot
Hi Chris, Christopher Schultz ch...@christopherschultz.net 於 2015年06月19日 (週五) 3:16 AM 寫道﹕ -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 James, On 6/18/15 4:56 AM, James Cheung wrote: Environment --- Tomcat 8.0.21 x64 bit, JDK 8u31, Windows 2008 R2 x64 bit Problem --- After upgrading from tomcat 7.0.42 to 8.0.21, my webapp(gih-ws) failed to startup every time the machine is rebooted. In the tomcat catalina log, it did not show any error, but in my webapp(gih-ws) access log, it showed below error. ERROR 08 6月 2015 03:20:39,329 (AxisEngine.java:219) -[]- The service cannot be found for the endpoint reference (EPR) /gih-ws/services/GIH3Service/keywordSearchWithIndex?maxNoOfResult=11k eyword=North%20Point%20Government%20OfficesstartIndex=0response=applic ation%2Fjsonlang=enextent=839266.674348%2C816651.312098%2C839765.32565 2%2C817436.687902 org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /gih-ws/services/GIH3Service/keywordSearchWithIndex?maxNoOfResult=11k eyword=North%20Point%20Government%20OfficesstartIndex=0response=applic ation%2Fjsonlang=enextent=839266.674348%2C816651.312098%2C839765.32565 2%2C817436.687902 at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhas e.java:78) This looks like you are trying to call a web service that does not exist. Is the gih-ws service failing to start because it can't access a remote web service, or is the local Axis service logging that the gih-ws service hasn't been deployed? We didn't make change to the web servcie. They worked fine before our upgrade. at org.apache.axis2.engine.Phase.invoke(Phase.java:329) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168) at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUti l.java:144) at org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUt il.java:139) at org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.proce ssURLRequest(AxisServlet.java:837) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:273 ) at javax.servlet.http.HttpServlet.service(HttpServlet.java:622) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli cationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFi lterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli cationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFi lterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVa lve.java:219) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextVa lve.java:106) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticat orBase.java:502) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.ja va:142) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.ja va:79) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAcces sLogValve.java:610) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv e.java:88) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java :518) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp1 1Processor.java:1091) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(A bstractProtocol.java:668) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.pro cess(Http11AprProtocol.java:283) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoi nt.java:2463) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint .java:2452) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j ava:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThr ead.java:61) at java.lang.Thread.run(Thread.java:745) Our finding --- We stopped the tomcat 8 service and then started it again and the webapp(gih-ws) can startup and there was no error in the gih-ws access log. It is so weird. Is there any tomcat 8 service startup issue every time the machine is rebooted? Should we start the Tomcat 8 service in Startup(Delayed) mode? I also include below tomcat catalina log for your reference. Thanks. Tomcat catalina log --- 10-Jun-2015 10:04:20.250 INFO [Thread-25] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
Re: Tomcat 8 webapp failed to start on Windows reboot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 James, On 6/18/15 4:56 AM, James Cheung wrote: Environment --- Tomcat 8.0.21 x64 bit, JDK 8u31, Windows 2008 R2 x64 bit Problem --- After upgrading from tomcat 7.0.42 to 8.0.21, my webapp(gih-ws) failed to startup every time the machine is rebooted. In the tomcat catalina log, it did not show any error, but in my webapp(gih-ws) access log, it showed below error. ERROR 08 6月 2015 03:20:39,329 (AxisEngine.java:219) -[]- The service cannot be found for the endpoint reference (EPR) /gih-ws/services/GIH3Service/keywordSearchWithIndex?maxNoOfResult=11k eyword=North%20Point%20Government%20OfficesstartIndex=0response=applic ation%2Fjsonlang=enextent=839266.674348%2C816651.312098%2C839765.32565 2%2C817436.687902 org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /gih-ws/services/GIH3Service/keywordSearchWithIndex?maxNoOfResult=11k eyword=North%20Point%20Government%20OfficesstartIndex=0response=applic ation%2Fjsonlang=enextent=839266.674348%2C816651.312098%2C839765.32565 2%2C817436.687902 at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhas e.java:78) This looks like you are trying to call a web service that does not exist. Is the gih-ws service failing to start because it can't access a remote web service, or is the local Axis service logging that the gih-ws service hasn't been deployed? at org.apache.axis2.engine.Phase.invoke(Phase.java:329) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168) at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUti l.java:144) at org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUt il.java:139) at org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.proce ssURLRequest(AxisServlet.java:837) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:273 ) at javax.servlet.http.HttpServlet.service(HttpServlet.java:622) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli cationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFi lterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli cationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFi lterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVa lve.java:219) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextVa lve.java:106) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticat orBase.java:502) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.ja va:142) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.ja va:79) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAcces sLogValve.java:610) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv e.java:88) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java :518) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp1 1Processor.java:1091) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(A bstractProtocol.java:668) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.pro cess(Http11AprProtocol.java:283) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoi nt.java:2463) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint .java:2452) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j ava:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThr ead.java:61) at java.lang.Thread.run(Thread.java:745) Our finding --- We stopped the tomcat 8 service and then started it again and the webapp(gih-ws) can startup and there was no error in the gih-ws access log. It is so weird. Is there any tomcat 8 service startup issue every time the machine is rebooted? Should we start the Tomcat 8 service in Startup(Delayed) mode? I also include below tomcat catalina log for your reference. Thanks. Tomcat catalina log --- 10-Jun-2015 10:04:20.250 INFO [Thread-25] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler [http-apr-9090] 10-Jun-2015 10:04:20.313 INFO [Thread-25] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler [http-bio-9443] 10-Jun-2015 10:04:20.375 INFO [Thread-25] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler [ajp-apr-8009] 10-Jun-2015 10:04:20.437 INFO
Re: FormAuthenticator, Tomcat restart
Thank you, Christopher!
On Thu, Jun 11, 2015 at 4:34 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Leonid,
On 6/11/15 4:18 AM, Leonid Rozenblyum wrote:
Hello. Just to double-check. By writing own login-handler, do you
mean, overriding FormAuthenticator.authenticate() (looks risky
since it's a big method which can change from one to another Tomcat
version)?
Or are there more painless ways to inject such custom login
handler?
On Thu, May 28, 2015 at 6:49 PM, Christopher Schultz
ch...@christopherschultz.net wrote: Mark,
On 5/28/15 5:29 AM, Mark Thomas wrote:
On 28/05/2015 10:22, Leonid Rozenblyum wrote:
Hello experts.
We are using FormAuthenticator and face a following issue:
1) Session persistence is disabled 2) User is on login page
3) Restart Tomcat 4) User tries authentication
He receives error 400 or 408.
While digging deeper we discovered that in this case
Tomcat validates session id and if it's old/invalid -
prevents logging-in even though valid credentials are
passed.
We tried landingPage solution - it looks better than error
400/408 but anyway it forces user to enter credentials
twice (or we don't know how to pass credentials to
landingPage implicitly).
We think that an improvement of user experience would be :
FormAuthenticator: 255 if (session == null) { session =
request.getSessionInternal(false); }
== if (session == null) { session =
request.getSessionInternal(true); }
So if session is invalid or missing - simply create it.
Does this idea make sense?
No. It makes no sense at all.
Can we achieve the goal of not forcing user entering
credentials twice without changes in Tomcat ?
No. The credentials are stored in the session. If you
restart Tomcat with session persistence disabled those
credentials are lost and the user is going to have to
re-enter them.
I think the OP is saying that the credentials are only entered a
single time. The Tomcat restart between showing and submitting the
login page is the source of the problem.
Leonid, the servlet spec is very clear about the workflow for
authentication: the client must request a protected resource, then
the container challenges the client for authentication (shows the
login page), and then the client must submit valid credentials
(send a request to j_security_check). After that, the container
must re-process the client's original request with the
newly-authenticated principal.
Tomcat stores the original request in the session. If you lose
your session between presenting the login page and submitting the
credentials, Tomcat has no way to re-process the original request.
IMO, this is a hole in the spec, because it doesn't allow people
to login simply because they want to; instead, they must first
attempt to reach a protected resource.
If you want your users to be able to login without requesting a
protected resource, you may write your own login-handler and call
ServletRequest.login(). That way, you won't require a session to
exist during that whole workflow.
-chris
No, I was suggesting that you write your own servlet or filter that
handles your logins. Instead of pointing your login form at
/j_security_check, you point it at /your/login/servlet and then call
Request.login() yourself. That way, you can decide what to do if the
session has timed-out in the meantime.
Note that you are opening-up a large can of worms by doing this. You
will be introducing lots of other problems that you will have to solve.
You might want to check out securityfilter, a project that is quite
long in the tooth, but somewhat gracefully handles situations like
this. It has its own set of awkward things you'll have to deal with
(like not being able to authenticate against Tomcat's realms, for
instance).
[One of these days, I'm going to get off my butt and update that project
.]
- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCAAGBQJVeY5OAAoJEBzwKT+lPKRYdpkQAJ4BGgPNJWU34mAKo0YljHBN
rAeIjl4gn4k+xU7mHwWH3h45hgCQVh+iCkqjH7rbgeGI1/IqETJcK2lXoXk/B+ZY
VjmMjh+fqRsUZG/UoP2T3cvrqCs0tl1Sm17WzJOLePYNNuowQVbmFznl4GAVoKsI
yRFYz7fPD4nXiS7+endkdVPGEn1sYSCQP5+EyVUNIlvqwOb9PN3bAlDSczidVHCN
oDgSrOvE9SGC88igS8sLW3NiWXPYqXVeI1YiX46S5AC/1JApFPzdVhYsbgvRUegG
k1EPo0YusG1jtBLj6fsqz6bsXZSIGchjZf2hwm/rrrpWdxJnKNAds8FRJ8Gfz43w
uJWRXZtwpBYXdl1btBLUlCHTUTUPkQZDqcT2pktmtAK7tDCQm7BA8x4cibRwztMI
QstMMgPjdjhS4ChuCcfEPoNzKNVDMDDH4pdjHj8hXE/b7PA7BSjRGtZIAvu0ZYZc
RauQUnsTGMzQyNeDAZBCqMhAxQO42B82Yu0cpMTVHqRDw5uEJq2+bhgzi7slJOMO
jLFxVT/k6DNdTG8+Z7eEfvaZXkf11o4arRGOH3gzZLtzPZgJQ3pDJ9gjKkvpcc4F
FzTTDDkMRuZG2J8VHrAKqf2VGNcqIgmdEKPMtKde4A3xJDtv7CGZLLhksneBLLAU
bsPyxrRr5sFycwffd/9k
=tRmm
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail:
Re: redirect to website not working
Ankur Gupta wrote: Thank you for your help... xx.xxx.xx.81 server through which iam using ie is not accessed to public website.This might be the problem. I want to ask a noob question that is there any method , as 81 server is not accessed to public websites but Linux server has access , so any method,way so that request can be sent to public website through Linux server . Linux server can be accessed through 81 server only. I have to use 81 server ie to request public website SMS sender vendor through Linux server. Yes, there exist ways to do that. But they are not simple to set up, and it would make the diagnostic of future problems much more complicated. It can also introduce security issues. In other words, this is not really noob level. For information only, here is information about how it's done : http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxyrequests But read the content of the red warning box, and do not do this unless you *really* know what you are doing. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: redirect to website not working
Thank you for your help... xx.xxx.xx.81 server through which iam using ie is not accessed to public website.This might be the problem. I want to ask a noob question that is there any method , as 81 server is not accessed to public websites but Linux server has access , so any method,way so that request can be sent to public website through Linux server . Linux server can be accessed through 81 server only. I have to use 81 server ie to request public website SMS sender vendor through Linux server.
Re: redirect to website not working
Hi. I will try to give you some more tips below, but really you should try and work this out by yourself. From what little information is available below, I still believe that there is no problem with your application under Tomcat, but that the problem is that *the browser* cannot access that SMS site you were talking about, or that the request that the browser is sending to that site is invalid. Ankur Gupta wrote: *Fiddler Error:* ... 3 302 HTTPxx.xxx.xx.99:8080 /examples/smstrial.jsp?mobileNumber=01234567890 text/html;charset=ISO-8859-1 iexplore:6656 Above exchange #3 seems to be the original request which the browser sends to the Tomcat application. What you do not show, is the *content* of the response sent back by Tomcat, except the status code, which is 302 (re-direct). What would be interesting to see here, is the *response header* Location:. (you can see that also in Fiddler) When the browser gets this 302 response from the server, it takes the content of the Location response header, and then immediately makes a new HTTP request to that URL. That is the exchange #4 below. 4 502 HTTP180.179.218.150 /sendurl.aspx?user=xxxpwd=xxxsenderid=xxxmobileno=0123456789msgtext=Hellosmstype=0 512 no-cache, must-revalidatetext/html; charset=UTF-8 iexplore:6656 The above exchange #4, seems to be the new request that the browser makes to the SMS server at 180.179.218.150, and that server responds with a 502 status (a server error). This is not Tomcat anymore, and thus out of scope for this forum. You have to figure out why that SMS server sends this response to the browser. Something tells me that you are not really familiar with the HTTP protocol. Maybe you should get some local help in that respect. Each interaction between browser and server consists of one request from the browser, and one response from the server. Fiddler shows this as one line, but you can click on that line and then ask to see different things (maybe you should ask for the raw content). Above you show the browser request, but not the server response content. ... *IE giving error:* [Fiddler] The connection to '180.179.218.150' failed. Error: TimedOut (0x274c). System.Net.Sockets.SocketException A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 180.179.218.150:80 This is a bit confusing, because it seems to say that the server at 180.179.218.150 is not responding. Maybe the browser that you are using cannot access that IP address ? Or it can connect to it, but something is blocking the server response to the browser. (Firewalls or so) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 8 webapp failed to start on Windows reboot
Environment --- Tomcat 8.0.21 x64 bit, JDK 8u31, Windows 2008 R2 x64 bit Problem --- After upgrading from tomcat 7.0.42 to 8.0.21, my webapp(gih-ws) failed to startup every time the machine is rebooted. In the tomcat catalina log, it did not show any error, but in my webapp(gih-ws) access log, it showed below error. ERROR 08 6月 2015 03:20:39,329 (AxisEngine.java:219) -[]- The service cannot be found for the endpoint reference (EPR) /gih-ws/services/GIH3Service/keywordSearchWithIndex?maxNoOfResult=11keyword=North%20Point%20Government%20OfficesstartIndex=0response=application%2Fjsonlang=enextent=839266.674348%2C816651.312098%2C839765.325652%2C817436.687902 org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /gih-ws/services/GIH3Service/keywordSearchWithIndex?maxNoOfResult=11keyword=North%20Point%20Government%20OfficesstartIndex=0response=application%2Fjsonlang=enextent=839266.674348%2C816651.312098%2C839765.325652%2C817436.687902 at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:78) at org.apache.axis2.engine.Phase.invoke(Phase.java:329) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168) at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:144) at org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:139) at org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:837) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:273) at javax.servlet.http.HttpServlet.service(HttpServlet.java:622) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:668) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:283) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2463) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2452) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Our finding --- We stopped the tomcat 8 service and then started it again and the webapp(gih-ws) can startup and there was no error in the gih-ws access log. It is so weird. Is there any tomcat 8 service startup issue every time the machine is rebooted? Should we start the Tomcat 8 service in Startup(Delayed) mode? I also include below tomcat catalina log for your reference. Thanks. Tomcat catalina log --- 10-Jun-2015 10:04:20.250 INFO [Thread-25] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler [http-apr-9090] 10-Jun-2015 10:04:20.313 INFO [Thread-25] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler [http-bio-9443] 10-Jun-2015 10:04:20.375 INFO [Thread-25] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler [ajp-apr-8009] 10-Jun-2015 10:04:20.437 INFO [Thread-25] org.apache.catalina.core.StandardService.stopInternal Stopping service Catalina 10-Jun-2015 10:04:20.500 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [gih-ws] registered the JDBC driver [org.logicalcobwebs.proxool.ProxoolDriver] but failed to unregister it when the web application was stopped. To
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
