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 ?!
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.
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 ?!
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 ?!
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
sending redirects to relative/absolute URLs
Hi, Does anybody know why Tomcat always redirects to absolute links? I looked at the implementation and the sendRedirect calls the toAbsolute method which always constructs an absolute URL. Is there any way to make Tomcat return relative URLs the way they were requested for redirecting? Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
RE: sending redirects to relative/absolute URLs
Len, Can you point me a place where I can read about these HTTP requirements? I thought this might be the case but I couldn't find anything helpful online. Probably didn't search enough. -Original Message- From: Len Popp [mailto:[EMAIL PROTECTED] Sent: Friday, May 20, 2005 9:28 AM To: Tomcat Users List Subject: Re: sending redirects to relative/absolute URLs No, because the HTTP protocol requires an absolute URL in redirect responses. On 5/20/05, Angelov, Rossen [EMAIL PROTECTED] wrote: Hi, Does anybody know why Tomcat always redirects to absolute links? I looked at the implementation and the sendRedirect calls the toAbsolute method which always constructs an absolute URL. Is there any way to make Tomcat return relative URLs the way they were requested for redirecting? Ross 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.
basic authentication and custom 401 error page
Hi, We are running our applications on Tomcat 4 and 5. On both versions we are having problems with the basic authentication. The problem is that I haven't found a way to overwrite the default 401 error page with a custom page. If I add an error-page element in web.xml for error 401 error-page error-code401/error-code location/err401.html/location /error-page then the username/password window is completely ignored and the err401.html page displayed. I searched the archives and different forums but there are a lot of people asking for help with similar problems without any responses. I found two reported bugs related to that issue: 12194 and 22617 for tomcat 3 and 4 I didn't find any bugs for tomcat 5 but it still not working for me. Any suggestions will be appreciated. Thanks, Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
RE: Tomcat 5 out of memory
Thanks a lot! I appreciate your help. Ross -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 8:03 AM To: Tomcat Users List Subject: RE: Tomcat 5 out of memory Hi, Incremental GC has nothing to do with it. Rebuilding the cache (whatever that means) has nothing to do with it. This has been discussed numerous times in the past, and has to do with the permanent generation as you've surmised. See for example: http://marc.theaimsgroup.com/?l=tomcat-userm=107590242329345w=2 http://marc.theaimsgroup.com/?l=tomcat-userm=107996450114197w=2 http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20758 http://marc.theaimsgroup.com/?l=tomcat-userm=107048670308534w=2 Ahh, I'm tired of searching. Yoav Shapira Millennium Research Informatics -Original Message- From: Angelov, Rossen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 9:39 PM To: 'Tomcat Users List' Subject: RE: Tomcat 5 out of memory That sounds like a reasonable explanation. Then, the only solution I can see is to set the development environment not a virtual server per developer but a Tomcat instance per person and if the OutOfMemory error happens again, restarting that Tomcat instance won't interfere with the rest of the developers' work. Do you by any chance have a link to that discussion you mentioned? I searched the archive and found some opinions, the closest was this one ...common classloader repositories (as well as shared and server) do not get discarded on webapp reload. They can't, as that might destroy other webapps. This probably raises the question in what cases the reload should be used. Thanks, Ross -Original Message- From: Parsons Technical Services [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 7:54 PM To: Tomcat Users List Subject: Re: Tomcat 5 out of memory Ross, If my memory serves me right (which is rarely) there was a discussion on the list about this. I believe the comment was that during reloads there are references to objects that don't get released when a context is undeployed. The memory is lost until a restart. In production this should not be an issue because of the infrequent occurrence of redeploys. Doug www.parsonstechnical.com - Original Message - From: Angelov, Rossen [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 7:13 PM Subject: RE: Tomcat 5 out of memory I don't understand why rebuilding the cache would take more memory than what was originally required. It just doesn't sound right or it is a memory leak when you use the stop/start or reload options. Giving a higher priority to this process is not a very good option because in our case it is a development UNIX server and there are database and other peoples' processes running. Increasing the memory heap size will just slow down the occurrence of that OutOfMemory error instead of preventing it. I'm actually looking for a long term solution because it may be critical whether to use tomcat for production and live web servers. Thanks, Ross -Original Message- From: Nicholas Bernstein [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 5:29 PM To: Tomcat Users List Subject: Re: Tomcat 5 out of memory rebuilding the cache, I would imagine. I'm not sure how you would reduce it though, it's a good thing(tm) -- really, it's reducing the memory usage by 2-3MB once the cache is rebuilt. This is just an (somewhat) educated guess, though. I suppose you could give it a higher priority so it could speed it up, and take up more resources, for a shorter period of time, or alternately, throw some hardware at it, and add some more memory. On Wed, 2004-04-07 at 15:17, Angelov, Rossen wrote: Hi, We are having problems with Tomcat when restarting the virtual servers or the contexts - the memory usage goes up with about 2-3 MB per restart. We have the following java options when starting Catalina: -Xms128m -Xmx256m -verbose:gc Does anybody know what's causing such a behavior and how it can be limited? Thanks, Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. -- +---+ | Nicholas Bernstein| [EMAIL PROTECTED] | | UNIX Systems Administrator| http://www.docmagic.com | | Document Systems Inc. | | | gpg: F706 8C4E 78FA 53A0 019F D983 FE28 2002 D1F3 | +---+ - 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
Tomcat 5 out of memory
Hi, We are having problems with Tomcat when restarting the virtual servers or the contexts - the memory usage goes up with about 2-3 MB per restart. We have the following java options when starting Catalina: -Xms128m -Xmx256m -verbose:gc Does anybody know what's causing such a behavior and how it can be limited? Thanks, Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
RE: Tomcat 5 out of memory
I don't understand why rebuilding the cache would take more memory than what was originally required. It just doesn't sound right or it is a memory leak when you use the stop/start or reload options. Giving a higher priority to this process is not a very good option because in our case it is a development UNIX server and there are database and other peoples' processes running. Increasing the memory heap size will just slow down the occurrence of that OutOfMemory error instead of preventing it. I'm actually looking for a long term solution because it may be critical whether to use tomcat for production and live web servers. Thanks, Ross -Original Message- From: Nicholas Bernstein [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 5:29 PM To: Tomcat Users List Subject: Re: Tomcat 5 out of memory rebuilding the cache, I would imagine. I'm not sure how you would reduce it though, it's a good thing(tm) -- really, it's reducing the memory usage by 2-3MB once the cache is rebuilt. This is just an (somewhat) educated guess, though. I suppose you could give it a higher priority so it could speed it up, and take up more resources, for a shorter period of time, or alternately, throw some hardware at it, and add some more memory. On Wed, 2004-04-07 at 15:17, Angelov, Rossen wrote: Hi, We are having problems with Tomcat when restarting the virtual servers or the contexts - the memory usage goes up with about 2-3 MB per restart. We have the following java options when starting Catalina: -Xms128m -Xmx256m -verbose:gc Does anybody know what's causing such a behavior and how it can be limited? Thanks, Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. -- +---+ | Nicholas Bernstein| [EMAIL PROTECTED] | | UNIX Systems Administrator| http://www.docmagic.com | | Document Systems Inc. | | | gpg: F706 8C4E 78FA 53A0 019F D983 FE28 2002 D1F3| +---+ - 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: Tomcat 5 out of memory
That sounds like a reasonable explanation. Then, the only solution I can see is to set the development environment not a virtual server per developer but a Tomcat instance per person and if the OutOfMemory error happens again, restarting that Tomcat instance won't interfere with the rest of the developers' work. Do you by any chance have a link to that discussion you mentioned? I searched the archive and found some opinions, the closest was this one ...common classloader repositories (as well as shared and server) do not get discarded on webapp reload. They can't, as that might destroy other webapps. This probably raises the question in what cases the reload should be used. Thanks, Ross -Original Message- From: Parsons Technical Services [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 7:54 PM To: Tomcat Users List Subject: Re: Tomcat 5 out of memory Ross, If my memory serves me right (which is rarely) there was a discussion on the list about this. I believe the comment was that during reloads there are references to objects that don't get released when a context is undeployed. The memory is lost until a restart. In production this should not be an issue because of the infrequent occurrence of redeploys. Doug www.parsonstechnical.com - Original Message - From: Angelov, Rossen [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 7:13 PM Subject: RE: Tomcat 5 out of memory I don't understand why rebuilding the cache would take more memory than what was originally required. It just doesn't sound right or it is a memory leak when you use the stop/start or reload options. Giving a higher priority to this process is not a very good option because in our case it is a development UNIX server and there are database and other peoples' processes running. Increasing the memory heap size will just slow down the occurrence of that OutOfMemory error instead of preventing it. I'm actually looking for a long term solution because it may be critical whether to use tomcat for production and live web servers. Thanks, Ross -Original Message- From: Nicholas Bernstein [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 5:29 PM To: Tomcat Users List Subject: Re: Tomcat 5 out of memory rebuilding the cache, I would imagine. I'm not sure how you would reduce it though, it's a good thing(tm) -- really, it's reducing the memory usage by 2-3MB once the cache is rebuilt. This is just an (somewhat) educated guess, though. I suppose you could give it a higher priority so it could speed it up, and take up more resources, for a shorter period of time, or alternately, throw some hardware at it, and add some more memory. On Wed, 2004-04-07 at 15:17, Angelov, Rossen wrote: Hi, We are having problems with Tomcat when restarting the virtual servers or the contexts - the memory usage goes up with about 2-3 MB per restart. We have the following java options when starting Catalina: -Xms128m -Xmx256m -verbose:gc Does anybody know what's causing such a behavior and how it can be limited? Thanks, Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. -- +---+ | Nicholas Bernstein| [EMAIL PROTECTED] | | UNIX Systems Administrator| http://www.docmagic.com | | Document Systems Inc. | | | gpg: F706 8C4E 78FA 53A0 019F D983 FE28 2002 D1F3 | +---+ - 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. - 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.
Symbolic links in WEB-INF directory, Tomcat 5
Hi, Can Tomcat work with symbolic links in WEB-INF instead of real directories? I have allowLinking set up to true and the Resources element is in the corresponding context but still Tomcat will fail deploying the application if I have symbolic links. Resources className=org.apache.naming.resources.FileDirContext allowLinking=true caseSensitive=true / My goal is to be able to link most of the contexts (from different virtual hosts) to the same WEB-INF/classes and WEB-INF/lib. Thanks, Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
Threads in Tomcat 5
Hi, I'm trying to understand how exactly Tomcat 5 is organized to work with threads. Is there any documentation on how the connector is using the threads? What happens in the thread pool, how exactly the are threads picked from the pool and what is their state? And what happens with the released threads? Our login application is having problems when retrieving data from the requests. I was debugging the process by printing out the current thread name and the request parameter values. Everything works fine when there is a different thread assigned to each request: request 1 current thread: http8080-Processor25 request 2 current thread: http8080-Processor23 request 3 current thread: http8080-Processor22 When an old thread is used for the new request, things don't work (usually the wrong parameter values are returned) and the debug output looks like this: request 1 current thread: http8080-Processor25 request 2 current thread: http8080-Processor23 request 3 current thread: http8080-Processor25 Our application uses ThreadLocal to create a Hashtable with the current request parameters as a cache storage. Very often the same thread is used for more than one requests, the parameter values are retrieved from the cache instead of using the new values. This completely breaks the logic and the login process fails. Thanks, Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
RE: Threads in Tomcat 5
Well, the login requirements are not that simple to explain in few lines. Some pages require authentication some don't, so it won't be appropriate to do this when the HttpSession is first started. ThreadLocal is used to identify the current thread (assuming that's for the current request) to get the request parameters and create a hashtable for caching purpose (this was done to speed up the registration process where over 30 demographic fields are passed between pages). The same logic is used when logging in or uploading a file with MultipartRequest. The applications were originally created 2-3 years ago to work on iPlanet and now I'm trying move them to Tomcat but it looks like there will be lot of problems. Ross -Original Message- From: Peter Lin [mailto:[EMAIL PROTECTED] Sent: Thursday, April 01, 2004 11:21 AM To: Tomcat Users List Subject: Re: Threads in Tomcat 5 why do you want to use a thread to manage authentication? given the requestProcessor threads are reused, it makes no sense to use the thread for the mapping. you're better off just authenticating the first time and setting the HttpSession, rather than look up the thread. I'm probably missing something. peter Angelov, Rossen [EMAIL PROTECTED] wrote: Hi, I'm trying to understand how exactly Tomcat 5 is organized to work with threads. Is there any documentation on how the connector is using the threads? What happens in the thread pool, how exactly the are threads picked from the pool and what is their state? And what happens with the released threads? Our login application is having problems when retrieving data from the requests. I was debugging the process by printing out the current thread name and the request parameter values. Everything works fine when there is a different thread assigned to each request: request 1 current thread: http8080-Processor25 request 2 current thread: http8080-Processor23 request 3 current thread: http8080-Processor22 When an old thread is used for the new request, things don't work (usually the wrong parameter values are returned) and the debug output looks like this: request 1 current thread: http8080-Processor25 request 2 current thread: http8080-Processor23 request 3 current thread: http8080-Processor25 Our application uses ThreadLocal to create a Hashtable with the current request parameters as a cache storage. Very often the same thread is used for more than one requests, the parameter values are retrieved from the cache instead of using the new values. This completely breaks the logic and the login process fails. Thanks, Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. - Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway - Enter today This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
RE: Threads in Tomcat 5
I'll consider the HttpSession as an option and will implement sorting to see if it work for us. I'm not sure what you mean by single-sign-on application but our authentication system uses a eRights, a product of eMETA, to authenticate users and give access only to certain resources (usually pages) based on the product and the policy information. Each http session is related to an eRights session. Ross -Original Message- From: Peter Lin [mailto:[EMAIL PROTECTED] Sent: Thursday, April 01, 2004 12:26 PM To: Tomcat Users List Subject: RE: Threads in Tomcat 5 hit send too soon. Another approach which I've used and is common is to have the notion of access control privledge like Unix file privledges. Each page has a set privledge level and once the user is authenticated, the page checks the users access level. there are numerous other variations on this for single-sign-on applications. peter Angelov, Rossen [EMAIL PROTECTED] wrote: Well, the login requirements are not that simple to explain in few lines. Some pages require authentication some don't, so it won't be appropriate to do this when the HttpSession is first started. ThreadLocal is used to identify the current thread (assuming that's for the current request) to get the request parameters and create a hashtable for caching purpose (this was done to speed up the registration process where over 30 demographic fields are passed between pages). The same logic is used when logging in or uploading a file with MultipartRequest. The applications were originally created 2-3 years ago to work on iPlanet and now I'm trying move them to Tomcat but it looks like there will be lot of problems. Ross -Original Message- From: Peter Lin [mailto:[EMAIL PROTECTED] Sent: Thursday, April 01, 2004 11:21 AM To: Tomcat Users List Subject: Re: Threads in Tomcat 5 why do you want to use a thread to manage authentication? given the requestProcessor threads are reused, it makes no sense to use the thread for the mapping. you're better off just authenticating the first time and setting the HttpSession, rather than look up the thread. I'm probably missing something. peter Angelov, Rossen wrote: Hi, I'm trying to understand how exactly Tomcat 5 is organized to work with threads. Is there any documentation on how the connector is using the threads? What happens in the thread pool, how exactly the are threads picked from the pool and what is their state? And what happens with the released threads? Our login application is having problems when retrieving data from the requests. I was debugging the process by printing out the current thread name and the request parameter values. Everything works fine when there is a different thread assigned to each request: request 1 current thread: http8080-Processor25 request 2 current thread: http8080-Processor23 request 3 current thread: http8080-Processor22 When an old thread is used for the new request, things don't work (usually the wrong parameter values are returned) and the debug output looks like this: request 1 current thread: http8080-Processor25 request 2 current thread: http8080-Processor23 request 3 current thread: http8080-Processor25 Our application uses ThreadLocal to create a Hashtable with the current request parameters as a cache storage. Very often the same thread is used for more than one requests, the parameter values are retrieved from the cache instead of using the new values. This completely breaks the logic and the login process fails. Thanks, Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. - Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway - Enter today This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. - Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway - Enter today This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
RE: Tomcat mixing different log4j FileAppenders
Log4J.jar is in extensions directory in java1.4/jre/lib
It is configured in a way that any application that uses our java1.4
installation can have access to this extensions directory. In this case
Tomcat is started with first setting JAVA_HOME to use the same java1.4
installation.
Here are the settings from our log4j properties file:
--
log4j.rootCategory=DEBUG, LOG
log4j.appender.LOG=org.apache.log4j.FileAppender
log4j.appender.LOG.File=/filepath1/log4j.log(and it's filepath2 for the
other log file)
log4j.appender.LOG.layout=org.apache.log4j.PatternLayout
log4j.appender.LOG.layout.ConversionPattern=%d{ABSOLUTE} %p - %m%n
--
I don't see how these settings can cause such a mismatch with the log data.
Ross
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 7:58 AM
To: Tomcat Users List
Subject: RE: Tomcat mixing different log4j FileAppenders
Hi,
How are you configuring log4j? Where is log4j.jar?
Yoav Shapira
Millennium Research Informatics
-Original Message-
From: Angelov, Rossen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 24, 2004 7:45 PM
To: 'Tomcat Users List'
Subject: Tomcat mixing different log4j FileAppenders
I'm using Tomcat 5.0.19 with two different web applications running on
different virtual hosts and Log4j to log errors.
Each application has its own log4j FileAppender and is supposed to
write to
its own log file.
I've noticed few times that Tomcat sends the log information to the
same
log
file which isn't right. Both applications are not supposed to share
anything
except the container. The issue is resolved after restarting Tomcat but
it
appears randomly again.
Has anybody experienced similar problems or do you have any suggestions
what
might be set incorrectly in my case?
Thanks,
Ross
This communication is intended solely for the addressee and is
confidential and not for third party unauthorized distribution.
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]
This communication is intended solely for the addressee and is
confidential and not for third party unauthorized distribution.
Cookie values
How are the cookies treated by Tomcat?
take this cookie for example: name=lastname, firstname
for version 0 the comma and the space are not valid but for version 1 they
are
If I have my Cookie version set to 1 the cookie looks like this:
name=lastname, firstname when read by JavaScript
if read by jsp with this code
Cookie[] c = request.getCookies();
for (int i=0; c != null i c.length; i++){
out.write(br+i+: +c[i].getName()+=+c[i].getValue());
}
it splits the name cookie in two separate cookies:
1. name=lastname and
2. firstname=
If I have my Cookie version set to 0 the cookie looks like this:
name=lastname, firstname when read by JavaScript
but the server throws this error java.lang.IllegalArgumentException:
lastname, firstname
Which is the right way of creating and reading cookie values when using
Tomcat?
I was using IE6.0 for these tests.
Thanks,
Ross
This communication is intended solely for the addressee and is
confidential and not for third party unauthorized distribution.
where to place the context for the default web application
Hi, According to the Server Configuration Reference, it is not recommended to place Context elements directly in the server.xml My question is where to place the context element for the default web application and how to name it because the context path in this case is a zero-length string? Thanks, Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
RE: where to place the context for the default web application
I called it default.xml and placed it under $CATALINA_HOME/conf/[enginename]/[hostname]/ directory. Looks like it's working. Thanks a lot, Ross -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 11:16 AM To: Tomcat Users List Subject: RE: where to place the context for the default web application Hi, The default web application is simply the one whose path (not docBase) is . You can name it and its context file anything you want, e.g. myapp.xml, and use whatever docBase you want. Yoav Shapira Millennium Research Informatics -Original Message- From: Angelov, Rossen [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 12:10 PM To: '[EMAIL PROTECTED]' Subject: where to place the context for the default web application Hi, According to the Server Configuration Reference, it is not recommended to place Context elements directly in the server.xml My question is where to place the context element for the default web application and how to name it because the context path in this case is a zero-length string? Thanks, Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution. 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] This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
Tomcat mixing different log4j FileAppenders
I'm using Tomcat 5.0.19 with two different web applications running on different virtual hosts and Log4j to log errors. Each application has its own log4j FileAppender and is supposed to write to its own log file. I've noticed few times that Tomcat sends the log information to the same log file which isn't right. Both applications are not supposed to share anything except the container. The issue is resolved after restarting Tomcat but it appears randomly again. Has anybody experienced similar problems or do you have any suggestions what might be set incorrectly in my case? Thanks, Ross This communication is intended solely for the addressee and is confidential and not for third party unauthorized distribution.
log level set to DEBUG for serviceRequest
Hi, Tomcat 4.1.12 and Solaris 5.7 and JDK 1.4 Is there a way to change the log level to INFO or completely remove or change the location of bin/serviceRequest.log? Currently it prints out tons of lines that I don't really need in the bin directory. I was searching for serviceRequest in the conf directory but didn't find anything. Ross
Is this normal for Tomcat?
Hi, I'm using Tomcat 4.1.12 running on Solaris 5.7 Issue #1: There are two different contexts with different paths and different docBase. Two different servlets using two different log files (log4j). I was browsing the pages from the same browser window (IE 5.5) switching between both contexts when I noticed both servlets are writing to the same log file. Theoretically it's not supposed to happen because they use different configuration files and I haven't changed them for days. These servlets are completely independent from each other. Issue #2: Sometimes when multiple users access pages happen to share the same http responses: User1 can see the cookies and the pages that user2 requested. How is all this possible? Ross
RE: Is this normal for Tomcat?
No, they are completely different: webapps - context1 - WEB-INF - classes - com/context1 webapps - context2 - WEB-INF - classes - com/context2 I don't have anything in common/lib or common/classes used by these servlets. log4j has two different paths for the log files. I'm not using FileAppender, the servlets read in the log4j properties from a separate configuration files passed as param-value when the servlet starts. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 12:08 PM To: Tomcat Users List Subject: RE: Is this normal for Tomcat? Howdy, Do you have any code in the common/lib or common/classes repository that these two contexts share? Is the File destination for log4j's FileAppender configured to be the same for the two contexts? Yoav Shapira Millennium ChemInformatics -Original Message- From: Angelov, Rossen [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 1:01 PM To: 'Tomcat Users List' Subject: Is this normal for Tomcat? Hi, I'm using Tomcat 4.1.12 running on Solaris 5.7 Issue #1: There are two different contexts with different paths and different docBase. Two different servlets using two different log files (log4j). I was browsing the pages from the same browser window (IE 5.5) switching between both contexts when I noticed both servlets are writing to the same log file. Theoretically it's not supposed to happen because they use different configuration files and I haven't changed them for days. These servlets are completely independent from each other. Issue #2: Sometimes when multiple users access pages happen to share the same http responses: User1 can see the cookies and the pages that user2 requested. How is all this possible? Ross 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]
RE: Is this normal for Tomcat?
Sorry, I meant, I'm not using Apache's FileLogger to log this data. Both are using FileAppender with different log4j.appender.LOG.File property. The categoryFactory, rootCategory, PatternLayout and ConversionPattern are the same. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 12:19 PM To: Tomcat Users List Subject: RE: Is this normal for Tomcat? Howdy, How is log4j writing to a file if you're not using FileAppender? Yoav Shapira Millennium ChemInformatics -Original Message- From: Angelov, Rossen [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 1:15 PM To: 'Tomcat Users List' Subject: RE: Is this normal for Tomcat? No, they are completely different: webapps - context1 - WEB-INF - classes - com/context1 webapps - context2 - WEB-INF - classes - com/context2 I don't have anything in common/lib or common/classes used by these servlets. log4j has two different paths for the log files. I'm not using FileAppender, the servlets read in the log4j properties from a separate configuration files passed as param-value when the servlet starts. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 12:08 PM To: Tomcat Users List Subject: RE: Is this normal for Tomcat? Howdy, Do you have any code in the common/lib or common/classes repository that these two contexts share? Is the File destination for log4j's FileAppender configured to be the same for the two contexts? Yoav Shapira Millennium ChemInformatics -Original Message- From: Angelov, Rossen [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 1:01 PM To: 'Tomcat Users List' Subject: Is this normal for Tomcat? Hi, I'm using Tomcat 4.1.12 running on Solaris 5.7 Issue #1: There are two different contexts with different paths and different docBase. Two different servlets using two different log files (log4j). I was browsing the pages from the same browser window (IE 5.5) switching between both contexts when I noticed both servlets are writing to the same log file. Theoretically it's not supposed to happen because they use different configuration files and I haven't changed them for days. These servlets are completely independent from each other. Issue #2: Sometimes when multiple users access pages happen to share the same http responses: User1 can see the cookies and the pages that user2 requested. How is all this possible? Ross 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] 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]
RE: Is this normal for Tomcat?
I'm not sure if I understand the question very well but the original HttpServletResponse is being passed to the constructor of another class to create an instance and then this instance is changed in the course of the execution. At the end it's printed out through PrintWriter and then flushed. Ross -Original Message- From: Larry Meadors [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 12:56 PM To: [EMAIL PROTECTED] Subject: RE: Is this normal for Tomcat? This could be a thread safety issue. Are you using a servlet that has instance variables to generate the response? Larry [EMAIL PROTECTED] 05/30/03 11:33 AM I still have no clue as to the shared cookies issue. Yoav Shapira Millennium ChemInformatics -Original Message- From: Angelov, Rossen [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 1:28 PM To: 'Tomcat Users List' Subject: RE: Is this normal for Tomcat? Sorry, I meant, I'm not using Apache's FileLogger to log this data. Both are using FileAppender with different log4j.appender.LOG.File property. The categoryFactory, rootCategory, PatternLayout and ConversionPattern are the same. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 12:19 PM To: Tomcat Users List Subject: RE: Is this normal for Tomcat? Howdy, How is log4j writing to a file if you're not using FileAppender? Yoav Shapira Millennium ChemInformatics -Original Message- From: Angelov, Rossen [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 1:15 PM To: 'Tomcat Users List' Subject: RE: Is this normal for Tomcat? No, they are completely different: webapps - context1 - WEB-INF - classes - com/context1 webapps - context2 - WEB-INF - classes - com/context2 I don't have anything in common/lib or common/classes used by these servlets. log4j has two different paths for the log files. I'm not using FileAppender, the servlets read in the log4j properties from a separate configuration files passed as param-value when the servlet starts. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 12:08 PM To: Tomcat Users List Subject: RE: Is this normal for Tomcat? Howdy, Do you have any code in the common/lib or common/classes repository that these two contexts share? Is the File destination for log4j's FileAppender configured to be the same for the two contexts? Yoav Shapira Millennium ChemInformatics -Original Message- From: Angelov, Rossen [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 1:01 PM To: 'Tomcat Users List' Subject: Is this normal for Tomcat? Hi, I'm using Tomcat 4.1.12 running on Solaris 5.7 Issue #1: There are two different contexts with different paths and different docBase. Two different servlets using two different log files (log4j). I was browsing the pages from the same browser window (IE 5.5) switching between both contexts when I noticed both servlets are writing to the same log file. Theoretically it's not supposed to happen because they use different configuration files and I haven't changed them for days. These servlets are completely independent from each other. Issue #2: Sometimes when multiple users access pages happen to share the same http responses: User1 can see the cookies and the pages that user2 requested. How is all this possible? Ross 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] 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] 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
RE: Tomcat 4 and native threads
HotSpot VM supports only native threads and the Classic VM supports native and green threads. To force it to use either native or green threads you can do: java -native mypkg.MyClass javac -native MyClass.java or if you use classic VM java -green mypkg.MyClass javac -green MyClass.java -Original Message- From: John Corrigan [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 2:22 PM To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: Tomcat 4 and native threads Doesn't the thread model depend on the JVM? -Original Message- From: Michenaud Laurent [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 12:19 PM To: [EMAIL PROTECTED] Subject: Tomcat 4 and native threads Hi, Tomcat 4 is using green threads, am i wrong ? how can i make it working with native threads ? thanks - 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]
