RE: servlet request time out ?!
I tried adding it to my .../WEB-INF/web.xml web-app session-config session-timeout45/session-timeout /session-config ... /web-app but I started getting errors when tomcat is deploying the context: Jun 3, 2005 11:51:20 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 28 column 11: The content of element type web-app must match (icon?,display-name?,description?,distributable?,context-param*,filter*,fil ter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mappin g*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,se curity-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-loca l-ref*). org.xml.sax.SAXParseException: The content of element type web-app must match (icon?,display-name?,description?,distributable?,context-param*,filter*,fil ter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mappin g*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,se curity-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-loca l-ref*). It looks like an XML error, but I don't see where is the problem. Removing the above 3 lines gets rid of the errors Ross -Original Message- From: J. Alejandro Zepeda Cortés [mailto:[EMAIL PROTECTED] Sent: Thursday, June 02, 2005 11:10 AM To: Tomcat Users List Subject: Re: servlet request time out ?! Maybe the setting in your web.xml is not enough for your request? session-config session-timeout45/session-timeout!-- 30 minutes by default-- /session-config - Original Message - From: Angelov, Rossen [EMAIL PROTECTED] To: 'Tomcat Users List' tomcat-user@jakarta.apache.org Sent: Thursday, June 02, 2005 11:34 AM Subject: RE: servlet request time out ?! I would like to bring that issue up again as I haven't resolved it yet and haven't found what's causing it. Any help and ideas are welcome! Thanks, Ross -Original Message- From: Angelov, Rossen Sent: Thursday, May 26, 2005 1:33 PM To: 'Tomcat Users List' Subject: servlet request time out ?! Hi, Does anybody know about a time out on a servlet request with Tomcat 5? The problem is that I have a request that takes about 30 minutes but the browser keeps waiting for the response forever. I tried different browsers but it's the same behavior. I put debug statements in the doPost method and it's finishing correctly. The last debug statement is printed out but the browser is still waiting for the response. Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
Re: servlet request time out ?!
On 6/3/05, Angelov, Rossen [EMAIL PROTECTED] wrote: I tried adding it to my .../WEB-INF/web.xml web-app session-config session-timeout45/session-timeout /session-config ... /web-app but I started getting errors when tomcat is deploying the context: Jun 3, 2005 11:51:20 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 28 column 11: The content of element type web-app must match (icon?,display-name?,description?,distributable?,context-param*,filter*,fil ter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mappin g*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,se curity-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-loca l-ref*). org.xml.sax.SAXParseException: The content of element type web-app must match (icon?,display-name?,description?,distributable?,context-param*,filter*,fil ter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mappin g*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,se curity-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-loca l-ref*). The session-config details need to go after the servlet-mapping's and before the mime-mapping's in your web.xml, that is what that error is saying, the DTD expects the elements to be in a certain order and your order isn't correct. Regards, -- Jason Bainbridge http://kde.org - [EMAIL PROTECTED] Personal Site - http://jasonbainbridge.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: servlet request time out ?!
Jason, thanks for pointing out the order in web.xml matters. Placing the session-config lines after the mappings resolved the problem with the XML exception, but another exception started appearing in the log: Jun 3, 2005 2:17:59 PM org.apache.coyote.tomcat5.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.ArrayIndexOutOfBoundsException: 0 at org.apache.coyote.tomcat5.CoyoteAdapter.normalize(CoyoteAdapter.java:483) at org.apache.coyote.tomcat5.CoyoteAdapter.postParseRequest(CoyoteAdapter.java: 239) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:158) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:683) at java.lang.Thread.run(Thread.java:534) Do you know what might be causing it and if the exception can be related to setting the session-config option? Ross -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Friday, June 03, 2005 11:12 AM To: Tomcat Users List Subject: Re: servlet request time out ?! On 6/3/05, Angelov, Rossen [EMAIL PROTECTED] wrote: I tried adding it to my .../WEB-INF/web.xml web-app session-config session-timeout45/session-timeout /session-config ... /web-app but I started getting errors when tomcat is deploying the context: Jun 3, 2005 11:51:20 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 28 column 11: The content of element type web-app must match (icon?,display-name?,description?,distributable?,context-param*,filter*,fil ter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mappin g*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,se curity-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-loca l-ref*). org.xml.sax.SAXParseException: The content of element type web-app must match (icon?,display-name?,description?,distributable?,context-param*,filter*,fil ter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mappin g*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,se curity-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-loca l-ref*). The session-config details need to go after the servlet-mapping's and before the mime-mapping's in your web.xml, that is what that error is saying, the DTD expects the elements to be in a certain order and your order isn't correct. Regards, -- Jason Bainbridge http://kde.org - [EMAIL PROTECTED] Personal Site - http://jasonbainbridge.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
RE: servlet request time out ?!
I would like to bring that issue up again as I haven't resolved it yet and haven't found what's causing it. Any help and ideas are welcome! Thanks, Ross -Original Message- From: Angelov, Rossen Sent: Thursday, May 26, 2005 1:33 PM To: 'Tomcat Users List' Subject: servlet request time out ?! Hi, Does anybody know about a time out on a servlet request with Tomcat 5? The problem is that I have a request that takes about 30 minutes but the browser keeps waiting for the response forever. I tried different browsers but it's the same behavior. I put debug statements in the doPost method and it's finishing correctly. The last debug statement is printed out but the browser is still waiting for the response. Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
Re: servlet request time out ?!
Maybe the setting in your web.xml is not enough for your request? session-config session-timeout45/session-timeout!-- 30 minutes by default-- /session-config - Original Message - From: Angelov, Rossen [EMAIL PROTECTED] To: 'Tomcat Users List' tomcat-user@jakarta.apache.org Sent: Thursday, June 02, 2005 11:34 AM Subject: RE: servlet request time out ?! I would like to bring that issue up again as I haven't resolved it yet and haven't found what's causing it. Any help and ideas are welcome! Thanks, Ross -Original Message- From: Angelov, Rossen Sent: Thursday, May 26, 2005 1:33 PM To: 'Tomcat Users List' Subject: servlet request time out ?! Hi, Does anybody know about a time out on a servlet request with Tomcat 5? The problem is that I have a request that takes about 30 minutes but the browser keeps waiting for the response forever. I tried different browsers but it's the same behavior. I put debug statements in the doPost method and it's finishing correctly. The last debug statement is printed out but the browser is still waiting for the response. Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
servlet request time out ?!
Hi, Does anybody know about a time out on a servlet request with Tomcat 5? The problem is that I have a request that takes about 30 minutes but the browser keeps waiting for the response forever. I tried different browsers but it's the same behavior. I put debug statements in the doPost method and it's finishing correctly. The last debug statement is printed out but the browser is still waiting for the response. Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
Re: servlet request time out ?!
Hi Angelov, I am new to Tomcat (Just started using Tomcat5.0 yesterday), but the problem you mentioned sounds like a typical connnection timout. Have you tried to setting the connectionTimeout value to 0 in the server.xml? Here is to location in server.xml. Where there is currently a value of [connectionTimeout=2] change to [connectionTimeout=0]. Service name=Catalina !-- A Connector represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to the associated Container (normally an Engine) for processing. By default, a non-SSL HTTP/1.1 Connector is established on port 8080. You can also enable an SSL HTTP/1.1 Connector on port 8443 by following the instructions below and uncommenting the second Connector entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 5 documentation bundle for more detailed instructions): * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or later, and put the JAR files into $JAVA_HOME/jre/lib/ext. * Execute: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows) $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix) with a password value of changeit for both the certificate and the keystore itself. By default, DNS lookups are enabled when a web application calls request.getRemoteHost(). This can have an adverse impact on performance, so you can disable it by setting the enableLookups attribute to false. When DNS lookups are disabled, request.getRemoteHost() will return the String version of the IP address of the remote client. -- !-- Define a non-SSL Coyote HTTP/1.1 Connector on the port specified during installation -- Connector port=8080 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 disableUploadTimeout=true / !-- Note : To disable connection timeouts, set connectionTimeout value to 0 -- Mike Angelov, Rossen wrote: Hi, Does anybody know about a time out on a servlet request with Tomcat 5? The problem is that I have a request that takes about 30 minutes but the browser keeps waiting for the response forever. I tried different browsers but it's the same behavior. I put debug statements in the doPost method and it's finishing correctly. The last debug statement is printed out but the browser is still waiting for the response. Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 5/25/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 5/25/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: servlet request time out ?!
I haven't tested this myself, so I'm only going on what the docs say (5.5): http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/http.html If I've understood correctly, this doc seems to say that the connectionTimeout param doesn't have the effect Angelov is looking for - it sets the max time between a connection (socket) being opened by the client, and the client sending a request url to TC. -Original Message- From: Mike Baliel [mailto:[EMAIL PROTECTED] Sent: Thursday 26 May 2005 19:49 To: Tomcat Users List Subject: Re: servlet request time out ?! Hi Angelov, I am new to Tomcat (Just started using Tomcat5.0 yesterday), but the problem you mentioned sounds like a typical connnection timout. Have you tried to setting the connectionTimeout value to 0 in the server.xml? Here is to location in server.xml. Where there is currently a value of [connectionTimeout=2] change to [connectionTimeout=0]. Service name=Catalina !-- A Connector represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to the associated Container (normally an Engine) for processing. By default, a non-SSL HTTP/1.1 Connector is established on port 8080. You can also enable an SSL HTTP/1.1 Connector on port 8443 by following the instructions below and uncommenting the second Connector entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 5 documentation bundle for more detailed instructions): * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or later, and put the JAR files into $JAVA_HOME/jre/lib/ext. * Execute: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows) $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix) with a password value of changeit for both the certificate and the keystore itself. By default, DNS lookups are enabled when a web application calls request.getRemoteHost(). This can have an adverse impact on performance, so you can disable it by setting the enableLookups attribute to false. When DNS lookups are disabled, request.getRemoteHost() will return the String version of the IP address of the remote client. -- !-- Define a non-SSL Coyote HTTP/1.1 Connector on the port specified during installation -- Connector port=8080 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 disableUploadTimeout=true / !-- Note : To disable connection timeouts, set connectionTimeout value to 0 -- Mike Angelov, Rossen wrote: Hi, Does anybody know about a time out on a servlet request with Tomcat 5? The problem is that I have a request that takes about 30 minutes but the browser keeps waiting for the response forever. I tried different browsers but it's the same behavior. I put debug statements in the doPost method and it's finishing correctly. The last debug statement is printed out but the browser is still waiting for the response. Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. -- -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 5/25/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 5/25/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: servlet request time out ?!
That's exactly how I understood it too. The request will be dropped if after certain number of milliseconds the request's URI hasn't been received. In my case the URI comes directly with the request and based on my log I can see the request is being processed but there is no response after the doPost method is finished. I can still give it try with connectionTimeout=0, but don't expect it to help. Ross -Original Message- From: Steve Kirk [mailto:[EMAIL PROTECTED] Sent: Thursday, May 26, 2005 3:09 PM To: 'Tomcat Users List'; [EMAIL PROTECTED] Subject: RE: servlet request time out ?! I haven't tested this myself, so I'm only going on what the docs say (5.5): http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/http.html If I've understood correctly, this doc seems to say that the connectionTimeout param doesn't have the effect Angelov is looking for - it sets the max time between a connection (socket) being opened by the client, and the client sending a request url to TC. -Original Message- From: Mike Baliel [mailto:[EMAIL PROTECTED] Sent: Thursday 26 May 2005 19:49 To: Tomcat Users List Subject: Re: servlet request time out ?! Hi Angelov, I am new to Tomcat (Just started using Tomcat5.0 yesterday), but the problem you mentioned sounds like a typical connnection timout. Have you tried to setting the connectionTimeout value to 0 in the server.xml? Here is to location in server.xml. Where there is currently a value of [connectionTimeout=2] change to [connectionTimeout=0]. Service name=Catalina !-- A Connector represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to the associated Container (normally an Engine) for processing. By default, a non-SSL HTTP/1.1 Connector is established on port 8080. You can also enable an SSL HTTP/1.1 Connector on port 8443 by following the instructions below and uncommenting the second Connector entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 5 documentation bundle for more detailed instructions): * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or later, and put the JAR files into $JAVA_HOME/jre/lib/ext. * Execute: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows) $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix) with a password value of changeit for both the certificate and the keystore itself. By default, DNS lookups are enabled when a web application calls request.getRemoteHost(). This can have an adverse impact on performance, so you can disable it by setting the enableLookups attribute to false. When DNS lookups are disabled, request.getRemoteHost() will return the String version of the IP address of the remote client. -- !-- Define a non-SSL Coyote HTTP/1.1 Connector on the port specified during installation -- Connector port=8080 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 disableUploadTimeout=true / !-- Note : To disable connection timeouts, set connectionTimeout value to 0 -- Mike Angelov, Rossen wrote: Hi, Does anybody know about a time out on a servlet request with Tomcat 5? The problem is that I have a request that takes about 30 minutes but the browser keeps waiting for the response forever. I tried different browsers but it's the same behavior. I put debug statements in the doPost method and it's finishing correctly. The last debug statement is printed out but the browser is still waiting for the response. Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. -- -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 5/25/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 5/25/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This communication
RE: servlet request time out ?!
Sorry Ross, got yr name wrong :) Would be interested to know how to do it though, if you find out could you please post, thanks. -Original Message- From: Angelov, Rossen [mailto:[EMAIL PROTECTED] Sent: Thursday 26 May 2005 21:20 To: 'Tomcat Users List'; [EMAIL PROTECTED] Subject: RE: servlet request time out ?! That's exactly how I understood it too. The request will be dropped if after certain number of milliseconds the request's URI hasn't been received. In my case the URI comes directly with the request and based on my log I can see the request is being processed but there is no response after the doPost method is finished. I can still give it try with connectionTimeout=0, but don't expect it to help. Ross -Original Message- From: Steve Kirk [mailto:[EMAIL PROTECTED] Sent: Thursday, May 26, 2005 3:09 PM To: 'Tomcat Users List'; [EMAIL PROTECTED] Subject: RE: servlet request time out ?! I haven't tested this myself, so I'm only going on what the docs say (5.5): http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/http.html If I've understood correctly, this doc seems to say that the connectionTimeout param doesn't have the effect Angelov is looking for - it sets the max time between a connection (socket) being opened by the client, and the client sending a request url to TC. -Original Message- From: Mike Baliel [mailto:[EMAIL PROTECTED] Sent: Thursday 26 May 2005 19:49 To: Tomcat Users List Subject: Re: servlet request time out ?! Hi Angelov, I am new to Tomcat (Just started using Tomcat5.0 yesterday), but the problem you mentioned sounds like a typical connnection timout. Have you tried to setting the connectionTimeout value to 0 in the server.xml? Here is to location in server.xml. Where there is currently a value of [connectionTimeout=2] change to [connectionTimeout=0]. Service name=Catalina !-- A Connector represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to the associated Container (normally an Engine) for processing. By default, a non-SSL HTTP/1.1 Connector is established on port 8080. You can also enable an SSL HTTP/1.1 Connector on port 8443 by following the instructions below and uncommenting the second Connector entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 5 documentation bundle for more detailed instructions): * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or later, and put the JAR files into $JAVA_HOME/jre/lib/ext. * Execute: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows) $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix) with a password value of changeit for both the certificate and the keystore itself. By default, DNS lookups are enabled when a web application calls request.getRemoteHost(). This can have an adverse impact on performance, so you can disable it by setting the enableLookups attribute to false. When DNS lookups are disabled, request.getRemoteHost() will return the String version of the IP address of the remote client. -- !-- Define a non-SSL Coyote HTTP/1.1 Connector on the port specified during installation -- Connector port=8080 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 disableUploadTimeout=true / !-- Note : To disable connection timeouts, set connectionTimeout value to 0 -- Mike Angelov, Rossen wrote: Hi, Does anybody know about a time out on a servlet request with Tomcat 5? The problem is that I have a request that takes about 30 minutes but the browser keeps waiting for the response forever. I tried different browsers but it's the same behavior. I put debug statements in the doPost method and it's finishing correctly. The last debug statement is printed out but the browser is still waiting for the response. Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. -- -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 5/25/2005
Re: servlet request time out ?!
Hi Angelov, I had a similar problem a few years back using websphere 4.0 and IBM's HTTP server. The HTTP server was dropping the connection with the servlet container before the unit of work had finished. Setting the HTTP server's connection timeout to infinite resolved the issue. Not sure if it will work here... but it is worth a try.. Angelov, Rossen wrote: That's exactly how I understood it too. The request will be dropped if after certain number of milliseconds the request's URI hasn't been received. In my case the URI comes directly with the request and based on my log I can see the request is being processed but there is no response after the doPost method is finished. I can still give it try with connectionTimeout=0, but don't expect it to help. Ross -Original Message- From: Steve Kirk [mailto:[EMAIL PROTECTED] Sent: Thursday, May 26, 2005 3:09 PM To: 'Tomcat Users List'; [EMAIL PROTECTED] Subject: RE: servlet request time out ?! I haven't tested this myself, so I'm only going on what the docs say (5.5): http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/http.html If I've understood correctly, this doc seems to say that the connectionTimeout param doesn't have the effect Angelov is looking for - it sets the max time between a connection (socket) being opened by the client, and the client sending a request url to TC. -Original Message- From: Mike Baliel [mailto:[EMAIL PROTECTED] Sent: Thursday 26 May 2005 19:49 To: Tomcat Users List Subject: Re: servlet request time out ?! Hi Angelov, I am new to Tomcat (Just started using Tomcat5.0 yesterday), but the problem you mentioned sounds like a typical connnection timout. Have you tried to setting the connectionTimeout value to 0 in the server.xml? Here is to location in server.xml. Where there is currently a value of [connectionTimeout=2] change to [connectionTimeout=0]. Service name=Catalina !-- A Connector represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to the associated Container (normally an Engine) for processing. By default, a non-SSL HTTP/1.1 Connector is established on port 8080. You can also enable an SSL HTTP/1.1 Connector on port 8443 by following the instructions below and uncommenting the second Connector entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 5 documentation bundle for more detailed instructions): * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or later, and put the JAR files into $JAVA_HOME/jre/lib/ext. * Execute: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows) $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix) with a password value of changeit for both the certificate and the keystore itself. By default, DNS lookups are enabled when a web application calls request.getRemoteHost(). This can have an adverse impact on performance, so you can disable it by setting the enableLookups attribute to false. When DNS lookups are disabled, request.getRemoteHost() will return the String version of the IP address of the remote client. -- !-- Define a non-SSL Coyote HTTP/1.1 Connector on the port specified during installation -- Connector port=8080 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 disableUploadTimeout=true / !-- Note : To disable connection timeouts, set connectionTimeout value to 0 -- Mike Angelov, Rossen wrote: Hi, Does anybody know about a time out on a servlet request with Tomcat 5? The problem is that I have a request that takes about 30 minutes but the browser keeps waiting for the response forever. I tried different browsers but it's the same behavior. I put debug statements in the doPost method and it's finishing correctly. The last debug statement is printed out but the browser is still waiting for the response. Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. -- -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 5/25/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 5/25/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e
RE: servlet request time out ?!
Well, I know only two attributes in Tomcat that configure connection related timeouts: connectionTimeout and disableUploadTimeout. I already tried setting connectionTimeout=0 but it didn't work. Now I'll try setting disableUploadTimeout=true. I didn't have it before in my server.xml and by default it's set to false, so hopefully this works. Any suggestions are welcome if anybody else knows other timeouts for the request. Thanks, Ross -Original Message- From: Mike Baliel [mailto:[EMAIL PROTECTED] Sent: Thursday, May 26, 2005 3:37 PM To: Tomcat Users List Subject: Re: servlet request time out ?! Hi Angelov, I had a similar problem a few years back using websphere 4.0 and IBM's HTTP server. The HTTP server was dropping the connection with the servlet container before the unit of work had finished. Setting the HTTP server's connection timeout to infinite resolved the issue. Not sure if it will work here... but it is worth a try.. Angelov, Rossen wrote: That's exactly how I understood it too. The request will be dropped if after certain number of milliseconds the request's URI hasn't been received. In my case the URI comes directly with the request and based on my log I can see the request is being processed but there is no response after the doPost method is finished. I can still give it try with connectionTimeout=0, but don't expect it to help. Ross -Original Message- From: Steve Kirk [mailto:[EMAIL PROTECTED] Sent: Thursday, May 26, 2005 3:09 PM To: 'Tomcat Users List'; [EMAIL PROTECTED] Subject: RE: servlet request time out ?! I haven't tested this myself, so I'm only going on what the docs say (5.5): http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/http.html If I've understood correctly, this doc seems to say that the connectionTimeout param doesn't have the effect Angelov is looking for - it sets the max time between a connection (socket) being opened by the client, and the client sending a request url to TC. -Original Message- From: Mike Baliel [mailto:[EMAIL PROTECTED] Sent: Thursday 26 May 2005 19:49 To: Tomcat Users List Subject: Re: servlet request time out ?! Hi Angelov, I am new to Tomcat (Just started using Tomcat5.0 yesterday), but the problem you mentioned sounds like a typical connnection timout. Have you tried to setting the connectionTimeout value to 0 in the server.xml? Here is to location in server.xml. Where there is currently a value of [connectionTimeout=2] change to [connectionTimeout=0]. Service name=Catalina !-- A Connector represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to the associated Container (normally an Engine) for processing. By default, a non-SSL HTTP/1.1 Connector is established on port 8080. You can also enable an SSL HTTP/1.1 Connector on port 8443 by following the instructions below and uncommenting the second Connector entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 5 documentation bundle for more detailed instructions): * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or later, and put the JAR files into $JAVA_HOME/jre/lib/ext. * Execute: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows) $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix) with a password value of changeit for both the certificate and the keystore itself. By default, DNS lookups are enabled when a web application calls request.getRemoteHost(). This can have an adverse impact on performance, so you can disable it by setting the enableLookups attribute to false. When DNS lookups are disabled, request.getRemoteHost() will return the String version of the IP address of the remote client. -- !-- Define a non-SSL Coyote HTTP/1.1 Connector on the port specified during installation -- Connector port=8080 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 disableUploadTimeout=true / !-- Note : To disable connection timeouts, set connectionTimeout value to 0 -- Mike Angelov, Rossen wrote: Hi, Does anybody know about a time out on a servlet request with Tomcat 5? The problem is that I have a request that takes about 30 minutes but the browser keeps waiting for the response forever. I tried different browsers but it's the same behavior. I put debug statements in the doPost method and it's finishing correctly. The last debug statement is printed out but the browser is still waiting
Strange Problem!: Connection time out while using URLConnection connect method
Hi All, I am posting this again. Please help. Thanks. --Forwarded message -- References: [EMAIL PROTECTED] From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Strange Problem!: Connection time out while using URLConnection connect method Date: Wed, 17 Nov 2004 09:30:17 GMT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi All, I am facing a very strange problem. When I run tomcat4.1.27 in command prompt, I am able to connect and call a servlet deployed in it from another java program running on another machine using using URLConnection connect method. But when I run tomcat server from windows services, the client program is not able to call the deployed servlet and throws the below exception at the line where connect method is invoked. java.net.ConnectException: Connection timed out: connect Has anyone else faced this strange problem. The only difference is in the way tomcat server has been started. When started in command prompt there are no problems in connecting to the server and calling the servlet deployed in it! I need to badly get this working when tomcat is started as a windows service. Thanks in Advance. Vignesh. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Strange Problem!: Connection time out while using URLConnection connect method
I think you may check you IP setting. You run tomcat in command prompt ,jvm binging your ip;but in windows service it may binding 127.0.0.1 or localhost. I guess it^_^ On Thu, 18 Nov 2004 09:36:32 GMT, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi All, I am posting this again. Please help. Thanks. --Forwarded message -- References: [EMAIL PROTECTED] From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Strange Problem!: Connection time out while using URLConnection connect method Date: Wed, 17 Nov 2004 09:30:17 GMT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi All, I am facing a very strange problem. When I run tomcat4.1.27 in command prompt, I am able to connect and call a servlet deployed in it from another java program running on another machine using using URLConnection connect method. But when I run tomcat server from windows services, the client program is not able to call the deployed servlet and throws the below exception at the line where connect method is invoked. java.net.ConnectException: Connection timed out: connect Has anyone else faced this strange problem. The only difference is in the way tomcat server has been started. When started in command prompt there are no problems in connecting to the server and calling the servlet deployed in it! I need to badly get this working when tomcat is started as a windows service. Thanks in Advance. Vignesh. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Strange Problem!: Connection time out while using URLConnection connect method
Is this somthing related to external Ip and Internal ip if you are behind the firewall... Birendar Singh Waldiya Tata Consultancy Services Limited Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com [EMAIL PROTECTED] 11/18/2004 03:06 PM Please respond to Tomcat Users List [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Strange Problem!: Connection time out while using URLConnection connect method Hi All, I am posting this again. Please help. Thanks. --Forwarded message -- References: [EMAIL PROTECTED] From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Strange Problem!: Connection time out while using URLConnection connect method Date: Wed, 17 Nov 2004 09:30:17 GMT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi All, I am facing a very strange problem. When I run tomcat4.1.27 in command prompt, I am able to connect and call a servlet deployed in it from another java program running on another machine using using URLConnection connect method. But when I run tomcat server from windows services, the client program is not able to call the deployed servlet and throws the below exception at the line where connect method is invoked. java.net.ConnectException: Connection timed out: connect Has anyone else faced this strange problem. The only difference is in the way tomcat server has been started. When started in command prompt there are no problems in connecting to the server and calling the servlet deployed in it! I need to badly get this working when tomcat is started as a windows service. Thanks in Advance. Vignesh. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ForwardSourceID:NT4412 DISCLAIMER: The information contained in this message is intended only and solely for the addressed individual or entity indicated in this message and for the exclusive use of the said addressed individual or entity indicated in this message (or responsible for delivery of the message to such person) and may contain legally privileged and confidential information belonging to Tata Consultancy Services Limited. It must not be printed, read, copied, disclosed, forwarded, distributed or used (in whatsoever manner) by any person other than the addressee. Unauthorized use, disclosure or copying is strictly prohibited and may constitute unlawful act and can possibly attract legal action, civil and/or criminal. The contents of this message need not necessarily reflect or endorse the views of Tata Consultancy Services limited on any subject matter. Any action taken or omitted to be taken based on this message is entirely at your risk and neither the originator of this message nor Tata Consultancy Services Limited takes any responsibility or liability towards the same. Opinions, conclusions and any other information contained in this message that do not relate to the official business of Tata Consultancy Services limited shall be understood as neither given nor endorsed by Tata Consultancy Services Limited or any affiliate of Tata Consultancy Services Limited. If you have received this message in error, you should destroy this message and may please notify the sender by e-mail. Thank you.
Re: Strange Problem!: Connection time out while using URLConnection connect method
Hi, Thanks. Thinking that could be the problem, I had already tried binding it with the specific IP address of the machine by setting the address attribute for HTTP connector in server.xml but that too didn't work. -- Original Message -- On 18 Nov 2004, 06:06:06 PM, Sailing Cai writes: I think you may check you IP setting. You run tomcat in command prompt ,jvm binging your ip;but in windows service it may binding 127.0.0.1 or localhost. I guess it^_^ On Thu, 18 Nov 2004 09:36:32 GMT, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi All, I am posting this again. Please help. Thanks. --Forwarded message -- References: [EMAIL PROTECTED] From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Strange Problem!: Connection time out while using URLConnection connect method Date: Wed, 17 Nov 2004 09:30:17 GMT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi All, I am facing a very strange problem. When I run tomcat4.1.27 in command prompt, I am able to connect and call a servlet deployed in it from another java program running on another machine using using URLConnection connect method. But when I run tomcat server from windows services, the client program is not able to call the deployed servlet and throws the below exception at the line where connect method is invoked. java.net.ConnectException: Connection timed out: connect Has anyone else faced this strange problem. The only difference is in the way tomcat server has been started. When started in command prompt there are no problems in connecting to the server and calling the servlet deployed in it! I need to badly get this working when tomcat is started as a windows service. Thanks in Advance. Vignesh. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Strange Problem!: Connection time out while using URLConnection connect method
Hi, The I am running tomcat and the client program in the same subnet and so there is no such issue. Thanks. -- Original Message -- On 18 Nov 2004, 06:12:54 PM, [EMAIL PROTECTED] writes: Is this somthing related to external Ip and Internal ip if you are behind the firewall... Birendar Singh Waldiya Tata Consultancy Services Limited Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com [EMAIL PROTECTED] 11/18/2004 03:06 PM Please respond to Tomcat Users List [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Strange Problem!: Connection time out while using URLConnection connect method Hi All, I am posting this again. Please help. Thanks. --Forwarded message -- References: [EMAIL PROTECTED] From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Strange Problem!: Connection time out while using URLConnection connect method Date: Wed, 17 Nov 2004 09:30:17 GMT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi All, I am facing a very strange problem. When I run tomcat4.1.27 in command prompt, I am able to connect and call a servlet deployed in it from another java program running on another machine using using URLConnection connect method. But when I run tomcat server from windows services, the client program is not able to call the deployed servlet and throws the below exception at the line where connect method is invoked. java.net.ConnectException: Connection timed out: connect Has anyone else faced this strange problem. The only difference is in the way tomcat server has been started. When started in command prompt there are no problems in connecting to the server and calling the servlet deployed in it! I need to badly get this working when tomcat is started as a windows service. Thanks in Advance. Vignesh. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ForwardSourceID:NT4412 DISCLAIMER: The information contained in this message is intended only and solely for the addressed individual or entity indicated in this message and for the exclusive use of the said addressed individual or entity indicated in this message (or responsible for delivery of the message to such person) and may contain legally privileged and confidential information belonging to Tata Consultancy Services Limited. It must not be printed, read, copied, disclosed, forwarded, distributed or used (in whatsoever manner) by any person other than the addressee. Unauthorized use, disclosure or copying is strictly prohibited and may constitute unlawful act and can possibly attract legal action, civil and/or criminal. The contents of this message need not necessarily reflect or endorse the views of Tata Consultancy Services limited on any subject matter. Any action taken or omitted to be taken based on this message is entirely at your risk and neither the originator of this message nor Tata Consultancy Services Limited takes any responsibility or liability towards the same. Opinions, conclusions and any other information contained in this message that do not relate to the official business of Tata Consultancy Services limited shall be understood as neither given nor endorsed by Tata Consultancy Services Limited or any affiliate of Tata Consultancy Services Limited. If you have received this message in error, you should destroy this message and may please notify the sender by e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Strange Problem!: Connection time out while using URLConnection connect method
Hi All, I am facing a very strange problem. When I run tomcat4.1.27 in command prompt, I am able to connect and call a servlet deployed in it from another java program running on another machine using using URLConnection connect method. But when I run tomcat server from windows services, the client program is not able to call the deployed servlet and throws the below exception at the line where connect method is invoked. java.net.ConnectException: Connection timed out: connect Has anyone else faced this strange problem. The only difference is in the way tomcat server has been started. When started in command prompt there are no problems in connecting to the server and calling the servlet deployed in it! I need to badly get this working when tomcat is started as a windows service. Thanks in Advance. Vignesh. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: session time out
Hola, Matt's right in principle. If you want to be sneaky and/or unpleasant to your users, you can have your app throw 401s when a session is invalid, and then put a custom error page for 401 errors in your web.xml, and do it that way. Yoav Shapira Millennium Research Informatics -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Saturday, July 31, 2004 6:07 AM To: Tomcat Users List Subject: RE: session time out If this is possible then i'd like to know but as far as I know you have to code around session time outs and redirect yourself. Ta Matt -Original Message- From: Asim Ghosh [mailto:[EMAIL PROTECTED] Sent: 31 July 2004 08:12 To: [EMAIL PROTECTED] Subject: session time out hello everybody, is there any option in web.xml that i can redirect my request to some other page when session has timed out. Asim - ALL-NEW Yahoo! Messenger - all new features - even more fun! This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
session time out
hello everybody, is there any option in web.xml that i can redirect my request to some other page when session has timed out. Asim - ALL-NEW Yahoo! Messenger - all new features - even more fun!
RE: session time out
If this is possible then i'd like to know but as far as I know you have to code around session time outs and redirect yourself. Ta Matt -Original Message- From: Asim Ghosh [mailto:[EMAIL PROTECTED] Sent: 31 July 2004 08:12 To: [EMAIL PROTECTED] Subject: session time out hello everybody, is there any option in web.xml that i can redirect my request to some other page when session has timed out. Asim - ALL-NEW Yahoo! Messenger - all new features - even more fun! Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[OT] reloading bean upon session time out
Hi folks, know this is somewhat off topic but Im still quite confident some (if not most) of you is capable of answering my question. Upon my users first request to my JSP-pages I retrive their user name and loads their authorization level etc. from a database. This information is stored in a bean given session scope. Thing is that after 30 minutes (default) the session times out and the required information is lost, thereby rendering my users unable to make request to the database. How do I test for this and redirect them to the original authorization page? (Ruling out the option of setting session time out to say 8 hours...) /Thomas FONT SIZE=1 FACE=Arial___ Vi goer opmaerksom paa, at denne e-mail kan indeholde fortrolig information. Hvis du ved en fejltagelse modtager e-mailen, beder vi dig venligst informere afsender om fejlen ved at bruge svar-funktionen. Samtidig beder vi dig slette e-mailen i dit system uden at videresende eller kopiere den. Selv om e-mailen og ethvert vedhaeftet bilag efter vores overbevisning er fri for virus og andre fejl, som kan paavirke computeren eller it-systemet, hvori den modtages og laeses, aabnes den paa modtagerens eget ansvar. Vi paatager os ikke noget ansvar for tab og skade, som er opstaaet i forbindelse med at modtage og bruge e-mailen. ___ Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake by sending a reply, then delete the message from your system without making, distributing or retaining any copies of it. Although we believe that the message and any attachments are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message. /FONT
Re: [OT] reloading bean upon session time out
At 07:59 AM 10/30/2003, you wrote: Upon my users first request to my JSP-pages I retrive their user name and loads their authorization level etc. from a database. This information is stored in a bean given session scope. Thing is that after 30 minutes (default) the session times out and the required information is lost, thereby rendering my users unable to make request to the database. If the session times out after 30 minutes, then it means that your user has not submitted a request with the appropriate JSESSIONID in 30 minutes -- that's what causes the session to timeout. If your users are still hitting your site and the session times out, then there's something else wrong with what you're doing. How do I test for this and redirect them to the original authorization page? (Ruling out the option of setting session time out to say 8 hours...) There are a hundred ways to do this, but it's really an architectural decision for you. If you're not using one of the frameworks and everything is JSP, one way is to include a login_check.jsp page at the top of every JSP page. This page checks to ensure that the user is logged in. You could accomplish the same thing with a Filter or custom tag ... really depends on what you're comfortable with and what fits best into your system. justin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Query on Connection Time out??
Hi all friends, I am using tomcat4.1.24 for my uploading software(swing for client interface and servlet).Iam facing problem with connection broken,During uploading of file if connection between local computer and remote computer broken then my software will give a message to user through pop up dialog box,but that dialog box appears after 3 or 4 minitues of connection broken that means as per my idea that Tomcat realease the connection after 3 or 4 minitues of connection broken .I have tried to rectify by configuring Connector element of server.xml file but couldn't slove my problem.Can any plz guide me am I correct that the delay in appearing of dialog box in case of connection broken due to below configuration of Tomcat in server.xml file or it may be due to any other reason. Connector className=org.apache.catalina.connector.http.HttpConnectorport=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 debug=0 connectionTimeout=0/ Regards Bikash __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Avoid the Tomcat to time out on my jdbcrealm
Hi. How can I avoid the Tomcat to time out on my jdbcrealm. Søren Blidorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Time Out
Hi, I have just built a new webserver and I am having a strange problem. The first few times I try to call a servlet it times out. Then eventually it will just call as normal and run ok. Then when I leave it for a while and come back I get the same issue. I looked in the logs and this was the only thing I could see that seemed to be an error. All the example servlets run fine and straight away. 2003-01-02 14:31:15 HttpProcessor[8080][4] process.finish java.lang.IllegalStateException: Current state = FLUSHED, new state = CODING_END at java.nio.charset.CharsetEncoder.throwIllegalStateException(CharsetEncoder.java:933) at java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:529) at sun.nio.cs.StreamEncoder$CharsetSE.flushLeftoverChar(StreamEncoder.java:356) at sun.nio.cs.StreamEncoder$CharsetSE.implClose(StreamEncoder.java:412) at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:158) at java.io.OutputStreamWriter.close(OutputStreamWriter.java:222) at java.io.PrintWriter.close(PrintWriter.java:137) at org.apache.catalina.connector.ResponseBase.finishResponse(ResponseBase.java:482) at org.apache.catalina.connector.HttpResponseBase.finishResponse(HttpResponseBase.java:237) at org.apache.catalina.connector.http.HttpResponseImpl.finishResponse(HttpResponseImpl.java:287) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1054) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125) at java.lang.Thread.run(Thread.java:536) The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you received this communication in error, please notify us immediately by responding to this email and then delete it from your system. Appleyard Finance Holdings Ltd or its subsidiaries are neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Time Out
Hello How do I change my Time Out options? My web form times out before I complete the Form... Thanks Ravi -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Setting the Time Out
Hello How do I change my Time Out options? My web form times out before I complete the Form... Thanks Ravi -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
where and how to set session time out to 1 hr?
where and how to set session time out to 1 hr? im using jboss-tomcat combo mark --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.410 / Virus Database: 231 - Release Date: 10/31/2002 -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
RE: where and how to set session time out to 1 hr?
The documentation is your friend. If the documentation fails you, Google is always there for you. web-app display-namemyApp/display-name servlet servlet-nameindex/servlet-name display-nameindex/display-name jsp-file/index.jsp/jsp-file /servlet session-config session-timeout30/session-timeout /session-config /web-app Change 30 to 60. I think you can also use HttpSession.setMaxInactiveInterval(): http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/servlet/http/HttpSession .html#setMaxInactiveInterval(int) John -Original Message- From: Mark Goking [mailto:Mark.Goking;asia.bigfoot.com] Sent: Thursday, November 07, 2002 4:32 AM To: Tomcat Users List Subject: where and how to set session time out to 1 hr? where and how to set session time out to 1 hr? im using jboss-tomcat combo mark --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.410 / Virus Database: 231 - Release Date: 10/31/2002 -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
RE: where and how to set session time out to 1 hr?
Yep.. only diff being setMaxInactiveInterval takes an argument in seconds where the web.xml setTimeout takes it in minutes. I think you can also use HttpSession.setMaxInactiveInterval(): -- Tref Gare Development Consultant Areeba Level 19/114 William St, Melbourne VIC 3000 email: [EMAIL PROTECTED] phone: +61 3 9642 5553 fax: +61 3 9642 1335 website: http://www.areeba.com.au -- This email is intended only for the use of the individual or entity named above and contains information that is confidential. No confidentiality is waived or lost by any mis-transmission. If you received this correspondence in error, please notify the sender and immediately delete it from your system. You must not disclose, copy or rely on any part of this correspondence if you are not the intended recipient. Any communication directed to clients via this message is subject to our Agreement and relevant Project Schedule. Any information that is transmitted via email which may offend may have been sent without knowledge or the consent of Areeba. -- -Original Message- From: Turner, John [mailto:JTurner;AAS.com] Sent: Friday, 8 November 2002 12:56 AM To: 'Tomcat Users List' Subject: RE: where and how to set session time out to 1 hr? The documentation is your friend. If the documentation fails you, Google is always there for you. web-app display-namemyApp/display-name servlet servlet-nameindex/servlet-name display-nameindex/display-name jsp-file/index.jsp/jsp-file /servlet session-config session-timeout30/session-timeout /session-config /web-app Change 30 to 60. I think you can also use HttpSession.setMaxInactiveInterval(): http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/servlet/http/HttpSes sion .html#setMaxInactiveInterval(int) John -Original Message- From: Mark Goking [mailto:Mark.Goking;asia.bigfoot.com] Sent: Thursday, November 07, 2002 4:32 AM To: Tomcat Users List Subject: where and how to set session time out to 1 hr? where and how to set session time out to 1 hr? im using jboss-tomcat combo mark --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.410 / Virus Database: 231 - Release Date: 10/31/2002 -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Time Out (I need help!)
Hi people! I am getting some problems with time out when a client tries to send a (around) 800kb file to my server via JSPSmartUpload. I think that if I set the timeout to a bigger time this problem will be solved, but I don't know how to do it... 1) How do I to re-set the timeout of tomcat (or apache)? (not the session time-out) 2) Does Somebody have the same problem with JSPSmartUpload or other upload package?? Thank u all!! Marcelo Mathias Lima [EMAIL PROTECTED] Java/JSP Developer -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Time out
Hi people! I am getting some problems with time out when a client tries to send a (around) 800kb file to my server via JSPSmartUpload. I think that if I set the timeout to a bigger time this problem will be solved, but I don't know how to do it... 1) How do I to re-set the timeout of tomcat (or apache)? (not the session time-out) 2) Does Somebody had the same problem with JSPSmartUpload? Thank u all!! Marcelo Mathias Lima [EMAIL PROTECTED] Java/JSP Developer -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
RE: Session Time out - Tomcat
Lior,
One easy way to do this is to store something in the session when you log
the user on (a user name or some unique piece of information) - you probably
already do this - and when you do any jsps or servlets, try doing
session.getAttribute on that item - if its null - the session is timed out.
I am sure there are other ways to do this but this is definitely an easy way
to do it!
e.g
%
if(session.getAttribute(whatever)==null)
{
%
jsp:forward page=some logout page.jsp/
%}%
-Original Message-
From: Lior Shliechkorn [mailto:liorshliech;yahoo.com]
Sent: Monday, October 21, 2002 1:40 PM
To: Tomcat
Subject: Session Time out - Tomcat
When Tomcat times a session out, as instructed in the web.xml, is there a
way to capture that so a page can be displayed that the session has timed
out, or even prompt the user if he would like to continue being logged on?
Thanks,
Lior
-
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
Session Time out - Tomcat
When Tomcat times a session out, as instructed in the web.xml, is there a way to capture that so a page can be displayed that the session has timed out, or even prompt the user if he would like to continue being logged on? Thanks, Lior - Do you Yahoo!? Y! Web Hosting - Let the expert host your web site
Re: Session Time out - Tomcat
Yes. Using the HttpSession object, or I believe in the new J2ee API there is a HttpSessionListener object, you can test if the session is valid. If it is not then redirect to wherever you want. Probably the simplest way is to test via if(request.getSession() == null) then go somewhere else On Mon, 2002-10-21 at 10:40, Lior Shliechkorn wrote: When Tomcat times a session out, as instructed in the web.xml, is there a way to capture that so a page can be displayed that the session has timed out, or even prompt the user if he would like to continue being logged on? Thanks, Lior - Do you Yahoo!? Y! Web Hosting - Let the expert host your web site ___ David H. Patton C.O.S. [EMAIL PROTECTED] x4727 - desk (202) 276-8998 - pcs -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
RE: Session Time out - Tomcat
On Mon, 21 Oct 2002 [EMAIL PROTECTED] wrote:
Thanks for the comments, Milt.
From a JSP (To my understanding anyway - I just re-checked it in a
book) - it would appear you CAN assume the session object is not
null - I quote: 'An implicit script language variable of type
javax.servlet.http.HttpSession is available for use in the page,
with the name session. It will represent the existing session, or
if there is no session existing already a new session will be
created.' - unless one sets explicitly to not use sessions, anyway
:)
Granted, if I had pulled the session out of the HttpServletRequest -
that would be another matter and it would be wise to check whether
that session object was null or not.
But - anyway - we're splitting hairs :)
Ah, OK, I'm more used to using sessions in servlets, not JSPs, so I
wasn't 100% sure about this.
And you're right - I didn't address the question as it was asked but
I guess I read it wrong! No matter!
I believe Dave (who replied earlier) might be on the right track
with the HttpSessionListener class but I would have to play around
with that a bit to see how it works!
Well, some of the session stuff should help -- but depending on
exactly what they want to do, they may need to roll their own, at
least for some of it.
-Original Message-
From: Milt Epstein [mailto:mepstein;uiuc.edu]
Sent: Monday, October 21, 2002 3:04 PM
To: Tomcat Users List
Subject: RE: Session Time out - Tomcat
On Mon, 21 Oct 2002 [EMAIL PROTECTED] wrote:
Lior,
One easy way to do this is to store something in the session when
you log the user on (a user name or some unique piece of
information) - you probably already do this - and when you do any
jsps or servlets, try doing session.getAttribute on that item - if
its null - the session is timed out.
I am sure there are other ways to do this but this is definitely an
easy way to do it!
I think this is an easy way to get NullPointerException's as well :-).
(You're not checking that session is not null, and I don't think you
can assume that.)
And I don't think you're really addressing the original question
(although I'm not sure the original question is so clear).
Basically, I think what the original poster asked about can be done,
but they'll have to do most of it themselves.
Frankly, one thing I'm a little unclear on, if a session is
invalidated, either via a timeout or programmatically, is what will
happen to next time getSession is called (with the create parameter
set to false). Will it return null, or will it return an invalidated
session. I'd think it'd return null, but then I'm not sure of why
isRequestedSessionIdValid exists. This makes a difference with regard
to whether/how you can distinguish between someone who's new to the
app and someone who was there before but who's session was invalidated.
e.g
%
if(session.getAttribute(whatever)==null)
{
%
jsp:forward page=some logout page.jsp/
%}%
-Original Message-
From: Lior Shliechkorn [mailto:liorshliech;yahoo.com]
Sent: Monday, October 21, 2002 1:40 PM
To: Tomcat
Subject: Session Time out - Tomcat
When Tomcat times a session out, as instructed in the web.xml, is there a
way to capture that so a page can be displayed that the session has timed
out, or even prompt the user if he would like to continue being logged on?
Thanks,
Lior
Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
--
To unsubscribe, e-mail:
mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail:
mailto:tomcat-user-help;jakarta.apache.org
Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: Testing session time-out behaviour
Although it isn't session timeout specifically, couldn't you just invalidate (invalidate() method on session object) the session by going to a specific url - eg servlet Would that emulate the behaviour you are trying to achieve? Craig R. McClanahan wrote: On Thu, 15 Aug 2002 [EMAIL PROTECTED] wrote: Date: Thu, 15 Aug 2002 14:07:13 -0500 From: [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Testing session time-out behaviour Hi, I have a web app with some specific requirements for session timeout. I would like to write automated acceptance tests to verify these requirements, and am faced with some options: - set web.xml to time-out in 1 minute, have my tests wait for just over a minute to force time-out - talk to my server (tomcat during testing) from the test client code (junit tests using httpunit) to somehow request it to time out - execute the shutdown / startup commands from the client code (session information for tomcat 4.0 goes away when i do this). I have a small app, so startup shutdown are both relatively quick (seconds). Waiting just over a minute is not guaranteed to work the way you think. The reason for this is that session timeouts are performed in a background thread that only runs periodically (typically every 15 seconds). Waiting a minute is a pain, because I have to change web.xml and reset it, also because I have a lot of screens and behaviours to test (hence the desire to automate), so even setting down to a minute I expect it would take my automated test suite from what is now about 5 minutes to run to about 30 minutes. One thing to consider is that you can call session.setMaxInactiveInterval() on a session instance itself, at a granularity of seconds. You still need to deal with the 15 second time though (unless you want to just simulate a timeout by forcibly invalidating a session) -- you could add a special URL to your webapp to do this in a test environment. As far as communicating with tomcat goes, I tried doing a get on the manager urls to reload the app, also to stop followed by start - but this does not appear to cause it to lose the session information. That's true ... Tomcat saves and reloads sessions across a restart. As far as executing startup / shutdown batch files, the rub is waiting on the shutdown and startup to complete before proceeding with the test. It is proving to be extremely tricky to do. You can forcibly eliminate any sessions saved by the previous shutdown by deleting the SESSIONS.ser file in the work directory for your webapp. So, from a java test client, is there a supported and relatively easy way for me to get tomcat to drop a session in the middle of a test? Suggestions? j Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Testing session time-out behaviour
On Thu, 15 Aug 2002 [EMAIL PROTECTED] wrote: Date: Thu, 15 Aug 2002 14:07:13 -0500 From: [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Testing session time-out behaviour Hi, I have a web app with some specific requirements for session timeout. I would like to write automated acceptance tests to verify these requirements, and am faced with some options: - set web.xml to time-out in 1 minute, have my tests wait for just over a minute to force time-out - talk to my server (tomcat during testing) from the test client code (junit tests using httpunit) to somehow request it to time out - execute the shutdown / startup commands from the client code (session information for tomcat 4.0 goes away when i do this). I have a small app, so startup shutdown are both relatively quick (seconds). Waiting just over a minute is not guaranteed to work the way you think. The reason for this is that session timeouts are performed in a background thread that only runs periodically (typically every 15 seconds). Waiting a minute is a pain, because I have to change web.xml and reset it, also because I have a lot of screens and behaviours to test (hence the desire to automate), so even setting down to a minute I expect it would take my automated test suite from what is now about 5 minutes to run to about 30 minutes. One thing to consider is that you can call session.setMaxInactiveInterval() on a session instance itself, at a granularity of seconds. You still need to deal with the 15 second time though (unless you want to just simulate a timeout by forcibly invalidating a session) -- you could add a special URL to your webapp to do this in a test environment. As far as communicating with tomcat goes, I tried doing a get on the manager urls to reload the app, also to stop followed by start - but this does not appear to cause it to lose the session information. That's true ... Tomcat saves and reloads sessions across a restart. As far as executing startup / shutdown batch files, the rub is waiting on the shutdown and startup to complete before proceeding with the test. It is proving to be extremely tricky to do. You can forcibly eliminate any sessions saved by the previous shutdown by deleting the SESSIONS.ser file in the work directory for your webapp. So, from a java test client, is there a supported and relatively easy way for me to get tomcat to drop a session in the middle of a test? Suggestions? j Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Testing session time-out behaviour
You can forcibly eliminate any sessions saved by the previous shutdown by deleting the SESSIONS.ser file in the work directory for your webapp. Thanks, Craig. Deleting this file between a stop and start application url request from the test client did the trick - finally able to simulate session timeout from the acceptance tests, and they run pretty quickly. Gracias, jimbo -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
session time out
Hi All What is the default value of session timeout in tomcat if we dont provide any value in web.xml file. I am using JBoss-2.4.1_Tomcat-3.2.3. Is the session timeout is total of activity+inactivity? Thanks in advance Mahesh -Original Message- From: kelly, Burrowa [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 03, 2002 10:23 AM To: [EMAIL PROTECTED] Subject: About reloading of classes I use tomcat 4.0.1. I have reloadable=true for my context in server.xml. But when I compile 4 classes, only one class is getting loaded - atleast that is what is shown in the tomcat runtime window. I am not sure if all the classes have been reloaded. What are others observations on this? __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Time out error
Hi All I am using loadrunner to test my application. When i am setting 5 users to connect to my server (I am using JBoss-2.4.1_Tomcat-3.2.3) ,it is successful. But when increases the count to 10 users, its giving timeout error for everyone. Can any body please solve out issue. thanks a lot in advance Mahesh -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Time out / Idle
Hi there folks, anybody would know why tomcat dies after a while of no use? i don't see a property specifying idle time, nor errors in the logs. Is this a bug? Many thanks, Gaston. Gaston R. Cangiano Kite Design Studio Tel: 510-486-8271 Fax: 425-930-1047 [EMAIL PROTECTED] http://www.kitedesign.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Time out / Idle
Gaston, Tomcat will not time out and shut down as far as I am aware. It never has on me and it runs for days and weeks between reboots. Soon to be months hopefully. Perhaps it is being started by someone with less then root privileges and when they log out the process goes with them. ?.. What version are you using. I use 3.2 and JDK 1.3 and have very stable performance. Do your system resources ever become critical? Power shortages, rolling blackouts... What OS are you using? good luck, Craig -Original Message- From: Gaston R. Cangiano [mailto:[EMAIL PROTECTED]] Sent: Friday, January 19, 2001 4:17 PM To: [EMAIL PROTECTED] Subject: Time out / Idle Hi there folks, anybody would know why tomcat dies after a while of no use? i don't see a property specifying idle time, nor errors in the logs. Is this a bug? Many thanks, Gaston. Gaston R. Cangiano Kite Design Studio Tel: 510-486-8271 Fax: 425-930-1047 [EMAIL PROTECTED] http://www.kitedesign.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Time out / Idle
thanks for responding so fast Craig! that's good to hear. When you say "days and hopefully months", do you mean "without usage", that is, does it shutdown when IDLE for a long time? the owner of the process is root and it's fine that way; version of tomcat is the latest stable release and jdk is 1.2, no resource or power shortages (for now, util the turn the swith off on us :-) It's running on Linux 2.2.5-15. Thanks, Gaston. -Original Message- From: Craig O'Brien [mailto:[EMAIL PROTECTED]] Sent: Friday, January 19, 2001 4:36 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Time out / Idle Gaston, Tomcat will not time out and shut down as far as I am aware. It never has on me and it runs for days and weeks between reboots. Soon to be months hopefully. Perhaps it is being started by someone with less then root privileges and when they log out the process goes with them. ?.. What version are you using. I use 3.2 and JDK 1.3 and have very stable performance. Do your system resources ever become critical? Power shortages, rolling blackouts... What OS are you using? good luck, Craig -Original Message- From: Gaston R. Cangiano [mailto:[EMAIL PROTECTED]] Sent: Friday, January 19, 2001 4:17 PM To: [EMAIL PROTECTED] Subject: Time out / Idle Hi there folks, anybody would know why tomcat dies after a while of no use? i don't see a property specifying idle time, nor errors in the logs. Is this a bug? Many thanks, Gaston. Gaston R. Cangiano Kite Design Studio Tel: 510-486-8271 Fax: 425-930-1047 [EMAIL PROTECTED] http://www.kitedesign.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re : Session Time Out
hi there is no built in function to get the session has timed out or not. Follow the steps. 1. Setting the max interval the session should be valid ...session.setMaxInactiveInterval(3600) this 3600 = 72 * 1000 milli seconds. 2. fine now u have set the session should exist for 2 hrs 3. Get the time when the page is last accessed 4. Calculate the time difference between when the page is last accsessed and when the page is accessed now . ( For getting the page last accessed ...u have session.getLastAccessesTime() - This will return when he last acessed the poage ) u know how many hrs / mins / secs the session should be valid ...just subtract the current tiume from last acesed time .. u will get a result . check the result with the time u have given for session . If it exceeds ...redirect him . Hope this will help Narayanan. s.w engineer Enhancement Technologies India. _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
