Re: servlet mapping request
Hello Tomcat Users. I've researched Linux books for a solution and no luck on httpd.conf. So I am guessing all I need to do is change the following in httpd.conf FROM : LoadModule jk_module libexec/mod_jk.so AddModule mod_jk.c VirtualHost 64.235.243.224 ServerAlias nbfc.us ServerAdmin [EMAIL PROTECTED] DocumentRoot /home/nbfcus/public_html BytesLog domlogs/nbfc.us-bytes_log ServerName www.nbfc.us User nbfcus Group nbfcus CustomLog /usr/local/apache/domlogs/nbfc.us combined ScriptAlias /cgi-bin/ /home/nbfcus/public_html/cgi-bin/ IfModule mod_jk.c JkMount /*.jsp ajp13 JkMount /servlet/* ajp13 JkMount /servlets/* ajp13 /IfModule /VirtualHost TO : LoadModule jk_module libexec/mod_jk.so AddModule mod_jk.c VirtualHost 64.235.243.224 ServerAlias nbfc.us ServerAdmin [EMAIL PROTECTED] DocumentRoot /home/nbfcus/public_html BytesLog domlogs/nbfc.us-bytes_log ServerName www.nbfc.us User nbfcus Group nbfcus CustomLog /usr/local/apache/domlogs/nbfc.us combined ScriptAlias /cgi-bin/ /home/nbfcus/public_html/cgi-bin/ IfModule mod_jk.c JkMount /*.jsp ajp13 JkMount /events/* ajp13 JkMount /servletHandler/* ajp13 /IfModule /VirtualHost On our host's website. All I did was replace /servlet/ with my desired servlet mappings. Would this work? - Original Message - From: Raymond P. Jones [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Tuesday, April 18, 2006 7:05 PM Subject: Re: servlet mapping request Hello Mark on Tomcat Users. 1. Tomcat version is 5.5.9 2. Content of web.xml in (public_html/WEB-INF/web.xml within 'nbfcus' homedir) : ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN http://java.sun.com/j2ee/dtds/web-app_2_2.dtd; web-app context-param param-namewebmaster/param-name param-value[EMAIL PROTECTED]/param-value descriptionThe EMAIL address of the administrator to whom questions and comments about this application should be addressed./description /context-param !-- Enable servlet mapping -- !-- To use these, you would need to call the mapped URL pattern from a JSP or servlet -- servlet servlet-nameEventsServlet/servlet-name servlet-classEventsServlet/servlet-class /servlet servlet servlet-nameservletHandler/servlet-name servlet-classservletHandler/servlet-class /servlet servlet-mapping servlet-nameEventsServlet/servlet-name url-pattern/events/url-pattern /servlet-mapping servlet-mapping servlet-nameservletHandler/servlet-name url-pattern*.do/url-pattern /servlet-mapping session-config session-timeout30/session-timeout /session-config /web-app 3. Here is requested info from httpd.conf: LoadModule jk_module libexec/mod_jk.so AddModule mod_jk.c VirtualHost 64.235.243.224 ServerAlias nbfc.us ServerAdmin [EMAIL PROTECTED] DocumentRoot /home/nbfcus/public_html BytesLog domlogs/nbfc.us-bytes_log ServerName www.nbfc.us User nbfcus Group nbfcus CustomLog /usr/local/apache/domlogs/nbfc.us combined ScriptAlias /cgi-bin/ /home/nbfcus/public_html/cgi-bin/ IfModule mod_jk.c JkMount /*.jsp ajp13 JkMount /servlet/* ajp13 JkMount /servlets/* ajp13 /IfModule /VirtualHost I hope this can help you to help me to determine problem. Thx, Raymond P. Jones Ph: 518-446-9845 E: [EMAIL PROTECTED] - Original Message - From: Mark Thomas [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Saturday, April 15, 2006 12:54 PM Subject: Re: servlet mapping request Info we need to help you: 1. Exact Tomcat version. I would be extremely surprised if this really is the most recent release (5.5.17) 2. The content of your web.xml 3. Given that you are using Apache as well, the relevant Jk directives from your httpd.conf file Related to point 3, can you direct your browser to Tomcat directly, bypassing Apache? If so, does this work? Mark Raymond P. Jones wrote: Hello Tomcat Users. I need your help regarding servlet mappings in our WEB-INF/web.xml file running on an Apache webserver with a Tomcat container(most recent release) on a public website. After putting our web.xml file in public\WEB-INF and asking our web host to restart Tomcat, our servlet mappings stilll do not work in our test web page. I've searched through many books, even a Tomcat Quickstart book and they all say Tomcat has to be restarted for the servlet mappings in web.xml to work. So we requested a Tomcat restart and after this, the servlet mapping we use gives a page not found error. When I use /servlet/EventsServlet in a link, it calls the servlet and it works, but according to Tomcat documentation this is a security issue that we don't want to implement. I'm hoping that you know what the solution(s) are and can point me in the right direction. I'm appreciative for assist
Re: Howto activate JSSESupport in Apache-mod_jk-Tomcat 5.5.x
Hi Mark, sorry, you misunderstood me. Of cause we already SSL for Apache, configured mod_jk to deliver certain SSL-Information etc. etc. etc. What Tomcat/Catalina doesn't support by default is getting a SSLSession based on the SSL-SessionID of a running SSL-Connection. So far I have found no information or documentation about how to activate SSL-based SessionManagement in Catalina, although it is part of the Servlet-API and I have found certain source-code in the catalina-connector-sourcetree that seem to work toward SSL-based SessionManagement. Hmm, I think I will try to contact the author of that sources to find out more about it. Oliver Schönwald Mark Thomas schrieb: Oliver Schoenwald wrote: If your are using mod_jk, you need to configure SSL on Apache. If you are using Tomcat on its own, read http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html Mark - 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]
Passing data across Tomcat installations
HI All, Is there a way to pass data (as sensitive as usrname) from one tomcat to another? To be more precise, I've an entry point server(Tomcat server), which shows links to many other other Tomcat installations. The user authenticates on the entry point server and then sees several links (to other tomcat servers). Now if he clicks on one of those links, I want the username to be passed from the entry point server to the secondary tomcat server. I've found that neither the session nor the request attributes are available on the other side. Is there any other way? -- Vivek. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 5.0.28 windows service path configuration
Title: signature Hello, I need your help to solve a problem, i would like to migrate my app from Tomcat 4.1.31 to 5.0.28 and use it as Windows Service. I would like to pass a directory Path during Tomcat 5.0.28 windows service installation. I can do it easily with Tomcat 4.1.31 when i use this command in a batch file : tomcat.exe -install "Skyview Server" ... -path "c:\firstdirectory;c:\seconddirectory" But I can't do it with Tomcat 5.0.28 when i use this command : service.bat install Skyview ... --path "c:\firstdirectory;c:\seconddirectory" I tried lots of workarounds to pass a path to Tomcat 5.0.28 during windows service installation, is there a way to configure Tomcat in this mode ? I would like to avoid update windows environment path in environment variable and i would prefer to use a Tomcat service for it. Thanks very much for your help -- Ludovic Larch Software Engineer Development Software Team [EMAIL PROTECTED] 12, rue des Landelles - Immeuble Hercule 2 - 35510 Cesson Svign - France Tel.: + 33 (0) 2 99 86 98 07 - Fax: + 33 (0) 2 99 86 98 01 The present email and all information included therein do not constitute a legal agreement accorded by JOUVE. All legal agreements must be formulated in writing on paper by a legal representative of JOUVE. If you have received this email by mistake, please inform us of that fact and destroy the email and any documents it might contain Thank you for your cooperation.
Tomcat 5.0 : how to redirect a 401 error to a specific page
Hello, Our webapp runs with Tomcat 5, Apache 2.0.46 from RHEL3, Tomcat 5.0.27 from JPackage, and communicate via mod_jk 1.2.6. Here's the problem we face: our webapp sends notifications by email, with a link to a JSP requiring a classical HTTP authentication dialog. This same page is used for the login form into the application, and its behaviour is controlled by the parameters passed to it. When the user DOES NOT submit any information (ie, it presses Cancel on the dialog box), Tomcat shows its 401 page. I've tried the following: * add an ErrorDocument directive to Apache config: no go; * add an error-page tag with error-code and location into the web-app section of WEB-INF/web.xml with the location pointing back to the same page, with no parameters: no go either... It's even worse in this case, since the Tomcat 401 page shows directly, the HTTP auth dialog doesn't even appear. I haven't tried _both_ at the same time, but I believe it wouldn't be the solution. As I'm not really fluent with Apache/Tomcat and webapps, I don't know where I should look at to solve the problem. Any hints would be more than welcome! Thanks for reading, and it'd be nice to reply-all, since the two CC are not on the list, -- Francis Galiegue, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] One2team - 12bis rue de la Pierre Levée, 75011 Paris - 0143381980 When it comes to performance, weight is everything - Tiff Needell - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5.0.28 windows service path configuration
Have you read this: http://tomcat.apache.org/tomcat-5.5-doc/windows-service-howto.html ??? I dont remember version 4 and what path would do. You can certainly pass along env variables with --JvmOptions Dpath=... hth, Tim -Original Message- From: ludovic larche [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 25, 2006 5:36 AM To: users@tomcat.apache.org Subject: Tomcat 5.0.28 windows service path configuration Hello, I need your help to solve a problem, i would like to migrate my app from Tomcat 4.1.31 to 5.0.28 and use it as Windows Service. I would like to pass a directory Path during Tomcat 5.0.28 windows service installation. I can do it easily with Tomcat 4.1.31 when i use this command in a batch file : tomcat.exe -install Skyview Server ... -path c:\firstdirectory;c:\seconddirectory But I can't do it with Tomcat 5.0.28 when i use this command : service.bat install Skyview ... --path c:\firstdirectory;c:\seconddirectory I tried lots of workarounds to pass a path to Tomcat 5.0.28 during windows service installation, is there a way to configure Tomcat in this mode ? I would like to avoid update windows environment path in environment variable and i would prefer to use a Tomcat service for it. Thanks very much for your help -- Ludovic Larché Software Engineer Development Software Team [EMAIL PROTECTED] 12, rue des Landelles - Immeuble Hercule 2 - 35510 Cesson Sévigné - France Tel. : + 33 (0) 2 99 86 98 07 - Fax : + 33 (0) 2 99 86 98 01 The present email and all information included therein do not constitute a legal agreement accorded by JOUVE. All legal agreements must be formulated in writing on paper by a legal representative of JOUVE. If you have received this email by mistake, please inform us of that fact and destroy the email and any documents it might contain Thank you for your cooperation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5.0 : how to redirect a 401 error to a specific page
See section 10.4.2 of http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html You have to understand the page user see when he hit cancel has been send by tomcat before the user hit cancel. This is the page which is shown to user to indicate him he requires authentification. If you want to customize the layout of this page, use the error-page error-code location way, but do not, in you page send any redirect as it will break authentification mecanism (the browser won't get it's 401 header and thus won't show the http auth dialog to user). Francis Galiegue a écrit : Hello, Our webapp runs with Tomcat 5, Apache 2.0.46 from RHEL3, Tomcat 5.0.27 from JPackage, and communicate via mod_jk 1.2.6. Here's the problem we face: our webapp sends notifications by email, with a link to a JSP requiring a classical HTTP authentication dialog. This same page is used for the login form into the application, and its behaviour is controlled by the parameters passed to it. When the user DOES NOT submit any information (ie, it presses Cancel on the dialog box), Tomcat shows its 401 page. I've tried the following: * add an ErrorDocument directive to Apache config: no go; * add an error-page tag with error-code and location into the web-app section of WEB-INF/web.xml with the location pointing back to the same page, with no parameters: no go either... It's even worse in this case, since the Tomcat 401 page shows directly, the HTTP auth dialog doesn't even appear. I haven't tried _both_ at the same time, but I believe it wouldn't be the solution. As I'm not really fluent with Apache/Tomcat and webapps, I don't know where I should look at to solve the problem. Any hints would be more than welcome! Thanks for reading, and it'd be nice to reply-all, since the two CC are not on the list, -- Francis Galiegue, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] One2team - 12bis rue de la Pierre Levée, 75011 Paris - 0143381980 When it comes to performance, weight is everything - Tiff Needell - 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: Problem with the xsl:import
Marc, Thanks for the reply. We can put in an import of the form xsl:import href=http://localhost/aaem/xsl/routesummarycontent.xsl; / and that works fine (for a single web server). But we have multiple web servers on the box (using different ports and different install paths) and they may be different versions (development, UAT, production) having different versions of routesummarycontent.xsl. If we use the import above all servers end up selecting the XSL for just one of the versions. We don't want to have a different import for each version either as that will need modifying as we migrate updated versions between servers. What we need is a relative import, for example, xsl:import href=/xsl/routesummarycontent.xsl / !-- doesn't work -- But I'm thinking this is impossible. Thanks Geoff -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 21 April 2006 14:41 To: Tomcat Users List Subject: Re: Problem with the xsl:import You need to put the XML import file (in your case routesummarycontent.xsl) somewhere that whomever is providing the resource (Apache or Tomcat) can see it. Let me try to elaborate. We use an AJP connector with Tomcat and receives requests from Apache on port 8009. We forward all Servlet stuff to the Tomcat, but we let Apache handle everything else. Even images, js files, etc that are contained within a web application (context). In order to accomplish this, we have an alias set up for each web application in Apache. Thus, when we go to http://localhost/mywebapp/js/myjsfile.js we know that Apache is pulling up that page. However, if we have a js file in a JSP page that is referenced such as script src=/mywebapp/js/myjsfile.js language=Javascript/script we know that Tomcat is processing the JSP page, but Apache is processing the handling of sending the JS file to the client. As this is another http request inside the page that was request. So, the short of it is that you need to place your XSL somewhere that can be accessed via HTTP. So you need to either move the XSL file to a place where an alias is defined for Apache (even root) or create an alias for your Tomcat context and then point your html tag to: xsl:import href=http://localhost/aaem/xsl/routesummarycontent.xsl; / HTH On 4/21/06, BLAND, Geoff, GBM [EMAIL PROTECTED] wrote: Using Apache Tomcat 5.0.28 I'm having a problem with the xsl:import command. I have several Tomcat running on the same server (they could be different releases of code so can't share resources). An XSLT script is called via a JSP to convert XML to HTML (xsl:apply nameXml=routesummary xsl=/xsl/routesummaryheader.xsl /). This routesummaryheader.xsl script then needs to call another XSLT script routesummarycontent.xsl and it does this via an import, for example, xsl:import href=http://localhost:8080/aaem/xsl/routesummarycontent.xsl; / Now this works fine. But I run many Tomcat servers on this box and so a specific URI is no good. So I want to replace that import with a relative URI xsl:import href=routesummarycontent.xsl / This does not work, I get Had IO Exception with stylesheet file: routesummarycontent.xsl. Note routesummaryheader.xsl and routesummarycontent.xsl are in the same directory. I've tried all kinds of relative paths in the import nothing seems to work. The JSP file is under webapps\app-dir\jsp. The XSLT files are under webapps\app-dir\xsl. How do I fix this? ** * The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorized and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate. Visit our websites at: http://www.rbos.com http://www.rbsmarkets.com ** * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Marc Farrow
Re: A docbase ... inside the host appBase has been specified
I would start by reading the tomcat docs: http://tomcat.apache.org/tomcat-5.5-doc/logging.html -- David [EMAIL PROTECTED] wrote: Thanks so much for your helpful response. I mistakenly thought that was the problem with my servlet. Now I see that it is actually running (I was trying to hit http://localhost:8080/CommandServlet rather than http://localhost:8080/subset/CommandServlet -- sorry, rookie here). I was hoping to see more logging info, but I also get the warnings: log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. What's the appropriate procedure for getting this working? On Apr 24, 2006, at 7:33 PM, David Smith wrote: Nothing to do with your web.xml file. Are you having trouble getting your servlet to run when you call it? -- David Smith Network Operations Supervisor Department of Entomology Cornell University 2132 Comstock Hall Ithaca, NY 14853 Phone: (607) 255-9571 Fax: (607) 255-0940 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with the xsl:import
It is not impossible. Try xsl:import href=/aaem/xsl/routesummarycontent.xsl / You just have to make sure that the XSL content is either 1) Processed by Tomcat (by your connector properties) a) in the MOD_JK* worlds, this is making sure the URL pattern matching is set to forward the appropriate requests to Tomcat. In other connectors, you will have to do basically the same thing by whatever means is needed with that connector. 2) Apache can see the aaem webapp via an alias. We use the second method. You let Apache handle all requests that do not require a servlet container and forward everything else (JSPs and servlets) to Tomcat. This works even if we have static content within our Tomcat webapp. hth On 4/25/06, BLAND, Geoff, GBM [EMAIL PROTECTED] wrote: Marc, Thanks for the reply. We can put in an import of the form xsl:import href=http://localhost/aaem/xsl/routesummarycontent.xsl; / and that works fine (for a single web server). But we have multiple web servers on the box (using different ports and different install paths) and they may be different versions (development, UAT, production) having different versions of routesummarycontent.xsl. If we use the import above all servers end up selecting the XSL for just one of the versions. We don't want to have a different import for each version either as that will need modifying as we migrate updated versions between servers. What we need is a relative import, for example, xsl:import href=/xsl/routesummarycontent.xsl / !-- doesn't work -- But I'm thinking this is impossible. Thanks Geoff -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 21 April 2006 14:41 To: Tomcat Users List Subject: Re: Problem with the xsl:import You need to put the XML import file (in your case routesummarycontent.xsl) somewhere that whomever is providing the resource (Apache or Tomcat) can see it. Let me try to elaborate. We use an AJP connector with Tomcat and receives requests from Apache on port 8009. We forward all Servlet stuff to the Tomcat, but we let Apache handle everything else. Even images, js files, etc that are contained within a web application (context). In order to accomplish this, we have an alias set up for each web application in Apache. Thus, when we go to http://localhost/mywebapp/js/myjsfile.js we know that Apache is pulling up that page. However, if we have a js file in a JSP page that is referenced such as script src=/mywebapp/js/myjsfile.js language=Javascript/script we know that Tomcat is processing the JSP page, but Apache is processing the handling of sending the JS file to the client. As this is another http request inside the page that was request. So, the short of it is that you need to place your XSL somewhere that can be accessed via HTTP. So you need to either move the XSL file to a place where an alias is defined for Apache (even root) or create an alias for your Tomcat context and then point your html tag to: xsl:import href=http://localhost/aaem/xsl/routesummarycontent.xsl; / HTH On 4/21/06, BLAND, Geoff, GBM [EMAIL PROTECTED] wrote: Using Apache Tomcat 5.0.28 I'm having a problem with the xsl:import command. I have several Tomcat running on the same server (they could be different releases of code so can't share resources). An XSLT script is called via a JSP to convert XML to HTML (xsl:apply nameXml=routesummary xsl=/xsl/routesummaryheader.xsl /). This routesummaryheader.xsl script then needs to call another XSLT script routesummarycontent.xsl and it does this via an import, for example, xsl:import href=http://localhost:8080/aaem/xsl/routesummarycontent.xsl; / Now this works fine. But I run many Tomcat servers on this box and so a specific URI is no good. So I want to replace that import with a relative URI xsl:import href=routesummarycontent.xsl / This does not work, I get Had IO Exception with stylesheet file: routesummarycontent.xsl. Note routesummaryheader.xsl and routesummarycontent.xsl are in the same directory. I've tried all kinds of relative paths in the import nothing seems to work. The JSP file is under webapps\app-dir\jsp. The XSLT files are under webapps\app-dir\xsl. How do I fix this? ** * The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorized and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept
RE: Problem with the xsl:import
Marc, Again thanks for the reply, we've kind of done what you say should work - it appears not to work. We have put in xsl:import href=/aaem/xsl/routesummarycontent.xsl / And also (I think this is more correct as we're already at the aaem level) xsl:import href=/xsl/routesummarycontent.xsl / Neither work. I'm pretty sure that alias is set correctly as if I put http://myserver:thisport/aaem/xsl/routesummarycontent.xsl into a web browser the XSLT script is found. I'm not sure quite what you mean by make sure XSL content is Processed by Tomcat. I assume this is happening as if we put in the full address the XSLT is processed with no problem. Thanks Geoff Bland -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 25 April 2006 12:29 To: Tomcat Users List Subject: Re: Problem with the xsl:import It is not impossible. Try xsl:import href=/aaem/xsl/routesummarycontent.xsl / You just have to make sure that the XSL content is either 1) Processed by Tomcat (by your connector properties) a) in the MOD_JK* worlds, this is making sure the URL pattern matching is set to forward the appropriate requests to Tomcat. In other connectors, you will have to do basically the same thing by whatever means is needed with that connector. 2) Apache can see the aaem webapp via an alias. We use the second method. You let Apache handle all requests that do not require a servlet container and forward everything else (JSPs and servlets) to Tomcat. This works even if we have static content within our Tomcat webapp. hth On 4/25/06, BLAND, Geoff, GBM [EMAIL PROTECTED] wrote: Marc, Thanks for the reply. We can put in an import of the form xsl:import href=http://localhost/aaem/xsl/routesummarycontent.xsl; / and that works fine (for a single web server). But we have multiple web servers on the box (using different ports and different install paths) and they may be different versions (development, UAT, production) having different versions of routesummarycontent.xsl. If we use the import above all servers end up selecting the XSL for just one of the versions. We don't want to have a different import for each version either as that will need modifying as we migrate updated versions between servers. What we need is a relative import, for example, xsl:import href=/xsl/routesummarycontent.xsl / !-- doesn't work -- But I'm thinking this is impossible. Thanks Geoff -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 21 April 2006 14:41 To: Tomcat Users List Subject: Re: Problem with the xsl:import You need to put the XML import file (in your case routesummarycontent.xsl) somewhere that whomever is providing the resource (Apache or Tomcat) can see it. Let me try to elaborate. We use an AJP connector with Tomcat and receives requests from Apache on port 8009. We forward all Servlet stuff to the Tomcat, but we let Apache handle everything else. Even images, js files, etc that are contained within a web application (context). In order to accomplish this, we have an alias set up for each web application in Apache. Thus, when we go to http://localhost/mywebapp/js/myjsfile.js we know that Apache is pulling up that page. However, if we have a js file in a JSP page that is referenced such as script src=/mywebapp/js/myjsfile.js language=Javascript/script we know that Tomcat is processing the JSP page, but Apache is processing the handling of sending the JS file to the client. As this is another http request inside the page that was request. So, the short of it is that you need to place your XSL somewhere that can be accessed via HTTP. So you need to either move the XSL file to a place where an alias is defined for Apache (even root) or create an alias for your Tomcat context and then point your html tag to: xsl:import href=http://localhost/aaem/xsl/routesummarycontent.xsl; / HTH On 4/21/06, BLAND, Geoff, GBM [EMAIL PROTECTED] wrote: Using Apache Tomcat 5.0.28 I'm having a problem with the xsl:import command. I have several Tomcat running on the same server (they could be different releases of code so can't share resources). An XSLT script is called via a JSP to convert XML to HTML (xsl:apply nameXml=routesummary xsl=/xsl/routesummaryheader.xsl /). This routesummaryheader.xsl script then needs to call another XSLT script routesummarycontent.xsl and it does this via an import, for example, xsl:import href=http://localhost:8080/aaem/xsl/routesummarycontent.xsl; / Now this works fine. But I run many Tomcat servers on this box and so a specific URI is no good. So I want to replace that import with a relative URI xsl:import href=routesummarycontent.xsl / This does not work, I get Had IO Exception with stylesheet file: routesummarycontent.xsl. Note routesummaryheader.xsl and routesummarycontent.xsl
Re: Problem with the xsl:import
This has to do with how HTTP requests are processed on your server. You control (by url pattern matching or some other technique) which service (Tomcat or Apache) gets to handle the request. Help me out a bit here. What language the tag XSL belong to? Is it a JSP tag or an HTML tag or what? On 4/25/06, BLAND, Geoff, GBM [EMAIL PROTECTED] wrote: Marc, Again thanks for the reply, we've kind of done what you say should work - it appears not to work. We have put in xsl:import href=/aaem/xsl/routesummarycontent.xsl / And also (I think this is more correct as we're already at the aaem level) xsl:import href=/xsl/routesummarycontent.xsl / Neither work. I'm pretty sure that alias is set correctly as if I put http://myserver:thisport/aaem/xsl/routesummarycontent.xsl into a web browser the XSLT script is found. I'm not sure quite what you mean by make sure XSL content is Processed by Tomcat. I assume this is happening as if we put in the full address the XSLT is processed with no problem. Thanks Geoff Bland -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 25 April 2006 12:29 To: Tomcat Users List Subject: Re: Problem with the xsl:import It is not impossible. Try xsl:import href=/aaem/xsl/routesummarycontent.xsl / You just have to make sure that the XSL content is either 1) Processed by Tomcat (by your connector properties) a) in the MOD_JK* worlds, this is making sure the URL pattern matching is set to forward the appropriate requests to Tomcat. In other connectors, you will have to do basically the same thing by whatever means is needed with that connector. 2) Apache can see the aaem webapp via an alias. We use the second method. You let Apache handle all requests that do not require a servlet container and forward everything else (JSPs and servlets) to Tomcat. This works even if we have static content within our Tomcat webapp. hth On 4/25/06, BLAND, Geoff, GBM [EMAIL PROTECTED] wrote: Marc, Thanks for the reply. We can put in an import of the form xsl:import href=http://localhost/aaem/xsl/routesummarycontent.xsl; / and that works fine (for a single web server). But we have multiple web servers on the box (using different ports and different install paths) and they may be different versions (development, UAT, production) having different versions of routesummarycontent.xsl. If we use the import above all servers end up selecting the XSL for just one of the versions. We don't want to have a different import for each version either as that will need modifying as we migrate updated versions between servers. What we need is a relative import, for example, xsl:import href=/xsl/routesummarycontent.xsl / !-- doesn't work -- But I'm thinking this is impossible. Thanks Geoff -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 21 April 2006 14:41 To: Tomcat Users List Subject: Re: Problem with the xsl:import You need to put the XML import file (in your case routesummarycontent.xsl) somewhere that whomever is providing the resource (Apache or Tomcat) can see it. Let me try to elaborate. We use an AJP connector with Tomcat and receives requests from Apache on port 8009. We forward all Servlet stuff to the Tomcat, but we let Apache handle everything else. Even images, js files, etc that are contained within a web application (context). In order to accomplish this, we have an alias set up for each web application in Apache. Thus, when we go to http://localhost/mywebapp/js/myjsfile.js we know that Apache is pulling up that page. However, if we have a js file in a JSP page that is referenced such as script src=/mywebapp/js/myjsfile.js language=Javascript/script we know that Tomcat is processing the JSP page, but Apache is processing the handling of sending the JS file to the client. As this is another http request inside the page that was request. So, the short of it is that you need to place your XSL somewhere that can be accessed via HTTP. So you need to either move the XSL file to a place where an alias is defined for Apache (even root) or create an alias for your Tomcat context and then point your html tag to: xsl:import href=http://localhost/aaem/xsl/routesummarycontent.xsl; / HTH On 4/21/06, BLAND, Geoff, GBM [EMAIL PROTECTED] wrote: Using Apache Tomcat 5.0.28 I'm having a problem with the xsl:import command. I have several Tomcat running on the same server (they could be different releases of code so can't share resources). An XSLT script is called via a JSP to convert XML to HTML (xsl:apply nameXml=routesummary xsl=/xsl/routesummaryheader.xsl /). This routesummaryheader.xsl script then needs to call another XSLT script routesummarycontent.xsl and it does this via an import, for
Re: Problem with the xsl:import
Here's the problem. xsl:import is purely an XSL thing. So it doesn't necessarily do anything similar to how the servlet spec does things. So when you have xsl:import href=cowbell.xsl / - cowbell is retreived in a relative style with respect to its context. (which could be file, or http). Your webapp lives in a context. But xsl knows nothing about context, or context as defined by the servlet spec. So asking for http://localhost/aaem/xsl/routesummarycontent.xsl is the same as a webbrowser asking for it. On a multi-hosted machine - yup - this will bring you interesting results. So what you probably need is your own javax.xml.transform.URIResolver. You probably need to write your own implementation of it and have tomcat use it. (A topic for which I have done neither) -Tim BLAND, Geoff, GBM wrote: Marc, Thanks for the reply. We can put in an import of the form xsl:import href=http://localhost/aaem/xsl/routesummarycontent.xsl; / and that works fine (for a single web server). But we have multiple web servers on the box (using different ports and different install paths) and they may be different versions (development, UAT, production) having different versions of routesummarycontent.xsl. If we use the import above all servers end up selecting the XSL for just one of the versions. We don't want to have a different import for each version either as that will need modifying as we migrate updated versions between servers. What we need is a relative import, for example, xsl:import href=/xsl/routesummarycontent.xsl / !-- doesn't work -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem with the xsl:import
Marc, The xsl:import href=... / statement to include routesummarycontent.xsl is in another XSLT script (routesummaryheader.xsl) which is loaded correctly from a JSP (routesummary.jsp) using the command xsl:apply nameXml=routesummary xsl=/xsl/routesummaryheader.xsl /. To recap; routesummary.jsp calls routesummaryheader.xsl which imports routesummarycontent.xsl. This has to do with how HTTP requests are processed on your server. We _think_ that the XSLT processor used by Tomcat can't use relative paths as it doesn't know what context it resides in (even if Tomcat does). Thanks Geoff -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 25 April 2006 13:03 To: Tomcat Users List Subject: Re: Problem with the xsl:import This has to do with how HTTP requests are processed on your server. You control (by url pattern matching or some other technique) which service (Tomcat or Apache) gets to handle the request. Help me out a bit here. What language the tag XSL belong to? Is it a JSP tag or an HTML tag or what? On 4/25/06, BLAND, Geoff, GBM [EMAIL PROTECTED] wrote: Marc, Again thanks for the reply, we've kind of done what you say should work - it appears not to work. We have put in xsl:import href=/aaem/xsl/routesummarycontent.xsl / And also (I think this is more correct as we're already at the aaem level) xsl:import href=/xsl/routesummarycontent.xsl / Neither work. I'm pretty sure that alias is set correctly as if I put http://myserver:thisport/aaem/xsl/routesummarycontent.xsl into a web browser the XSLT script is found. I'm not sure quite what you mean by make sure XSL content is Processed by Tomcat. I assume this is happening as if we put in the full address the XSLT is processed with no problem. Thanks Geoff Bland -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 25 April 2006 12:29 To: Tomcat Users List Subject: Re: Problem with the xsl:import It is not impossible. Try xsl:import href=/aaem/xsl/routesummarycontent.xsl / You just have to make sure that the XSL content is either 1) Processed by Tomcat (by your connector properties) a) in the MOD_JK* worlds, this is making sure the URL pattern matching is set to forward the appropriate requests to Tomcat. In other connectors, you will have to do basically the same thing by whatever means is needed with that connector. 2) Apache can see the aaem webapp via an alias. We use the second method. You let Apache handle all requests that do not require a servlet container and forward everything else (JSPs and servlets) to Tomcat. This works even if we have static content within our Tomcat webapp. hth On 4/25/06, BLAND, Geoff, GBM [EMAIL PROTECTED] wrote: Marc, Thanks for the reply. We can put in an import of the form xsl:import href=http://localhost/aaem/xsl/routesummarycontent.xsl; / and that works fine (for a single web server). But we have multiple web servers on the box (using different ports and different install paths) and they may be different versions (development, UAT, production) having different versions of routesummarycontent.xsl. If we use the import above all servers end up selecting the XSL for just one of the versions. We don't want to have a different import for each version either as that will need modifying as we migrate updated versions between servers. What we need is a relative import, for example, xsl:import href=/xsl/routesummarycontent.xsl / !-- doesn't work -- But I'm thinking this is impossible. Thanks Geoff -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 21 April 2006 14:41 To: Tomcat Users List Subject: Re: Problem with the xsl:import You need to put the XML import file (in your case routesummarycontent.xsl) somewhere that whomever is providing the resource (Apache or Tomcat) can see it. Let me try to elaborate. We use an AJP connector with Tomcat and receives requests from Apache on port 8009. We forward all Servlet stuff to the Tomcat, but we let Apache handle everything else. Even images, js files, etc that are contained within a web application (context). In order to accomplish this, we have an alias set up for each web application in Apache. Thus, when we go to http://localhost/mywebapp/js/myjsfile.js we know that Apache is pulling up that page. However, if we have a js file in a JSP page that is referenced such as script src=/mywebapp/js/myjsfile.js language=Javascript/script we know that Tomcat is processing the JSP page, but Apache is processing the handling of sending the JS file to the client. As this is another http request inside the page that was request. So, the short of it is that you need to place your XSL somewhere that can be accessed via HTTP. So you need to either move the XSL
RE: Problem with the xsl:import
Tim, I think you're right. That's pretty much what we had thought. Also we had thought of writing our own resolver, we've done this to solve other (non-web) issues, but we were hoping tat there might be a better way of doing this. Thanks for your help. Geoff -Original Message- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: 25 April 2006 13:17 To: Tomcat Users List Subject: Re: Problem with the xsl:import Here's the problem. xsl:import is purely an XSL thing. So it doesn't necessarily do anything similar to how the servlet spec does things. So when you have xsl:import href=cowbell.xsl / - cowbell is retreived in a relative style with respect to its context. (which could be file, or http). Your webapp lives in a context. But xsl knows nothing about context, or context as defined by the servlet spec. So asking for http://localhost/aaem/xsl/routesummarycontent.xsl is the same as a webbrowser asking for it. On a multi-hosted machine - yup - this will bring you interesting results. So what you probably need is your own javax.xml.transform.URIResolver. You probably need to write your own implementation of it and have tomcat use it. (A topic for which I have done neither) -Tim *** The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorized and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate. Visit our websites at: http://www.rbos.com http://www.rbsmarkets.com *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with the xsl:import
Geoff, As Tim stated. The XSL:import... tag is an HTTP request. Even though it is coming in through the JSP page it is still and HTTP request and not a relative file path issue in regards to the context. I think we at least have you on the right path. On 4/25/06, BLAND, Geoff, GBM [EMAIL PROTECTED] wrote: Marc, The xsl:import href=... / statement to include routesummarycontent.xsl is in another XSLT script (routesummaryheader.xsl) which is loaded correctly from a JSP (routesummary.jsp) using the command xsl:apply nameXml=routesummary xsl=/xsl/routesummaryheader.xsl /. To recap; routesummary.jsp calls routesummaryheader.xsl which imports routesummarycontent.xsl. This has to do with how HTTP requests are processed on your server. We _think_ that the XSLT processor used by Tomcat can't use relative paths as it doesn't know what context it resides in (even if Tomcat does). Thanks Geoff -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 25 April 2006 13:03 To: Tomcat Users List Subject: Re: Problem with the xsl:import This has to do with how HTTP requests are processed on your server. You control (by url pattern matching or some other technique) which service (Tomcat or Apache) gets to handle the request. Help me out a bit here. What language the tag XSL belong to? Is it a JSP tag or an HTML tag or what? On 4/25/06, BLAND, Geoff, GBM [EMAIL PROTECTED] wrote: Marc, Again thanks for the reply, we've kind of done what you say should work - it appears not to work. We have put in xsl:import href=/aaem/xsl/routesummarycontent.xsl / And also (I think this is more correct as we're already at the aaem level) xsl:import href=/xsl/routesummarycontent.xsl / Neither work. I'm pretty sure that alias is set correctly as if I put http://myserver:thisport/aaem/xsl/routesummarycontent.xsl into a web browser the XSLT script is found. I'm not sure quite what you mean by make sure XSL content is Processed by Tomcat. I assume this is happening as if we put in the full address the XSLT is processed with no problem. Thanks Geoff Bland -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 25 April 2006 12:29 To: Tomcat Users List Subject: Re: Problem with the xsl:import It is not impossible. Try xsl:import href=/aaem/xsl/routesummarycontent.xsl / You just have to make sure that the XSL content is either 1) Processed by Tomcat (by your connector properties) a) in the MOD_JK* worlds, this is making sure the URL pattern matching is set to forward the appropriate requests to Tomcat. In other connectors, you will have to do basically the same thing by whatever means is needed with that connector. 2) Apache can see the aaem webapp via an alias. We use the second method. You let Apache handle all requests that do not require a servlet container and forward everything else (JSPs and servlets) to Tomcat. This works even if we have static content within our Tomcat webapp. hth On 4/25/06, BLAND, Geoff, GBM [EMAIL PROTECTED] wrote: Marc, Thanks for the reply. We can put in an import of the form xsl:import href=http://localhost/aaem/xsl/routesummarycontent.xsl; / and that works fine (for a single web server). But we have multiple web servers on the box (using different ports and different install paths) and they may be different versions (development, UAT, production) having different versions of routesummarycontent.xsl. If we use the import above all servers end up selecting the XSL for just one of the versions. We don't want to have a different import for each version either as that will need modifying as we migrate updated versions between servers. What we need is a relative import, for example, xsl:import href=/xsl/routesummarycontent.xsl / !-- doesn't work -- But I'm thinking this is impossible. Thanks Geoff -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 21 April 2006 14:41 To: Tomcat Users List Subject: Re: Problem with the xsl:import You need to put the XML import file (in your case routesummarycontent.xsl) somewhere that whomever is providing the resource (Apache or Tomcat) can see it. Let me try to elaborate. We use an AJP connector with Tomcat and receives requests from Apache on port 8009. We forward all Servlet stuff to the Tomcat, but we let Apache handle everything else. Even images, js files, etc that are contained within a web application (context). In order to accomplish this, we have an alias set up for each web application in Apache. Thus, when we go to http://localhost/mywebapp/js/myjsfile.js we know that Apache is pulling up that page. However, if we have a js file in a JSP page that is
Re: jsvc creates LOTS of processes
Good Morning Mark
This was raised by Wade Chandler with previous versions of jsvc using
commons-daemon-1.0
JDK 1.5
RH 7.3 with Kernel 2.4.2
http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/200501.mbox/[EMAIL
PROTECTED]
Did you verify you are actually binding?
(perhaps thru turning on debug option in jsvc.exe and doing a netstat -a before
AND after)
Just for my own understanding What do gain by running thru jsvc.exe vs ?
Thanks,
Martin --
*
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: Mark Shifman [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Monday, April 24, 2006 12:55 PM
Subject: jsvc creates LOTS of processes
I noticed that jsvc creates about 68 processes on one of my servers.
I start it using an init.d script under redhat 9.
I don't think I have done anything egregious.
...snip
CATALINA_OPTS= -Djava.awt.headless=true -Xmx750m -Xms750m
...snip
start(){
$DAEMON_HOME/jsvc \
-user $TOMCAT_USER \
-home $JAVA_HOME \
-Dcatalina.home=$CATALINA_HOME \
-Djava.io.tmpdir=$CATALINA_HOME/temp \
-outfile $CATALINA_HOME/logs/catalina.out \
-errfile '1' \
$CATALINA_OPTS \
-cp $CLASSPATH \
org.apache.catalina.startup.Bootstrap
echo starting tomcat: $CATALINA_HOME
echo tomcat user: $TOMCAT_USER
#
# To get a verbose JVM
#-verbose \
# To get a debug of jsvc.
#-debug \
}
I was getting a 143 error on exiting Tomcat with an old version of jsvc.
I got the version packaged with 5.5.16 and compiled it just in case this
was fixed.
My 143 error is gone, but there still are lots of processes generated
when I start Tomcat as a daemon.
I have another server where only 1 jsvc.exe process is started when I
start Tomcat.
What am I doing wrong on the server with 68 processes.
mas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Your opinion - a graphical configuration console for Tomcat
Hexamind Companion is a tool for developers and system administrators who manage the configuration of Tomcat servers. We are nearing the final stages of its development, and would like to hear your opinion about this tool. Please follow the link below to learn more and participate in our online survey. http://www.hexamind.com/website/surveys/tomcat?orig=a1 We thank you for your help, Itai Shirav Hexamind Ltd. http://www.hexamind.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
modul to crush tomcat admin
Hi I would like to crush the tomcat admin with the admin modul have created. Is that possible ? What is the way ? Thibaut - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with tomcat hanging
I read the relase notes for tomcat and tried setting ulimit -s 2048 in the start script (I restarted the app). I just noticed that when tomcat hangs and I can still pull up the default tomcat page if I go the the tomcat server and load the url http://servername:8088. I am wondering if my problem is not tomcat ? If I can pull up the default page does that indicate the problem is elsewhere ? james
Re: Problems with tomcat hanging
It kind of sounds like your connection to the database is timing out.
Does this happen after the tomcat instance in question has been idle for
an extended time?
james edwards wrote:
We are running separate tomcat and apache servers, the http requests are
being proxied from the apache server to the tomcat server.
Tomcat connects to an informix database; our application is a webpage that
allows users to make queries against the dB and report the results
in html.
Here is the box we are running the tomcat on:
[EMAIL PROTECTED] javaapps]# uname -a
Linux serv3.nmcourts.com 2.6.9-22.ELsmp #1 SMP Sat Oct 8 19:11:43 CDT 2005
i686 i686 i386 GNU/Linux
[EMAIL PROTECTED] javaapps]# cat /etc/redhat-release
CentOS release 4.3 (Final)
[EMAIL PROTECTED] javaapps]#
We are using the following vers. of tomcat apache:
[EMAIL PROTECTED] javaapps]# ls
apache-ant-1.6.5 apache-tomcat-5.5.16
jakarta-tomcat-connectors-1.2.15-src jdk1.5.0_06
apache-ant-1.6.5-bin.tar apache-tomcat-5.5.16.tar.gz
jakarta-tomcat-connectors-1.2.15-src.tar.gz jdk-1_5_0_06-linux-i586.bin
At least once a day the tomcat process hangs. Loading the default page
brings an error saying tomcat cannot connect to the dB.
Running queries on the tomcat server itself we get the same error. We run
another tomcat app (on a separate box) that queries the same dB
and it works fine at the same time as this problem on the other tomcat box.
Only restarting tomcat fixes this problem, a restart of the informix server
does not fix it. Looking at logs, I do not see anything logged to indicate
that the process is hung. Can someone suggest what I can do to get better
information on what is happening and why ?
We are some logs, we had the restart this morning at 8:06:13 AM and as you
can see there was nothing in the logs (catalina.out)
prior to that other that a restart not quite 24 hrs prior.
Apr 23, 2006 10:38:50 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Apr 23, 2006 10:38:50 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Apr 23, 2006 10:38:50 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Apr 23, 2006 10:38:50 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Apr 23, 2006 10:38:50 AM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Apr 23, 2006 10:38:51 AM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Apr 23, 2006 10:38:51 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/24 config=null
Apr 23, 2006 10:38:51 AM org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
Apr 23, 2006 10:38:51 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 4596 ms
Apr 24, 2006 8:06:13 AM org.apache.coyote.http11.Http11BaseProtocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
Apr 24, 2006 8:06:14 AM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Apr 24, 2006 8:06:14 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextDestroyed()
Apr 24, 2006 8:06:14 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextDestroyed()
Apr 24, 2006 8:06:14 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextDestroyed()
Apr 24, 2006 8:06:14 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextDestroyed()
- Closing Spring root WebApplicationContext
- Closing application context [
org.springframework.web.context.support.XmlWebApplicationContext
;hashCode=32278793]
- Destroying singletons in factory {
org.springframework.beans.factory.support.DefaultListableBeanFactorydefining
beans
[dataSource,jdbcTemplate,searchService,partySearchService,searchServiceDaoBase,searchServiceDaoImpl,caselookupDataAccess,searchServiceUtils,searchController,caselookupSearchController,searchDetailController,dwiSearchController,dwiSearchService,searchDetailService,partySearchResults,dwiSearchResults,searchDetailWrapperBean,caseDetail,criminalChargeDetail,judgeAssignmentHistory,roaActivity,caseParties,civilComplaint,searchValidator,urlMapping,viewResolver];
root of BeanFactory hierarchy}
- Closing WebApplicationContext of Spring FrameworkServlet 'caselookup'
- Closing application context [WebApplicationContext for namespace
'caselookup-servlet']
- Destroying singletons in factory {
org.springframework.beans.factory.support.DefaultListableBeanFactorydefining
beans
Re: Problems with tomcat hanging
On 4/25/06, David Kerber [EMAIL PROTECTED] wrote: It kind of sounds like your connection to the database is timing out. Does this happen after the tomcat instance in question has been idle for an extended time? Yes, overnight. Perhaps when the dB is brought down to do a backup. We will test tonight prior to the backup and see if it works then does not work after the backup. Thanks ! James H. Edwards Network Systems Administrator Judicial Information Division [EMAIL PROTECTED] (505)476-6960
RE: Properties file problem
Hardwiring a directory inside a war's web.xml will likely get you into
portability problems. If you must do this, at least make it a JNDI lookup
so that the JNDI provider (Tomcat, other app server) can manage this
resource -- that is, the person deploying the app has some flexibility in
where to put the file(s).
Tim
-Original Message-
From: VIKASS NAGPAL [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 25, 2006 12:07 PM
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: Re: Properties file problem
Hi All,
I think the problem can be resolved by creating the temporary directory,
anyother directory which location can be hard-wired as initial parameter in
the web.xml file. But where in my application's web.xml I have to
hard-wire this directory. Can you please let me exactly where should I
hard-wire this directory so that my application can dynamically create the
properties file inside this directory.
Thanks,
Vikas Nagpal.
--- Hadraba Petr [EMAIL PROTECTED] wrote:
Hi Vikas,
some details:
I see you're correctly using the
getClass.getResource() (I'm using
getServletContext().getResourceAsStream() or
getServletContext().getResource()). But, Why are you creating
resources? You see all the war content in the host OS filesystem
because of unpackWars=true. This is because of performance (I hope)
and if you set this to false, Tomcat will *read* resources (also
classes and anything else) from the WAR file directly! You are mixing
two things together: one are resources (they are using URL instead of
File) and on the other side Host OS FileSystem (the File objects).
So, you store database connection parameters in the property file. I
see two options to solve your problem:
1. Move the property file outside the resources if you want dynamic
creation. For example: temporary directory, any other directory which
location can be hard-wired as initial parameter in the web.xml file.
2. Use Tomcat's database pooler. You give more performence (if you're
not using your own database connection pooler)!
Please explain what you want to do, what's your goal...
Have a nice day
PETR
On 4/21/06, VIKASS NAGPAL [EMAIL PROTECTED] wrote:
Hi All,
I have a problem here. I have Pproperties file.
It has the following code:
File f = new File(propertyFolder);
if (!f.exists()) f.mkdir();
f = new File(propertyFolder +
System.getProperty(file.separator) + propertyFileName);
if (!f.exists())
{
String s = ((this.getClass().getResource(/ +
propertyFileName)).toString());
File pf = new File(s.substring(6));
This code creates a folder with the name propertiespaydir and file
with the name pdr.properties. In order to connect to the
database i
have to read the Servername, Database name,
Username
and password from this file or creates a file with
the
name pdr.properties file. But If i rename this pdr.properties file
to something else then my code does not create the file with the
name
pdr.properties.
So I cannot connect to the database. So anyone of
you
knows what change should i make into my existing
code
in order for me to create the file with the name pdr.properties in
case it does not exist. I would really be thankful for any help in
this matter.
Thanks,
With regards,
Vikas Nagpal.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam
protection around
http://mail.yahoo.com
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
--
Petr Hadraba
graphic artist and software designer
http://people.hadraba-soft.com/~petr
hadrabap AT bluetone DOT cz
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
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]
Custom 404 page with listings set to false
I set the following in web.xml: init-param param-namedebug/param-name param-value0/param-value /init-param init-param param-namelistings/param-name param-valuefalse/param-value /init-param load-on-startup1/load-on-startup And I also have this: error-page error-code404/error-code location/404.html/location /error-page But when someone tried to list a diretory, e.g., www.ourdomain.com/images, all of the images in the 404 page and links end up broken and we see this in the log file: 2006-04-25 12:57:47 [EMAIL PROTECTED]: Exception Processing ErrorPage[errorCode=404, location=/404.html] ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:331) at org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:297) at org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.java:537 ) at org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(CoyoteResponseFac ade.java:238) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:303 ) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:147 ) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex t.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118 ) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex t.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex t.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex t.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) 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) Is there another directive that needs setting? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: modul to crush tomcat admin
Thibaut wrote: Hi I would like to crush the tomcat admin with the admin modul have created. Is that possible ? What is the way ? I am not sure what you meant but I don't think crush is the right word. You'll need to try re-phrasing this before we can help you. Are you trying to install the admin module? Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: autocreate a Context Descriptor for webApps without META-INF/context.xml
I would like to know if there is an answer to this as well. Thanks, -Original Message- From: Bodo Piehl [mailto:[EMAIL PROTECTED] Sent: Sunday, April 23, 2006 1:14 PM To: users@tomcat.apache.org Subject: autocreate a Context Descriptor for webApps without META-INF/context.xml I read in the documentation in chapter A word on Contexts the text below. If I put a war-file (which doesn't contain a META-INF/context.xml) into the webapps-dir, the war-file is extracted and the webApp deployed, e.g. on startup. But afterwards the Context Descriptor isn't autogenerated and placed in $CATALINA_HOME/conf/[enginename]/[hostname]/ as expected. As a result my webApp is deployed every startup again. Do I need to set a flag to turn on that behavior in Tomcat? I use Tomcat 5.5.16. Can anybody reproduce my problem? thanks Bodo Context Descriptors not only help Tomcat to know how to configure Contexts but other tools such as the Tomcat Manager and TDC often use these Context Descriptors to perform their roles properly. The locations for Context Descriptors are; 1. $CATALINA_HOME/conf/[enginename]/[hostname]/context.xml 2. $CATALINA_HOME/webapps/[webappname]/META-INF/context.xml If a Context Descriptor is not provided for a Context, Tomcat automatically creates one and places it in (1) with a filename of [webappname].xml although if manually created, the filename need not match the web application name as Tomcat is concerned only with the Context configuration contained within the Context Descriptor file(s). ___ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 - 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]
IIS Integration
Hi everyone, We are looking for some suggestions on running Tomcat with IIS. We are running IIS 6 and Tomcat 5.0.28. We've been working with the isapi_redirect dll (JK2), however we run into a problem where the server drops connections frequently. In other words, a user comes to the site, and the server doesn't accept the connection. Does anyone have IIS6/Tomcat working, and if so, can you provide some pointers to how you got it working? Do you have it using any type of high load (say, 1k+ hits a second)? Does anyone have any other suggestions (we're certainly open to them). Thanks! Cory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: IIS Integration
JK or JK2? You say JK2, but mention isapi_redirect.dll (JK). JK2 is not supported any longer. In a previous life (feel free to chime in, Derrick!) we had JK running with IIS 6 on W2K3. It was not handling 1K request/second. JK2 + IIS + a custom ISAPI on IIS 6 was a memory corruption nightmare! I believe the problems were all in the custom ISAPI module, which has now been fixed. Tim -Original Message- From: Cory Foy [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 25, 2006 2:29 PM To: users@tomcat.apache.org Subject: IIS Integration Hi everyone, We are looking for some suggestions on running Tomcat with IIS. We are running IIS 6 and Tomcat 5.0.28. We've been working with the isapi_redirect dll (JK2), however we run into a problem where the server drops connections frequently. In other words, a user comes to the site, and the server doesn't accept the connection. Does anyone have IIS6/Tomcat working, and if so, can you provide some pointers to how you got it working? Do you have it using any type of high load (say, 1k+ hits a second)? Does anyone have any other suggestions (we're certainly open to them). Thanks! Cory - 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: jsvc creates LOTS of processes
Hi:
I think my problem is a problem with seeing threads.
The kernel I am using is 2.4.21-37.ELsmp
When I launch jsvc with debug things look reasonable and netstat -a also
looks ok.
I run tomcat as a daemon via jsvc in order to take advantage of the
system startup stuff for free.
It automatically starts on reboot, I can use /sbin/service tomcat to
start and stop at will.
So tomcat is run like the other services on my machine, ie sshd, httpd, etc.
Thanks for your help.
mas
Martin Gainty wrote:
Good Morning Mark
This was raised by Wade Chandler with previous versions of jsvc using
commons-daemon-1.0
JDK 1.5
RH 7.3 with Kernel 2.4.2
http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/200501.mbox/[EMAIL
PROTECTED]
Did you verify you are actually binding?
(perhaps thru turning on debug option in jsvc.exe and doing a netstat -a before
AND after)
Just for my own understanding What do gain by running thru jsvc.exe vs ?
Thanks,
Martin --
*
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: Mark Shifman [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Monday, April 24, 2006 12:55 PM
Subject: jsvc creates LOTS of processes
I noticed that jsvc creates about 68 processes on one of my servers.
I start it using an init.d script under redhat 9.
I don't think I have done anything egregious.
...snip
CATALINA_OPTS= -Djava.awt.headless=true -Xmx750m -Xms750m
...snip
start(){
$DAEMON_HOME/jsvc \
-user $TOMCAT_USER \
-home $JAVA_HOME \
-Dcatalina.home=$CATALINA_HOME \
-Djava.io.tmpdir=$CATALINA_HOME/temp \
-outfile $CATALINA_HOME/logs/catalina.out \
-errfile '1' \
$CATALINA_OPTS \
-cp $CLASSPATH \
org.apache.catalina.startup.Bootstrap
echo starting tomcat: $CATALINA_HOME
echo tomcat user: $TOMCAT_USER
#
# To get a verbose JVM
#-verbose \
# To get a debug of jsvc.
#-debug \
}
I was getting a 143 error on exiting Tomcat with an old version of jsvc.
I got the version packaged with 5.5.16 and compiled it just in case this
was fixed.
My 143 error is gone, but there still are lots of processes generated
when I start Tomcat as a daemon.
I have another server where only 1 jsvc.exe process is started when I
start Tomcat.
What am I doing wrong on the server with 68 processes.
mas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Mark Shifman MD. Ph.D.
Yale Center for Medical Informatics
Phone (203)737-5219
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
AW: autocreate a Context Descriptor for webApps without META-INF/context.xml
can you reproduce that problem? I'am thinking about reporting that problem in bugzilla. Therefore it would be nice if somebody else could confirm it. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von BATCHELOR, SCOTT (CONTRACTOR) Gesendet: Dienstag, 25. April 2006 20:12 An: Tomcat Users List Betreff: RE: autocreate a Context Descriptor for webApps without META-INF/context.xml I would like to know if there is an answer to this as well. Thanks, -Original Message- From: Bodo Piehl [mailto:[EMAIL PROTECTED] Sent: Sunday, April 23, 2006 1:14 PM To: users@tomcat.apache.org Subject: autocreate a Context Descriptor for webApps without META-INF/context.xml I read in the documentation in chapter A word on Contexts the text below. If I put a war-file (which doesn't contain a META-INF/context.xml) into the webapps-dir, the war-file is extracted and the webApp deployed, e.g. on startup. But afterwards the Context Descriptor isn't autogenerated and placed in $CATALINA_HOME/conf/[enginename]/[hostname]/ as expected. As a result my webApp is deployed every startup again. Do I need to set a flag to turn on that behavior in Tomcat? I use Tomcat 5.5.16. Can anybody reproduce my problem? thanks Bodo Context Descriptors not only help Tomcat to know how to configure Contexts but other tools such as the Tomcat Manager and TDC often use these Context Descriptors to perform their roles properly. The locations for Context Descriptors are; 1. $CATALINA_HOME/conf/[enginename]/[hostname]/context.xml 2. $CATALINA_HOME/webapps/[webappname]/META-INF/context.xml If a Context Descriptor is not provided for a Context, Tomcat automatically creates one and places it in (1) with a filename of [webappname].xml although if manually created, the filename need not match the web application name as Tomcat is concerned only with the Context configuration contained within the Context Descriptor file(s). ___ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 - 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: multiple axis webapps
my guess is that there was an error when /newapp started up, hence it never got deployed. Check the logs Filip Rajarshi Guha wrote: Hi, I'm not sure if this is a Tomcat problem or something to do with AXIS. If the latter apologies for posting it here. I have a Tomcat server that is providing a set of AXIS webservices as well as another webapp that simply displays a welcome page. Recently, I wanted to set up another AXIS based webservice which had to be separate from the original services. Thus my $CATALINE_HOME/webapps directory looked like: axis/ XYZ/ newapp/ where axis/ and XYZ/ were my preexisting webapps. newapp/ is simply a copy of axis/. When I restart Tomcat and try doing: http://localhost:8080/newapp/ I get a 404 error message. However doing http://localhost:8080/axis/ works fine as does the same thing for the XYZ webapp. My problem is: I can't remember how I need to set up a new webapp. I digged through the config files for Tomcat and there are no references to my preexisting services. Furthermore I had figured that Tomcat would simply invoke the webapp based on the name in the URL. The web.xml file for the newapp webapp is identical to the one for the AXIS webapp (except for the name of the attachments directory). I'm totally stumped and any pointers would be appreciated. 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]
Tomcat + IIS + SSL
Hi, We are currently running tomcat on port 8080 and IIS 6 on port 80, and depending on what directory the user selects, e.g http://www.blah.com/redirectToTomcat The request gets forwarded to the appropriate tomcat webapp on port 8080. We are using the Jakarta Isapi Redirector isapi_redirect.dll to do this. This has worked fine for months. The second I uncomment this section in tomcat's server.xml: !-- Define a SSL HTTP/1.1 Connector on port 8443 -- !-- Connector port=8443 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false disableUploadTimeout=true acceptCount=100 scheme=https secure=true clientAuth=false sslProtocol=TLS / -- IIS redirection hangs. Accessing tomcat webapp using :8080 still works, but IIS does not forward to it any longer. I also tried changing the connector port from 8443 to 9443 but same problem. To be honest, I'm not sure if I should use an SSL certificate for IIS and somehow have it take care of security, or to simply add it to the 8443 connector in Tomcat. (that's a less important story) What I really need to know is how to make them work together using https, with the minimum being IIS redirecting say https://./blahblah to tomcat https://.:8443/blahblah. I've tried this and get the hanging problem as described above. I've gotten tomcat to work fine with SSL on my development machine (which does not have IIS redirection at all) but not on our server which does use IIS. Unfortunately I haven't been able to find anything very useful on this on Google/forums etc and have minimum time frames to play around testing different options on the server. I'd appreciate any help/ideas. Thanks.
RE: Tomcat + IIS + SSL
You should use the AJP connector to communicate between IIS (isapi_redirect.dll) and Tomcat (via JK). Let IIS handle the web, ssl, and port problems. Tim -Original Message- From: Andrew Bubnic [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 25, 2006 8:29 PM To: users@tomcat.apache.org Subject: Tomcat + IIS + SSL Hi, We are currently running tomcat on port 8080 and IIS 6 on port 80, and depending on what directory the user selects, e.g http://www.blah.com/redirectToTomcat The request gets forwarded to the appropriate tomcat webapp on port 8080. We are using the Jakarta Isapi Redirector isapi_redirect.dll to do this. This has worked fine for months. The second I uncomment this section in tomcat's server.xml: !-- Define a SSL HTTP/1.1 Connector on port 8443 -- !-- Connector port=8443 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false disableUploadTimeout=true acceptCount=100 scheme=https secure=true clientAuth=false sslProtocol=TLS / -- IIS redirection hangs. Accessing tomcat webapp using :8080 still works, but IIS does not forward to it any longer. I also tried changing the connector port from 8443 to 9443 but same problem. To be honest, I'm not sure if I should use an SSL certificate for IIS and somehow have it take care of security, or to simply add it to the 8443 connector in Tomcat. (that's a less important story) What I really need to know is how to make them work together using https, with the minimum being IIS redirecting say https://./blahblah to tomcat https://.:8443/blahblah. I've tried this and get the hanging problem as described above. I've gotten tomcat to work fine with SSL on my development machine (which does not have IIS redirection at all) but not on our server which does use IIS. Unfortunately I haven't been able to find anything very useful on this on Google/forums etc and have minimum time frames to play around testing different options on the server. I'd appreciate any help/ideas. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 4.1.24 - Out of memory
HI All, My name is Kingston. I am currently running Tomcat 4.1.24 on Windows 2003 Server (SP 1) with jd2sk1.4.2_04. The application accesses a MS SQL Server 2000 through a JDBC driver. Tomcat loads properly and the application can be accessed. However, after a half a day and a number of users accessing the application I get the error java.lang.OutOfMemoryError. The number of users accessing the application is around 50 at any one time. I am starting the tomcat via the service. The server has 2GB of ram, out of which SQL Server is taking 800 MB. What I have also noticed during my testing is when I open the application and access the screen, the memory usage keeps increasing. Any ideas on what is the cause of the problem? Kingston Sew - How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates.
Re: Tomcat 4.1.24 - Out of memory
First guess, there are many memory leaks in your application...things like unclosed connections and all... Did you check on those? -- Vivek. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.24 - Out of memory
1. some jsps or servlets have probably forgotten to close some Statement or ResultSet or Connections. Fix them. 2. You could try using connection pooling if possible. 3. remove any unwanted jars from your tomcat. - Manivannan Palanichamy http://geocities.com/manivannan57 -- View this message in context: http://www.nabble.com/Tomcat-4.1.24---Out-of-memory-t1509167.html#a4095212 Sent from the Tomcat - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
