RE: Tomcat at Standalone
Tomcat as a standalone is really fast,reliable and good. -Oorspronkelijk bericht- Van: Anderson, M. Paul [mailto:[EMAIL PROTECTED] Verzonden: Friday, March 04, 2005 2:02 PM Aan: Tomcat Users List Onderwerp: Tomcat at Standalone This question must have been asked a million times but I can't seem to find any information on it - any advice would be appreciated. I need to stand up a web site that will only serve jsp and servlets. I suspect the number of concurrent users will be no more than 10, but it could possibly grow in the future. Here are my questions: What is industry best practice for setting up a jsp/servlet site that will not require any static HTML pages? Can Tomcat be reliably used as standalone for this purpose? Is this the normal configuration for this type of site? Are there known security issues with using Tomcat in standalone? The other piece would be Apache, if it is standard practice to use it even if you don't need to serve HTML pages. Also, I will be doing all of my own authentication into the site so no security features of Apache or Tomcat will be required. Thanks a lot for any advice or pointers! Paul - 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: Tomcat at Standalone
I will attempt to answer you questions as best I can. Your file structure of your site will typically look something like this $CATALINA_HOME/ webapps/ (PLACE YOUR WEBAPPS HERE) common/ lib/ conf/ Catalina/ localhost (CONTEXT DESCRIPTER GOES HERE) bin/ server/ Now your web application will be placed in the webapp directory. This will setup as follows: webapp/ someapplication/ pages/ Place all your jsp's here css/ Style sheets images/ images WEB-INF/ web.xml --- need to configure this classes/ --- application specific classes go here lib/ --- application specific jars go here Yes you can use tomcat standalone. If you are using a unix environment, port 80 is a priviledged port and you must either run tomcat as root (I do not recommend this), use jscv, or Mod_JK, or Mod_Proxy. By default, Tomcat runs on port 8080, but this can be changed to whatever you want. No more security issues than with any other webserver. You need to keep up on your patches/upgrades and monitor the security bulletins. Don't run it as root on a Unix box or Local System or Administrator on Windows. Sometimes it is easier to use the built in authentication mechanisms. That is why developers provided this stuffto save you time and effort. Tomcat provides a variety of login mechanisms. I would read up on them to see if they fit your needs. I hope that helps you out. It took me a while to figure all this stuff out and I still don't know a 1/3 of what I should. But this list is a great place to get info from. Thanks Randall -Original Message- From: Anderson, M. Paul [mailto:[EMAIL PROTECTED] Sent: Friday, March 04, 2005 6:02 AM To: Tomcat Users List Subject: Tomcat at Standalone This question must have been asked a million times but I can't seem to find any information on it - any advice would be appreciated. I need to stand up a web site that will only serve jsp and servlets. I suspect the number of concurrent users will be no more than 10, but it could possibly grow in the future. Here are my questions: What is industry best practice for setting up a jsp/servlet site that will not require any static HTML pages? Can Tomcat be reliably used as standalone for this purpose? Is this the normal configuration for this type of site? Are there known security issues with using Tomcat in standalone? The other piece would be Apache, if it is standard practice to use it even if you don't need to serve HTML pages. Also, I will be doing all of my own authentication into the site so no security features of Apache or Tomcat will be required. Thanks a lot for any advice or pointers! Paul - 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: Tomcat as standalone
Putting Apache on an Internet-visible network, and having this route its traffic to Tomcat on a local network on your website (eg a 10, 172 or 192.168 address) can improve your security no end. There is no direct way to your Tomcat server. As long as you have tightend your code for SQL and HTML scams, you will have a very safe environment. Of course this means a second server and so more cost, but if you want a Rolls-Royce solution... :-) Joe. From: Ben Souther [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: Tomcat as standalone Date: Mon, 13 Dec 2004 00:54:52 -0500 Since 90% of your app is dynamic, there is a good chance that Tomcat as a standalone may actually be more efficient. The work the webserver and connector has to do to pass the requests/responses back and forth to tomcat is all in addition to what Tomcat would have to do anyway. I would recommend giving Tomcat as a standalone a shot. If you feel you need more performance, look into your options. Putting a webserver in front of Tomcat is one of them. Load balancing, heavier hardware, clustering, are some others. Remember, Tomcat, The Apache Web Server, and the connectors needed to join the two don't have the same release cycles. Besides performance, you also want to consider maintenance and upkeep costs. If you want to be real thorough, set up both scenarios and compare them under load. Set up SSL under both scenerios. Also compare the effort to get them up and running. Then also take a look at the open bug list for Tomcat to see how many issues are related to connectors. Look at the release cycles for tomcat, apache, and the connectors. Then look at how much time you have budgeted for maintaining each setup. Without looking at your app, hardware and business plan, nobody can tell you for certain which way to go. One thing to be aware of. There is a lot of outdated information on the web claiming that Tomcat as a standalone is not ready for production. If you come across one of these sites, make sure you know either when it was written or what version of Tomcat they're talking about. Both Tomcat and the JVMs needed to run it have made great strides in recent years. What was accurate at the time it was written may be very inaccurate now. On Sun, 2004-12-12 at 23:33, Dola Woolfe wrote: It 90% of my website is dynamic, is it a good idea to skip the apache server altogether and just run Tomcat alone on port 80? Seems like a good idea: one few application to worry about, no headache with connecting apache and tomcat (which I still haven't figured out how to do with 5.x) and so forth. Please, any opinions. Also is 5.5 ready for prime-time? Thank you very much in advance. Dola __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo - 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] _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat as standalone
When done right, true. Apache has a long, proven track record when it comes to safety. But also remember, if you have two servers running, you have to servers to secure and monitor. You'll have to keep on top of any new exploits for Tomcat AND Apache. On Mon, 2004-12-13 at 08:38, Jon Doe wrote: Putting Apache on an Internet-visible network, and having this route its traffic to Tomcat on a local network on your website (eg a 10, 172 or 192.168 address) can improve your security no end. There is no direct way to your Tomcat server. As long as you have tightend your code for SQL and HTML scams, you will have a very safe environment. Of course this means a second server and so more cost, but if you want a Rolls-Royce solution... :-) Joe. From: Ben Souther [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: Tomcat as standalone Date: Mon, 13 Dec 2004 00:54:52 -0500 Since 90% of your app is dynamic, there is a good chance that Tomcat as a standalone may actually be more efficient. The work the webserver and connector has to do to pass the requests/responses back and forth to tomcat is all in addition to what Tomcat would have to do anyway. I would recommend giving Tomcat as a standalone a shot. If you feel you need more performance, look into your options. Putting a webserver in front of Tomcat is one of them. Load balancing, heavier hardware, clustering, are some others. Remember, Tomcat, The Apache Web Server, and the connectors needed to join the two don't have the same release cycles. Besides performance, you also want to consider maintenance and upkeep costs. If you want to be real thorough, set up both scenarios and compare them under load. Set up SSL under both scenerios. Also compare the effort to get them up and running. Then also take a look at the open bug list for Tomcat to see how many issues are related to connectors. Look at the release cycles for tomcat, apache, and the connectors. Then look at how much time you have budgeted for maintaining each setup. Without looking at your app, hardware and business plan, nobody can tell you for certain which way to go. One thing to be aware of. There is a lot of outdated information on the web claiming that Tomcat as a standalone is not ready for production. If you come across one of these sites, make sure you know either when it was written or what version of Tomcat they're talking about. Both Tomcat and the JVMs needed to run it have made great strides in recent years. What was accurate at the time it was written may be very inaccurate now. On Sun, 2004-12-12 at 23:33, Dola Woolfe wrote: It 90% of my website is dynamic, is it a good idea to skip the apache server altogether and just run Tomcat alone on port 80? Seems like a good idea: one few application to worry about, no headache with connecting apache and tomcat (which I still haven't figured out how to do with 5.x) and so forth. Please, any opinions. Also is 5.5 ready for prime-time? Thank you very much in advance. Dola __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo - 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] _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ - 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: Tomcat as standalone
Dola, You will find a wealth of opinions on this. The real answer is always a big IT DEPENDS. Because each case is different only you can really determine this. Some things to ask: Is there something you are doing that Tomcat can't do unless connected to Apache? Are the majority of your hits to the static content? How many apps are running? How will the apps and static content be managed? And I am sure many on the list (more experienced than I) can add some more. I currently have a small site and all is served by Tomcat. Performs fine for me. As Tomcat has matured it has improved to the point that it can run standalone in all but the most demanding situations. And again you will find a wide range of opinions on this. To begin with, I think you will be fine with Tomcat alone. Unless there is a functionality of Apache that you need. You can always add it later if needed. Just my .02 Doug - Original Message - From: Dola Woolfe [EMAIL PROTECTED] To: Tom Cat [EMAIL PROTECTED] Sent: Sunday, December 12, 2004 11:33 PM Subject: Tomcat as standalone It 90% of my website is dynamic, is it a good idea to skip the apache server altogether and just run Tomcat alone on port 80? Seems like a good idea: one few application to worry about, no headache with connecting apache and tomcat (which I still haven't figured out how to do with 5.x) and so forth. Please, any opinions. Also is 5.5 ready for prime-time? Thank you very much in advance. Dola __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo - 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: Tomcat as standalone
Since 90% of your app is dynamic, there is a good chance that Tomcat as a standalone may actually be more efficient. The work the webserver and connector has to do to pass the requests/responses back and forth to tomcat is all in addition to what Tomcat would have to do anyway. I would recommend giving Tomcat as a standalone a shot. If you feel you need more performance, look into your options. Putting a webserver in front of Tomcat is one of them. Load balancing, heavier hardware, clustering, are some others. Remember, Tomcat, The Apache Web Server, and the connectors needed to join the two don't have the same release cycles. Besides performance, you also want to consider maintenance and upkeep costs. If you want to be real thorough, set up both scenarios and compare them under load. Set up SSL under both scenerios. Also compare the effort to get them up and running. Then also take a look at the open bug list for Tomcat to see how many issues are related to connectors. Look at the release cycles for tomcat, apache, and the connectors. Then look at how much time you have budgeted for maintaining each setup. Without looking at your app, hardware and business plan, nobody can tell you for certain which way to go. One thing to be aware of. There is a lot of outdated information on the web claiming that Tomcat as a standalone is not ready for production. If you come across one of these sites, make sure you know either when it was written or what version of Tomcat they're talking about. Both Tomcat and the JVMs needed to run it have made great strides in recent years. What was accurate at the time it was written may be very inaccurate now. On Sun, 2004-12-12 at 23:33, Dola Woolfe wrote: It 90% of my website is dynamic, is it a good idea to skip the apache server altogether and just run Tomcat alone on port 80? Seems like a good idea: one few application to worry about, no headache with connecting apache and tomcat (which I still haven't figured out how to do with 5.x) and so forth. Please, any opinions. Also is 5.5 ready for prime-time? Thank you very much in advance. Dola __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo - 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: Tomcat 4.1.30 Standalone and FOP ?
if you are refering to the jakarta Formatting Objects Processor libraries then yes, I use them extensively for pdf report generation. Put the FOP jar, plus any of the XML/XSLT etc jars, in a suitable location and off you go Matt - Original Message - From: Philippe Couas [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 14, 2004 11:29 AM Subject: Tomcat 4.1.30 Standalone and FOP ? Hi, Can i associate FOP with Tomcat 4.1.30 without Apache ?? Thanks Philippe Philippe COUAS Responsable Développement INFODEV S.A. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5 standalone on Linux 2.6
David Rees wrote: On Wed, January 7, 2004 1at 1:54 am, Remy Maucherat wrote: Does anyone have stability issues on this platform (without any LD_ASSUME_KERNEL, and with Sun JDK 1.4.2 or similar very recent VM) ? I'm trying to compare with Redhat 9 and see if the troubles also happen with that (cleaner) platform. Bonus question: How's the performance / scalability ? I've been running Linux kernels 2.6.0 on a couple of very lightly loaded Tomcat servers without any issues. This is running on Fedora Core 1 and JDK 1.4.2_01-b06 (which reminds me, I should upgrade that machine to the latest JDK, 1.4.2_03-b02). No LD_ASSUME_KERNEL env vars set. I also have a Redhat 7.3 with kernel 2.6.0 server running Tomcat with JDK 1.4.2_02-b03 with no problems, but again it's a development server so no real load. I haven't done any performance / scalability tests but theoretically it should be a lot better than 2.4 kernels. This was a bonus question :) I was wondering if Tomcat 5 (or 4.1.29, it's basically the same for the connector) had the same issues than on Redhat 9 (with Redhat kernels) and therefore needed a LD_ASSUME_KERNEL. The Redhat issue occurs regardless of the load, so your answer clears this :) Thanks ! BTW, I'm not sure what platform you really mean by Linux 2.6 as that isn't a specific platform, but any Linux distribution running a 2.6 kernel. Yes, that was the question. -- x Rémy Maucherat Senior Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5 standalone on Linux 2.6
I've also been running a development machine with RH9/kernel 2.6.0 using Tomcat 4.1.29/Apache 2.0.48/mod_jk/JDK-1.4.2_03/struts/jdbc-common pool/Postgresql-7.4.1. No real load test yet, but haven't needed to set the LD_KERNEL_ASSUME yet. I'm going to start working with JMeter and see if I can produce some benchmark results against the 2.4 kernel. I'll be putting the setup procedure and benchmark results here: http://daydream.stanford.edu/tomcat/install_web_services.html What was meant by Linux 2.6? Was that Debian or Suse? Oscar Does anyone have stability issues on this platform (without any LD_ASSUME_KERNEL, and with Sun JDK 1.4.2 or similar very recent VM) ? I'm trying to compare with Redhat 9 and see if the troubles also happen with that (cleaner) platform. Bonus question: How's the performance / scalability ? I've been running Linux kernels 2.6.0 on a couple of very lightly loaded Tomcat servers without any issues. This is running on Fedora Core 1 and JDK 1.4.2_01-b06 (which reminds me, I should upgrade that machine to the latest JDK, 1.4.2_03-b02). No LD_ASSUME_KERNEL env vars set. I also have a Redhat 7.3 with kernel 2.6.0 server running Tomcat with JDK 1.4.2_02-b03 with no problems, but again it's a development server so no real load. I haven't done any performance / scalability tests but theoretically it should be a lot better than 2.4 kernels. BTW, I'm not sure what platform you really mean by Linux 2.6 as that isn't a specific platform, but any Linux distribution running a 2.6 kernel. -Dave - 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: Tomcat 5 standalone on Linux 2.6
On Wed, January 7, 2004 1at 1:54 am, Remy Maucherat wrote: Does anyone have stability issues on this platform (without any LD_ASSUME_KERNEL, and with Sun JDK 1.4.2 or similar very recent VM) ? I'm trying to compare with Redhat 9 and see if the troubles also happen with that (cleaner) platform. Bonus question: How's the performance / scalability ? I've been running Linux kernels 2.6.0 on a couple of very lightly loaded Tomcat servers without any issues. This is running on Fedora Core 1 and JDK 1.4.2_01-b06 (which reminds me, I should upgrade that machine to the latest JDK, 1.4.2_03-b02). No LD_ASSUME_KERNEL env vars set. I also have a Redhat 7.3 with kernel 2.6.0 server running Tomcat with JDK 1.4.2_02-b03 with no problems, but again it's a development server so no real load. I haven't done any performance / scalability tests but theoretically it should be a lot better than 2.4 kernels. BTW, I'm not sure what platform you really mean by Linux 2.6 as that isn't a specific platform, but any Linux distribution running a 2.6 kernel. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.1.24 Standalone max requests serviced java exception
Hi all, After realizing that the application bug wasn't a bug or my main culprit, I did some checking on my machine setup. I found that Hyperthreading actually decreased the total load Tomcat could handle. Once I turned HT off, I was able to significantly increase the amount of load the server could handle (my application uses a lot of jsp pages). Just wanted to post a follow up. -Hakan -Original Message- From: Kilic, Hakan [mailto:[EMAIL PROTECTED] Sent: Friday, November 21, 2003 9:53 AM To: 'Tomcat Users List' Subject: RE: Tomcat 4.1.24 Standalone max requests serviced java exception Hi Yansheng, That was a great link, thanks! I did happen to have an error page specified for my application, and once I removed this, I found that another java exception was being reported, one from my application itself, that was being hidden by the illegalstateexception. Thanks so much! -Hakan Kilic -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Thursday, November 20, 2003 3:17 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.1.24 Standalone max requests serviced java exception Here is a good link explaining the error: http://www2.real-time.com/rte-tomcat/2000/Jun/msg02488.html -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Thursday, November 20, 2003 1:12 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.1.24 Standalone max requests serviced java exception I will give this a try: I don't think this is related to the number of requests. By default, JSP pages will try to create a session. So if you call a new jsp page after the response has been sent committed, this is exactly what is supposed to happen. Are you trying to forward or redirect the reponse after it's being committed? How do you test your application, btw? -Yan -Original Message- From: Kilic, Hakan [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 7:47 AM To: 'Tomcat Users List' Subject: Tomcat 4.1.24 Standalone max requests serviced java exception Hi all, I'm running into this java exception only when increasing my traffic to my Tomcat web server. I'm running Tomcat 4.1.24 Standalone, and my traffic is about 100 concurrent connections when this happens. I'm just wondering if a) This error is really related to reaching the max number of requests my server can handle b) How can I increase the number of requests my server can service, already tinkered around with connections in the server.xml (it's a dual P3 1.4 GHz, 2G ram machine) c) What's this java exception really mean. 2003-11-18 12:45:17 JspFactoryImpl: Exception initializing page context java.lang.IllegalStateException: Cannot create a session after the response has been committed at org.apache.coyote.tomcat4.CoyoteRequest.doGetSession(CoyoteRequest.java:1884 ) at org.apache.coyote.tomcat4.CoyoteRequest.getSession(CoyoteRequest.java:1731) at org.apache.coyote.tomcat4.CoyoteRequestFacade.getSession(CoyoteRequestFacade .java:365) at org.apache.coyote.tomcat4.CoyoteRequestFacade.getSession(CoyoteRequestFacade .java:370) at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWr apper.java:268) at org.apache.jasper.runtime.PageContextImpl._initialize(PageContextImpl.java:1 38) at org.apache.jasper.runtime.PageContextImpl.initialize(PageContextImpl.java:11 4) at org.apache.jasper.runtime.JspFactoryImpl.internalGetPageContext(JspFactoryIm pl.java:175) at org.apache.jasper.runtime.JspFactoryImpl.getPageContext(JspFactoryImpl.java: 154) at org.apache.jsp.core_loadtest_jsp._jspService(core_loadtest_jsp.java:33) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch er.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher .java:498) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:8 22) at org.apache.jsp.digits_jsp._jspService(digits_jsp.java:2905) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295
RE: Tomcat 4.1.24 Standalone max requests serviced java exception
Howdy, Thank you for posting the followup -- it's important when people actually report results. Expect JDK 1.5 (this is not a tomcat-specific issue) to run better on Hyperthreaded machines. Yoav Shapira Millennium ChemInformatics -Original Message- From: Kilic, Hakan [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 26, 2003 1:48 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.1.24 Standalone max requests serviced java exception Hi all, After realizing that the application bug wasn't a bug or my main culprit, I did some checking on my machine setup. I found that Hyperthreading actually decreased the total load Tomcat could handle. Once I turned HT off, I was able to significantly increase the amount of load the server could handle (my application uses a lot of jsp pages). Just wanted to post a follow up. -Hakan -Original Message- From: Kilic, Hakan [mailto:[EMAIL PROTECTED] Sent: Friday, November 21, 2003 9:53 AM To: 'Tomcat Users List' Subject: RE: Tomcat 4.1.24 Standalone max requests serviced java exception Hi Yansheng, That was a great link, thanks! I did happen to have an error page specified for my application, and once I removed this, I found that another java exception was being reported, one from my application itself, that was being hidden by the illegalstateexception. Thanks so much! -Hakan Kilic -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Thursday, November 20, 2003 3:17 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.1.24 Standalone max requests serviced java exception Here is a good link explaining the error: http://www2.real-time.com/rte-tomcat/2000/Jun/msg02488.html -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Thursday, November 20, 2003 1:12 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.1.24 Standalone max requests serviced java exception I will give this a try: I don't think this is related to the number of requests. By default, JSP pages will try to create a session. So if you call a new jsp page after the response has been sent committed, this is exactly what is supposed to happen. Are you trying to forward or redirect the reponse after it's being committed? How do you test your application, btw? -Yan -Original Message- From: Kilic, Hakan [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 7:47 AM To: 'Tomcat Users List' Subject: Tomcat 4.1.24 Standalone max requests serviced java exception Hi all, I'm running into this java exception only when increasing my traffic to my Tomcat web server. I'm running Tomcat 4.1.24 Standalone, and my traffic is about 100 concurrent connections when this happens. I'm just wondering if a) This error is really related to reaching the max number of requests my server can handle b) How can I increase the number of requests my server can service, already tinkered around with connections in the server.xml (it's a dual P3 1.4 GHz, 2G ram machine) c) What's this java exception really mean. 2003-11-18 12:45:17 JspFactoryImpl: Exception initializing page context java.lang.IllegalStateException: Cannot create a session after the response has been committed at org.apache.coyote.tomcat4.CoyoteRequest.doGetSession(CoyoteRequest.java :188 4 ) at org.apache.coyote.tomcat4.CoyoteRequest.getSession(CoyoteRequest.java:1 731) at org.apache.coyote.tomcat4.CoyoteRequestFacade.getSession(CoyoteRequestF acad e .java:365) at org.apache.coyote.tomcat4.CoyoteRequestFacade.getSession(CoyoteRequestF acad e .java:370) at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequ estW r apper.java:268) at org.apache.jasper.runtime.PageContextImpl._initialize(PageContextImpl.j ava: 1 38) at org.apache.jasper.runtime.PageContextImpl.initialize(PageContextImpl.ja va:1 1 4) at org.apache.jasper.runtime.JspFactoryImpl.internalGetPageContext(JspFact oryI m pl.java:175) at org.apache.jasper.runtime.JspFactoryImpl.getPageContext(JspFactoryImpl. java : 154) at org.apache.jsp.core_loadtest_jsp._jspService(core_loadtest_jsp.java:33) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.j ava: 2 10) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295 ) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispat cher . java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDis patc h er.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispa tche r .java:498) at org.apache.jasper.runtime.JspRuntimeLibrary.include
RE: Tomcat 4.1.24 Standalone max requests serviced java exception
Hi Yansheng, That was a great link, thanks! I did happen to have an error page specified for my application, and once I removed this, I found that another java exception was being reported, one from my application itself, that was being hidden by the illegalstateexception. Thanks so much! -Hakan Kilic -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Thursday, November 20, 2003 3:17 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.1.24 Standalone max requests serviced java exception Here is a good link explaining the error: http://www2.real-time.com/rte-tomcat/2000/Jun/msg02488.html -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Thursday, November 20, 2003 1:12 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.1.24 Standalone max requests serviced java exception I will give this a try: I don't think this is related to the number of requests. By default, JSP pages will try to create a session. So if you call a new jsp page after the response has been sent committed, this is exactly what is supposed to happen. Are you trying to forward or redirect the reponse after it's being committed? How do you test your application, btw? -Yan -Original Message- From: Kilic, Hakan [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 7:47 AM To: 'Tomcat Users List' Subject: Tomcat 4.1.24 Standalone max requests serviced java exception Hi all, I'm running into this java exception only when increasing my traffic to my Tomcat web server. I'm running Tomcat 4.1.24 Standalone, and my traffic is about 100 concurrent connections when this happens. I'm just wondering if a) This error is really related to reaching the max number of requests my server can handle b) How can I increase the number of requests my server can service, already tinkered around with connections in the server.xml (it's a dual P3 1.4 GHz, 2G ram machine) c) What's this java exception really mean. 2003-11-18 12:45:17 JspFactoryImpl: Exception initializing page context java.lang.IllegalStateException: Cannot create a session after the response has been committed at org.apache.coyote.tomcat4.CoyoteRequest.doGetSession(CoyoteRequest.java:1884 ) at org.apache.coyote.tomcat4.CoyoteRequest.getSession(CoyoteRequest.java:1731) at org.apache.coyote.tomcat4.CoyoteRequestFacade.getSession(CoyoteRequestFacade .java:365) at org.apache.coyote.tomcat4.CoyoteRequestFacade.getSession(CoyoteRequestFacade .java:370) at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWr apper.java:268) at org.apache.jasper.runtime.PageContextImpl._initialize(PageContextImpl.java:1 38) at org.apache.jasper.runtime.PageContextImpl.initialize(PageContextImpl.java:11 4) at org.apache.jasper.runtime.JspFactoryImpl.internalGetPageContext(JspFactoryIm pl.java:175) at org.apache.jasper.runtime.JspFactoryImpl.getPageContext(JspFactoryImpl.java: 154) at org.apache.jsp.core_loadtest_jsp._jspService(core_loadtest_jsp.java:33) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch er.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher .java:498) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:8 22) at org.apache.jsp.digits_jsp._jspService(digits_jsp.java:2905) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke
RE: Tomcat 4.1.24 Standalone max requests serviced java exception
I will give this a try: I don't think this is related to the number of requests. By default, JSP pages will try to create a session. So if you call a new jsp page after the response has been sent committed, this is exactly what is supposed to happen. Are you trying to forward or redirect the reponse after it's being committed? How do you test your application, btw? -Yan -Original Message- From: Kilic, Hakan [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 7:47 AM To: 'Tomcat Users List' Subject: Tomcat 4.1.24 Standalone max requests serviced java exception Hi all, I'm running into this java exception only when increasing my traffic to my Tomcat web server. I'm running Tomcat 4.1.24 Standalone, and my traffic is about 100 concurrent connections when this happens. I'm just wondering if a) This error is really related to reaching the max number of requests my server can handle b) How can I increase the number of requests my server can service, already tinkered around with connections in the server.xml (it's a dual P3 1.4 GHz, 2G ram machine) c) What's this java exception really mean. 2003-11-18 12:45:17 JspFactoryImpl: Exception initializing page context java.lang.IllegalStateException: Cannot create a session after the response has been committed at org.apache.coyote.tomcat4.CoyoteRequest.doGetSession(CoyoteRequest.java:1884 ) at org.apache.coyote.tomcat4.CoyoteRequest.getSession(CoyoteRequest.java:1731) at org.apache.coyote.tomcat4.CoyoteRequestFacade.getSession(CoyoteRequestFacade .java:365) at org.apache.coyote.tomcat4.CoyoteRequestFacade.getSession(CoyoteRequestFacade .java:370) at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWr apper.java:268) at org.apache.jasper.runtime.PageContextImpl._initialize(PageContextImpl.java:1 38) at org.apache.jasper.runtime.PageContextImpl.initialize(PageContextImpl.java:11 4) at org.apache.jasper.runtime.JspFactoryImpl.internalGetPageContext(JspFactoryIm pl.java:175) at org.apache.jasper.runtime.JspFactoryImpl.getPageContext(JspFactoryImpl.java: 154) at org.apache.jsp.core_loadtest_jsp._jspService(core_loadtest_jsp.java:33) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch er.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher .java:498) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:8 22) at org.apache.jsp.digits_jsp._jspService(digits_jsp.java:2905) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2416) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at
RE: Tomcat 4.1.24 Standalone max requests serviced java exception
Here is a good link explaining the error: http://www2.real-time.com/rte-tomcat/2000/Jun/msg02488.html -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Thursday, November 20, 2003 1:12 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.1.24 Standalone max requests serviced java exception I will give this a try: I don't think this is related to the number of requests. By default, JSP pages will try to create a session. So if you call a new jsp page after the response has been sent committed, this is exactly what is supposed to happen. Are you trying to forward or redirect the reponse after it's being committed? How do you test your application, btw? -Yan -Original Message- From: Kilic, Hakan [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 7:47 AM To: 'Tomcat Users List' Subject: Tomcat 4.1.24 Standalone max requests serviced java exception Hi all, I'm running into this java exception only when increasing my traffic to my Tomcat web server. I'm running Tomcat 4.1.24 Standalone, and my traffic is about 100 concurrent connections when this happens. I'm just wondering if a) This error is really related to reaching the max number of requests my server can handle b) How can I increase the number of requests my server can service, already tinkered around with connections in the server.xml (it's a dual P3 1.4 GHz, 2G ram machine) c) What's this java exception really mean. 2003-11-18 12:45:17 JspFactoryImpl: Exception initializing page context java.lang.IllegalStateException: Cannot create a session after the response has been committed at org.apache.coyote.tomcat4.CoyoteRequest.doGetSession(CoyoteRequest.java:1884 ) at org.apache.coyote.tomcat4.CoyoteRequest.getSession(CoyoteRequest.java:1731) at org.apache.coyote.tomcat4.CoyoteRequestFacade.getSession(CoyoteRequestFacade .java:365) at org.apache.coyote.tomcat4.CoyoteRequestFacade.getSession(CoyoteRequestFacade .java:370) at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWr apper.java:268) at org.apache.jasper.runtime.PageContextImpl._initialize(PageContextImpl.java:1 38) at org.apache.jasper.runtime.PageContextImpl.initialize(PageContextImpl.java:11 4) at org.apache.jasper.runtime.JspFactoryImpl.internalGetPageContext(JspFactoryIm pl.java:175) at org.apache.jasper.runtime.JspFactoryImpl.getPageContext(JspFactoryImpl.java: 154) at org.apache.jsp.core_loadtest_jsp._jspService(core_loadtest_jsp.java:33) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch er.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher .java:498) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:8 22) at org.apache.jsp.digits_jsp._jspService(digits_jsp.java:2905) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995
RE: Tomcat 4 StandAlone Web Server, Static HTML and Images
Thanks Jeff, Steve: Giving me a lot of ideas: Sadly I'm still running
full speed into mud ...
I have changed the image directory to reside under my WEB-INF folder, do
I need to configure this in one of the xml files as well? ie.
application web.xml, or server.xml or something?
I have written a filter that does authentication: It serves the
index.shtml file, but for some reason I have to specify it as
WEB-INF\index.shtml to make it work ...
snip ---
if (!validated) {
// Create the RequestDispatcher
Globals.utility.Log(className,
doFilter:,
Forwarding to + getHtmlResult, 5);
RequestDispatcher rd = config.getServletContext().
getRequestDispatcher( getHtmlResult );
rd.forward( req, res );
return ;
}
--- snip
where getHtmlResult is a string I read from a xml file. To make it work
I need to specify WEB-INF\index.shtml in my xml file.
This then serves the html, but none of my stylesheets or images are
displayed ...
snip ---
link rel=stylesheet type=text/css href=style.css
img src=images/logo.gif alt=Home width=142 height=60 border=0
hspace=0 vspace=0
--- snip
On Mon, 2002-11-18 at 15:58, Steve Beech wrote:
Jeff's right. You're web app is in the folder /servlet so your images should
be in /servlet/images - of course I'm assuming you've got images on the
index.shtml page and these are the ones you can't see.
You only need the one web.xml file (in the WEB-INF folder for your web-app)
- a second under images is not required.
STeve
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 18 November 2002 15:33
To: Tomcat Users List
Subject: Re: Tomcat 4 StandAlone Web Server, Static HTML and Images
Looks like you're basically putting your images in its own web app. You
may need a WEB-INF directory and trivial web.xml file under the images
directory in order for Tomcat to like it as a web app (not sure though).
Then, I think your url for the image would be /images/image.gif.
Alternatively, you could move your images directory to be within your
servlet web app. Then, your url (from index.shtml) would be
images/image.gif.
HTH,
-Jeff
p niemandt [EMAIL PROTECTED]
11/18/02 09:35 AM
Please respond to Tomcat Users List
To: Tomcat Users List [EMAIL PROTECTED]
cc:
Subject:Tomcat 4 StandAlone Web Server, Static HTML and
Images
Hi Group: Please help ...
I'm very new to servlets, though I do have a lot of programming
experience. My problem is that I can't seem to get images displayed
properly using Tomcat as the web server.
I have a very simple layout ...
webapps
/servlet
index.shtml
/WEB-INF- My servlets and web.xml
/images
contains my images
I manage to serve the index.shtml quite easily, my problem is that I
can't get the images displayed without specifying the whole url in the
form file:///dir/to/images/image.gif, and I think this is wrong.
There is a lot of information regarding how to configure a web server to
display the images, and this I can do fine, but I would like to only run
Tomcat: My site is very small, and the latency in Tomcat would not
effect it. My question is in how to specify the url for the image in the
html,
I have tried image.gif, /servlet/image.gif, ../image/image.gif,
/servlet/../image/image.gif, etc, etc.
Now I suspect I'm missing something very stupid, but sadly I have no
idea what. I do not want to code the image display, as far as I know,
Tomcat should be able to handle such a simple html site.
My servlets work well, database connectivity and all, and the site works
well if I use apache as well, but how to do this without Apache is
currently beyond me.
Any information or just hints in the correct direction would be greatly
appreciated.
--
p niemandt [EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat 4 StandAlone Web Server, Static HTML and Images
Hi,
the problem with relative URL's when using the forward-method of a
request-dispatcher is that the URL's have to be relative to the server-root and
not to the destination page's actual location
e.g. under weapps you have a images-, a JSP and the WEB-INF-directory where your
servlet resides. Now when your servlet forwards to a JSP-page via a
request-dispatcher an the JSP-page contains an image you have to use the URL:
../images/image-used-in-the-page
Georg
p niemandt schrieb:
Thanks Jeff, Steve: Giving me a lot of ideas: Sadly I'm still running
full speed into mud ...
I have changed the image directory to reside under my WEB-INF folder, do
I need to configure this in one of the xml files as well? ie.
application web.xml, or server.xml or something?
I have written a filter that does authentication: It serves the
index.shtml file, but for some reason I have to specify it as
WEB-INF\index.shtml to make it work ...
snip ---
if (!validated) {
// Create the RequestDispatcher
Globals.utility.Log(className,
doFilter:,
Forwarding to + getHtmlResult, 5);
RequestDispatcher rd = config.getServletContext().
getRequestDispatcher( getHtmlResult );
rd.forward( req, res );
return ;
}
--- snip
where getHtmlResult is a string I read from a xml file. To make it work
I need to specify WEB-INF\index.shtml in my xml file.
This then serves the html, but none of my stylesheets or images are
displayed ...
snip ---
link rel=stylesheet type=text/css href=style.css
img src=images/logo.gif alt=Home width=142 height=60 border=0
hspace=0 vspace=0
--- snip
On Mon, 2002-11-18 at 15:58, Steve Beech wrote:
Jeff's right. You're web app is in the folder /servlet so your images should
be in /servlet/images - of course I'm assuming you've got images on the
index.shtml page and these are the ones you can't see.
You only need the one web.xml file (in the WEB-INF folder for your web-app)
- a second under images is not required.
STeve
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 18 November 2002 15:33
To: Tomcat Users List
Subject: Re: Tomcat 4 StandAlone Web Server, Static HTML and Images
Looks like you're basically putting your images in its own web app. You
may need a WEB-INF directory and trivial web.xml file under the images
directory in order for Tomcat to like it as a web app (not sure though).
Then, I think your url for the image would be /images/image.gif.
Alternatively, you could move your images directory to be within your
servlet web app. Then, your url (from index.shtml) would be
images/image.gif.
HTH,
-Jeff
p niemandt [EMAIL PROTECTED]
11/18/02 09:35 AM
Please respond to Tomcat Users List
To: Tomcat Users List [EMAIL PROTECTED]
cc:
Subject:Tomcat 4 StandAlone Web Server, Static HTML and
Images
Hi Group: Please help ...
I'm very new to servlets, though I do have a lot of programming
experience. My problem is that I can't seem to get images displayed
properly using Tomcat as the web server.
I have a very simple layout ...
webapps
/servlet
index.shtml
/WEB-INF- My servlets and web.xml
/images
contains my images
I manage to serve the index.shtml quite easily, my problem is that I
can't get the images displayed without specifying the whole url in the
form file:///dir/to/images/image.gif, and I think this is wrong.
There is a lot of information regarding how to configure a web server to
display the images, and this I can do fine, but I would like to only run
Tomcat: My site is very small, and the latency in Tomcat would not
effect it. My question is in how to specify the url for the image in the
html,
I have tried image.gif, /servlet/image.gif, ../image/image.gif,
/servlet/../image/image.gif, etc, etc.
Now I suspect I'm missing something very stupid, but sadly I have no
idea what. I do not want to code the image display, as far as I know,
Tomcat should be able to handle such a simple html site.
My servlets work well, database connectivity and all, and the site works
well if I use apache as well, but how to do this without Apache is
currently beyond me.
Any information or just hints in the correct direction would be greatly
appreciated.
--
p niemandt [EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat 4 StandAlone Web Server, Static HTML and Images
Hi: This is getting closer, but somewhere I'm still doing something
extremely stupid, I think ...
Without the ../ in my url, if I check the logs, I get a 302, Moved kinda
thing, but with the ../ I get a 200 ok. The problem is that I still
can't see the image.
Can the problem be that the file served is called index.shtml, and is
not a jsp page?
I have tried to both include the request and to forward the request,
with the same results.
TIA,
On Tue, 2002-11-19 at 13:12, Georg Hanwalter wrote:
Hi,
the problem with relative URL's when using the forward-method of a
request-dispatcher is that the URL's have to be relative to the server-root and
not to the destination page's actual location
e.g. under weapps you have a images-, a JSP and the WEB-INF-directory where your
servlet resides. Now when your servlet forwards to a JSP-page via a
request-dispatcher an the JSP-page contains an image you have to use the URL:
../images/image-used-in-the-page
Georg
p niemandt schrieb:
Thanks Jeff, Steve: Giving me a lot of ideas: Sadly I'm still running
full speed into mud ...
I have changed the image directory to reside under my WEB-INF folder, do
I need to configure this in one of the xml files as well? ie.
application web.xml, or server.xml or something?
I have written a filter that does authentication: It serves the
index.shtml file, but for some reason I have to specify it as
WEB-INF\index.shtml to make it work ...
snip ---
if (!validated) {
// Create the RequestDispatcher
Globals.utility.Log(className,
doFilter:,
Forwarding to + getHtmlResult, 5);
RequestDispatcher rd = config.getServletContext().
getRequestDispatcher( getHtmlResult );
rd.forward( req, res );
return ;
}
--- snip
where getHtmlResult is a string I read from a xml file. To make it work
I need to specify WEB-INF\index.shtml in my xml file.
This then serves the html, but none of my stylesheets or images are
displayed ...
snip ---
link rel=stylesheet type=text/css href=style.css
img src=images/logo.gif alt=Home width=142 height=60 border=0
hspace=0 vspace=0
--- snip
On Mon, 2002-11-18 at 15:58, Steve Beech wrote:
Jeff's right. You're web app is in the folder /servlet so your images should
be in /servlet/images - of course I'm assuming you've got images on the
index.shtml page and these are the ones you can't see.
You only need the one web.xml file (in the WEB-INF folder for your web-app)
- a second under images is not required.
STeve
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 18 November 2002 15:33
To: Tomcat Users List
Subject: Re: Tomcat 4 StandAlone Web Server, Static HTML and Images
Looks like you're basically putting your images in its own web app. You
may need a WEB-INF directory and trivial web.xml file under the images
directory in order for Tomcat to like it as a web app (not sure though).
Then, I think your url for the image would be /images/image.gif.
Alternatively, you could move your images directory to be within your
servlet web app. Then, your url (from index.shtml) would be
images/image.gif.
HTH,
-Jeff
p niemandt [EMAIL PROTECTED]
11/18/02 09:35 AM
Please respond to Tomcat Users List
To: Tomcat Users List [EMAIL PROTECTED]
cc:
Subject:Tomcat 4 StandAlone Web Server, Static HTML and
Images
Hi Group: Please help ...
I'm very new to servlets, though I do have a lot of programming
experience. My problem is that I can't seem to get images displayed
properly using Tomcat as the web server.
I have a very simple layout ...
webapps
/servlet
index.shtml
/WEB-INF- My servlets and web.xml
/images
contains my images
I manage to serve the index.shtml quite easily, my problem is that I
can't get the images displayed without specifying the whole url in the
form file:///dir/to/images/image.gif, and I think this is wrong.
There is a lot of information regarding how to configure a web server to
display the images, and this I can do fine, but I would like to only run
Tomcat: My site is very small, and the latency in Tomcat would not
effect it. My question is in how to specify the url for the image in the
html,
I have tried image.gif, /servlet/image.gif, ../image/image.gif,
/servlet/../image/image.gif, etc, etc.
Now I suspect I'm missing something very stupid, but sadly I have no
idea what. I do not want to code the image display, as far as I know,
Tomcat should be able to handle such a simple html site.
My servlets work well
Re: Tomcat 4 StandAlone Web Server, Static HTML and Images
Do you use tomcat as standalone serving also all static files or do you use tomcat
together with a webserver like apache or iis. In this take care that your webserver
knows your webapp-directory for serving the static-files like your images
Georg
p niemandt schrieb:
Hi: This is getting closer, but somewhere I'm still doing something
extremely stupid, I think ...
Without the ../ in my url, if I check the logs, I get a 302, Moved kinda
thing, but with the ../ I get a 200 ok. The problem is that I still
can't see the image.
Can the problem be that the file served is called index.shtml, and is
not a jsp page?
I have tried to both include the request and to forward the request,
with the same results.
TIA,
On Tue, 2002-11-19 at 13:12, Georg Hanwalter wrote:
Hi,
the problem with relative URL's when using the forward-method of a
request-dispatcher is that the URL's have to be relative to the server-root and
not to the destination page's actual location
e.g. under weapps you have a images-, a JSP and the WEB-INF-directory where your
servlet resides. Now when your servlet forwards to a JSP-page via a
request-dispatcher an the JSP-page contains an image you have to use the URL:
../images/image-used-in-the-page
Georg
p niemandt schrieb:
Thanks Jeff, Steve: Giving me a lot of ideas: Sadly I'm still running
full speed into mud ...
I have changed the image directory to reside under my WEB-INF folder, do
I need to configure this in one of the xml files as well? ie.
application web.xml, or server.xml or something?
I have written a filter that does authentication: It serves the
index.shtml file, but for some reason I have to specify it as
WEB-INF\index.shtml to make it work ...
snip ---
if (!validated) {
// Create the RequestDispatcher
Globals.utility.Log(className,
doFilter:,
Forwarding to + getHtmlResult, 5);
RequestDispatcher rd = config.getServletContext().
getRequestDispatcher( getHtmlResult );
rd.forward( req, res );
return ;
}
--- snip
where getHtmlResult is a string I read from a xml file. To make it work
I need to specify WEB-INF\index.shtml in my xml file.
This then serves the html, but none of my stylesheets or images are
displayed ...
snip ---
link rel=stylesheet type=text/css href=style.css
img src=images/logo.gif alt=Home width=142 height=60 border=0
hspace=0 vspace=0
--- snip
On Mon, 2002-11-18 at 15:58, Steve Beech wrote:
Jeff's right. You're web app is in the folder /servlet so your images should
be in /servlet/images - of course I'm assuming you've got images on the
index.shtml page and these are the ones you can't see.
You only need the one web.xml file (in the WEB-INF folder for your web-app)
- a second under images is not required.
STeve
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 18 November 2002 15:33
To: Tomcat Users List
Subject: Re: Tomcat 4 StandAlone Web Server, Static HTML and Images
Looks like you're basically putting your images in its own web app. You
may need a WEB-INF directory and trivial web.xml file under the images
directory in order for Tomcat to like it as a web app (not sure though).
Then, I think your url for the image would be /images/image.gif.
Alternatively, you could move your images directory to be within your
servlet web app. Then, your url (from index.shtml) would be
images/image.gif.
HTH,
-Jeff
p niemandt [EMAIL PROTECTED]
11/18/02 09:35 AM
Please respond to Tomcat Users List
To: Tomcat Users List [EMAIL PROTECTED]
cc:
Subject:Tomcat 4 StandAlone Web Server, Static HTML and
Images
Hi Group: Please help ...
I'm very new to servlets, though I do have a lot of programming
experience. My problem is that I can't seem to get images displayed
properly using Tomcat as the web server.
I have a very simple layout ...
webapps
/servlet
index.shtml
/WEB-INF- My servlets and web.xml
/images
contains my images
I manage to serve the index.shtml quite easily, my problem is that I
can't get the images displayed without specifying the whole url in the
form file:///dir/to/images/image.gif, and I think this is wrong.
There is a lot of information regarding how to configure a web server to
display the images, and this I can do fine, but I would like to only run
Tomcat: My site is very small, and the latency in Tomcat would not
effect it. My question is in how
Re: Tomcat 4 StandAlone Web Server, Static HTML and Images
Yeah: I'm trying to use tomcat as a standalone web server: I managed to
do this fine using apache to host the images: but we don't want to run
both Apache and Tomcat for our web app. { The app is not complex enough
to warrant the extra overhead }
On Tue, 2002-11-19 at 14:46, Georg Hanwalter wrote:
Do you use tomcat as standalone serving also all static files or do you use tomcat
together with a webserver like apache or iis. In this take care that your webserver
knows your webapp-directory for serving the static-files like your images
Georg
p niemandt schrieb:
Hi: This is getting closer, but somewhere I'm still doing something
extremely stupid, I think ...
Without the ../ in my url, if I check the logs, I get a 302, Moved kinda
thing, but with the ../ I get a 200 ok. The problem is that I still
can't see the image.
Can the problem be that the file served is called index.shtml, and is
not a jsp page?
I have tried to both include the request and to forward the request,
with the same results.
TIA,
On Tue, 2002-11-19 at 13:12, Georg Hanwalter wrote:
Hi,
the problem with relative URL's when using the forward-method of a
request-dispatcher is that the URL's have to be relative to the server-root and
not to the destination page's actual location
e.g. under weapps you have a images-, a JSP and the WEB-INF-directory where your
servlet resides. Now when your servlet forwards to a JSP-page via a
request-dispatcher an the JSP-page contains an image you have to use the URL:
../images/image-used-in-the-page
Georg
p niemandt schrieb:
Thanks Jeff, Steve: Giving me a lot of ideas: Sadly I'm still running
full speed into mud ...
I have changed the image directory to reside under my WEB-INF folder, do
I need to configure this in one of the xml files as well? ie.
application web.xml, or server.xml or something?
I have written a filter that does authentication: It serves the
index.shtml file, but for some reason I have to specify it as
WEB-INF\index.shtml to make it work ...
snip ---
if (!validated) {
// Create the RequestDispatcher
Globals.utility.Log(className,
doFilter:,
Forwarding to + getHtmlResult, 5);
RequestDispatcher rd = config.getServletContext().
getRequestDispatcher( getHtmlResult );
rd.forward( req, res );
return ;
}
--- snip
where getHtmlResult is a string I read from a xml file. To make it work
I need to specify WEB-INF\index.shtml in my xml file.
This then serves the html, but none of my stylesheets or images are
displayed ...
snip ---
link rel=stylesheet type=text/css href=style.css
img src=images/logo.gif alt=Home width=142 height=60 border=0
hspace=0 vspace=0
--- snip
On Mon, 2002-11-18 at 15:58, Steve Beech wrote:
Jeff's right. You're web app is in the folder /servlet so your images should
be in /servlet/images - of course I'm assuming you've got images on the
index.shtml page and these are the ones you can't see.
You only need the one web.xml file (in the WEB-INF folder for your web-app)
- a second under images is not required.
STeve
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 18 November 2002 15:33
To: Tomcat Users List
Subject: Re: Tomcat 4 StandAlone Web Server, Static HTML and Images
Looks like you're basically putting your images in its own web app. You
may need a WEB-INF directory and trivial web.xml file under the images
directory in order for Tomcat to like it as a web app (not sure though).
Then, I think your url for the image would be /images/image.gif.
Alternatively, you could move your images directory to be within your
servlet web app. Then, your url (from index.shtml) would be
images/image.gif.
HTH,
-Jeff
p niemandt [EMAIL PROTECTED]
11/18/02 09:35 AM
Please respond to Tomcat Users List
To: Tomcat Users List [EMAIL PROTECTED]
cc:
Subject:Tomcat 4 StandAlone Web Server, Static HTML and
Images
Hi Group: Please help ...
I'm very new to servlets, though I do have a lot of programming
experience. My problem is that I can't seem to get images displayed
properly using Tomcat as the web server.
I have a very simple layout ...
webapps
/servlet
index.shtml
/WEB-INF- My servlets and web.xml
/images
contains my images
I manage to serve the index.shtml quite easily, my
Re: Tomcat 4 StandAlone Web Server, Static HTML and Images
Looks like you're basically putting your images in its own web app. You may need a WEB-INF directory and trivial web.xml file under the images directory in order for Tomcat to like it as a web app (not sure though). Then, I think your url for the image would be /images/image.gif. Alternatively, you could move your images directory to be within your servlet web app. Then, your url (from index.shtml) would be images/image.gif. HTH, -Jeff p niemandt [EMAIL PROTECTED] 11/18/02 09:35 AM Please respond to Tomcat Users List To: Tomcat Users List [EMAIL PROTECTED] cc: Subject:Tomcat 4 StandAlone Web Server, Static HTML and Images Hi Group: Please help ... I'm very new to servlets, though I do have a lot of programming experience. My problem is that I can't seem to get images displayed properly using Tomcat as the web server. I have a very simple layout ... webapps /servlet index.shtml /WEB-INF- My servlets and web.xml /images contains my images I manage to serve the index.shtml quite easily, my problem is that I can't get the images displayed without specifying the whole url in the form file:///dir/to/images/image.gif, and I think this is wrong. There is a lot of information regarding how to configure a web server to display the images, and this I can do fine, but I would like to only run Tomcat: My site is very small, and the latency in Tomcat would not effect it. My question is in how to specify the url for the image in the html, I have tried image.gif, /servlet/image.gif, ../image/image.gif, /servlet/../image/image.gif, etc, etc. Now I suspect I'm missing something very stupid, but sadly I have no idea what. I do not want to code the image display, as far as I know, Tomcat should be able to handle such a simple html site. My servlets work well, database connectivity and all, and the site works well if I use apache as well, but how to do this without Apache is currently beyond me. Any information or just hints in the correct direction would be greatly appreciated. -- p niemandt [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat 4 StandAlone Web Server, Static HTML and Images
Jeff's right. You're web app is in the folder /servlet so your images should be in /servlet/images - of course I'm assuming you've got images on the index.shtml page and these are the ones you can't see. You only need the one web.xml file (in the WEB-INF folder for your web-app) - a second under images is not required. STeve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 18 November 2002 15:33 To: Tomcat Users List Subject: Re: Tomcat 4 StandAlone Web Server, Static HTML and Images Looks like you're basically putting your images in its own web app. You may need a WEB-INF directory and trivial web.xml file under the images directory in order for Tomcat to like it as a web app (not sure though). Then, I think your url for the image would be /images/image.gif. Alternatively, you could move your images directory to be within your servlet web app. Then, your url (from index.shtml) would be images/image.gif. HTH, -Jeff p niemandt [EMAIL PROTECTED] 11/18/02 09:35 AM Please respond to Tomcat Users List To: Tomcat Users List [EMAIL PROTECTED] cc: Subject:Tomcat 4 StandAlone Web Server, Static HTML and Images Hi Group: Please help ... I'm very new to servlets, though I do have a lot of programming experience. My problem is that I can't seem to get images displayed properly using Tomcat as the web server. I have a very simple layout ... webapps /servlet index.shtml /WEB-INF- My servlets and web.xml /images contains my images I manage to serve the index.shtml quite easily, my problem is that I can't get the images displayed without specifying the whole url in the form file:///dir/to/images/image.gif, and I think this is wrong. There is a lot of information regarding how to configure a web server to display the images, and this I can do fine, but I would like to only run Tomcat: My site is very small, and the latency in Tomcat would not effect it. My question is in how to specify the url for the image in the html, I have tried image.gif, /servlet/image.gif, ../image/image.gif, /servlet/../image/image.gif, etc, etc. Now I suspect I'm missing something very stupid, but sadly I have no idea what. I do not want to code the image display, as far as I know, Tomcat should be able to handle such a simple html site. My servlets work well, database connectivity and all, and the site works well if I use apache as well, but how to do this without Apache is currently beyond me. Any information or just hints in the correct direction would be greatly appreciated. -- p niemandt [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat 4.0.1 StandAlone Web Server and SSL
Where/what is CVS? Thanks, John - Original Message - From: Peter Romianowski [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Saturday, February 16, 2002 6:14 AM Subject: RE: Tomcat 4.0.1 StandAlone Web Server and SSL Take a look into the the CVS. There is an updated version of the SSL-howto (under catalina/webapps/tomcat-doc) which describes how to use Verisign or Thawte CAs. -Original Message- From: Anton Brazhnyk [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 16, 2002 10:11 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.1 StandAlone Web Server and SSL Hi, -Original Message- From: John Echano [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 16, 2002 2:36 AM To: [EMAIL PROTECTED] Subject: Tomcat 4.0.1 StandAlone Web Server and SSL We are interested in implementing SSL four our Apache Jakarta Tomcat Server. We are running this as a standalone web server on Red Hat Linux 7.1. According to Tomcat's documentation, it currently operates on JKS format keystores (the Java's standard keystore format). Is this something supported by well-known public CAs like Verisign or Thawte? For example, Are we going to be able to generate a certificate request in a format that Thawte supports and that the return certificate can be imported into the Tomcat Server? If yes, how? The ssl-howto only provides instruction on how to use a self-sign certificate. IMHO, its possible, but you'll have to become very familiar (I wish I were) with SSL, PKI, JSSE and so on. Thanks, John Anton -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Tomcat 4.0.1 StandAlone Web Server and SSL
Hi, -Original Message- From: John Echano [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 16, 2002 2:36 AM To: [EMAIL PROTECTED] Subject: Tomcat 4.0.1 StandAlone Web Server and SSL We are interested in implementing SSL four our Apache Jakarta Tomcat Server. We are running this as a standalone web server on Red Hat Linux 7.1. According to Tomcat's documentation, it currently operates on JKS format keystores (the Java's standard keystore format). Is this something supported by well-known public CAs like Verisign or Thawte? For example, Are we going to be able to generate a certificate request in a format that Thawte supports and that the return certificate can be imported into the Tomcat Server? If yes, how? The ssl-howto only provides instruction on how to use a self-sign certificate. IMHO, its possible, but you'll have to become very familiar (I wish I were) with SSL, PKI, JSSE and so on. Thanks, John Anton -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Tomcat 4.0.1 StandAlone Web Server and SSL
Take a look into the the CVS. There is an updated version of the SSL-howto (under catalina/webapps/tomcat-doc) which describes how to use Verisign or Thawte CAs. -Original Message- From: Anton Brazhnyk [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 16, 2002 10:11 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.1 StandAlone Web Server and SSL Hi, -Original Message- From: John Echano [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 16, 2002 2:36 AM To: [EMAIL PROTECTED] Subject: Tomcat 4.0.1 StandAlone Web Server and SSL We are interested in implementing SSL four our Apache Jakarta Tomcat Server. We are running this as a standalone web server on Red Hat Linux 7.1. According to Tomcat's documentation, it currently operates on JKS format keystores (the Java's standard keystore format). Is this something supported by well-known public CAs like Verisign or Thawte? For example, Are we going to be able to generate a certificate request in a format that Thawte supports and that the return certificate can be imported into the Tomcat Server? If yes, how? The ssl-howto only provides instruction on how to use a self-sign certificate. IMHO, its possible, but you'll have to become very familiar (I wish I were) with SSL, PKI, JSSE and so on. Thanks, John Anton -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Tomcat as standalone container
NO need of Apache -Original Message-From: Casstevens, Brian [mailto:[EMAIL PROTECTED]]Sent: Thursday, June 14, 2001 6:17 PMTo: [EMAIL PROTECTED]Subject: Tomcat as standalone container I am trying to use Tomcat as a standalone servlet container.To do this, do I need to have the Apache Web server installed and running, or is this contained in Tomcat? Thanks, Brian Casstevens
RE: Tomcat as standalone container
...hence the use of the word "standalone" ;) - r -Original Message-From: Rajeshwar Rao.V [mailto:[EMAIL PROTECTED]]Sent: June 14, 2001 8:49 AMTo: '[EMAIL PROTECTED]'Subject: RE: Tomcat as standalone container NO need of Apache -Original Message-From: Casstevens, Brian [mailto:[EMAIL PROTECTED]]Sent: Thursday, June 14, 2001 6:17 PMTo: [EMAIL PROTECTED]Subject: Tomcat as standalone container I am trying to use Tomcat as a standalone servlet container.To do this, do I need to have the Apache Web server installed and running, or is this contained in Tomcat? Thanks, Brian Casstevens
RE: Tomcat as standalone container
The Apache Web server is not contained in Tomcat. Tomcat is a Web server which includes a servlet engine and a JSP engine. To use Tomcat, there is no need to install a native Web server such as Apache or IIS or Netscape. Tomcat is able to serve static html pages as well. For production needs, Tomcat is also able to run ontop of such native servers (either as a in-process or out-of-process container) but this is not necessary. This is a choice which depends of your context. For more information, download the last version and have a look to the user's guide. Christian BERNARD Nagora Technologies -Original Message-From: Casstevens, Brian [mailto:[EMAIL PROTECTED]]Sent: Thursday, June 14, 2001 2:47 PMTo: [EMAIL PROTECTED]Subject: Tomcat as standalone container I am trying to use Tomcat as a standalone servlet container.To do this, do I need to have the Apache Web server installed and running, or is this contained in Tomcat? Thanks, Brian Casstevens
Re: Tomcat 3.2 standalone on Solaris 2.7 core dumping
HI Tom: try increasing the memory available to shell in which your tomcat server is running(on popup window in case ur using defaults) It might work Hemant - Original Message - From: Tom Amiro [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, June 03, 2001 10:31 PM Subject: Tomcat 3.2 standalone on Solaris 2.7 core dumping Hi, I'm using Tomcat 3.2 in standalone mode on Solaris 2.7 with the JDK 1.3, and it is core dumping with Java Out of Memory. Tomcat is running a servlet that performs XSLT transformations on an XML file that is ~1.4MB big and returns html output to the client browser. It was running fine during development, but once the servlet was made available to the web site's users (www.coolrunning.com), it began crashing. Must be due to the increased load. I don't know how heavy the load is exactly, nor how to determine it, but the site is not an Ebay by any means. I'm assuming Tomcat can handle a single servlet application on a low-traffic web site -- less than 100,000 hits a day. Following suggestions on the web, I've - Increased the memory allocated to Tomcat to 128M (using -Xmx128m switch) - Increased the max_threads to 100 - Increased the file descriptors to 256 - added System.gc(); to the end of the Servlet code These changes have helped; it takes much longer, but it still crashes under normal use. I've been watching the output from the top command. It shows that the Tomcat Java process is starting with about 32MB and over time and load it climbs. It was running at 62M for quite a while, and it even dropped to 55M, and then grew to 169M without crashing. Not sure how high the SIZE (memory) gets to before it crashes; but crash it does with a core dump. With the 'ps' command, I don't see any accumulation of treads. Here's a dump 81= /usr/ucb/ps -auxww | grep thread root 24231 73.0 28.3173016141648 ?R 20:30:02 21:51 /usr/local/j2sdk/ bin/../bin/sparc/native_threads/java -Xmx128m -Dtomcat.home=/usr/local/tomca t or g.apache.tomcat.startup.Tomcat I don't know how to analyze the core dump, except to use strings on it. At least, I can see that it was definitely caused by Tomcat. What would be a reasonable setting on max_threads? Is 100 just to low? I could start Tomcat with more memory, say 256M (system has 512MB), but I don't want to negatively impact the other applications. The system is running Apache without any problems, independent of Tomcat. I've spent months developing this JSP/Servlet application for the Coolrunning Events calendar, and can't go back. Have to make Tomcat work! Any help appreciated. Tom
Re: Tomcat as standalone HTTP server
On Wed, 25 Apr 2001, Olivier LAUDREN wrote: | Hi, | | Is there somebody using Jakarta Tomcat as standalone HTTP server? | Witch (is/are) the most important difference(s) between this | configuration and Apache + Tomcat? Speed on static documents. Apache is written in some C, while Tomcat is written in the considerably slower Java. Also you can load-balance via the apache, having one front-end apache server, and 49 backend Tomcats. The apache can then do sticky session load balancing between those tomcats. It's a more messy config using both, but it works! -- Mvh, Endre
RE: Tomcat 3.2.1 Standalone, JSSE 1.0.2 and Socket ERROR
I have the same problem as you!
I've also tried the the URL with setting,
System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.ww
w.protocol");
I get the same error from both test and it is:
Tomcat server says:
2001-02-01 01:15:20 - Ctx( ): IOException in: R( /) Received fatal alert:
certificate_unknown
Client app says:
javax.net.ssl.SSLException: untrusted server cert chain at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.a([DashoPro-V1.2-120198])at
com.sun.net.ssl.internal.ssl.ClientHandshaker.a([DashoPro-V1.2-120198])
at
com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage([DashoPro-V1.2-
120198])at
com.sun.net.ssl.internal.ssl.Handshaker.process_record([DashoPro-V1.2-120198
]) at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.a([DashoPro-V1.2-120198])at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.a([DashoPro-V1.2-120198])at
com.sun.net.ssl.internal.ssl.AppOutputStream.write([DashoPro-V1.2-120198])
at java.io.OutputStream.write(OutputStream.java:65) at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake([DashoPro-V1.2-120
198]) at untitled1.SSLTest.handshake(SSLTest.java, Compiled Code) at
untitled1.SSLTest.init(SSLTest.java:17) at
untitled1.SSLTest.main(SSLTest.java:109)
Anyone that can explain this to me?
I guess that the problem is that if not using a trusted CA server, but is
there a workarond when developing?
--Tobias--
-Original Message-
From: Valentin Sanchez [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 05, 2001 11:27 AM
To: [EMAIL PROTECTED]
Subject: Tomcat 3.2.1 Standalone, JSSE 1.0.2 and Socket ERROR
I am trying to use Tomcat 3.2.1 standalone compiled with SSL support and
Jsse 1.0.2
I hava configured Tomcat to use port 443 with SSL and it works fine using a
browser.
If I use "http://myserver/mypage.html" it do not use ssl
If I use "https://myserver/mypage.html" it uses ssl.
Now I m using jsse to open a secure socket connection to get the same page.
The code is as follows:
***
SSLSocket socket =
(SSLSocket)factory.createSocket("myserver", 443);
socket.startHandshake();
PrintWriter out = new PrintWriter(
new BufferedWriter(
new OutputStreamWriter(
socket.getOutputStream(;
out.println("GET http://myserver/mypage.html HTTP/1.0");
out.println();
out.flush();
if (out.checkError())
System.out.println(
"SSLSocketClient: java.io.PrintWriter error");
/* read response */
BufferedReader in = new BufferedReader(
new InputStreamReader(
socket.getInputStream()));
String inputLine;
while ((inputLine = in.readLine()) != null)
System.out.println(inputLine);
in.close();
out.close();
socket.close();
***
*
The code is copied from the Jsse examples.
Tomcat returns an error: Request not found and the execption in Tomcat is:
java.io.exception Name of file,directory or volume label is not valid.
The same code works fine with www.verisign.com/index.html.
It also works with a server using IIS4.0.
Thanks in advance,
Valen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: Tomcat 3.2 standalone + SSL - Help please
try https://ip.add.re.ss:8443 instead. ie has to know that you want to use https instead of http Filip - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, December 19, 2000 2:26 PM Subject: Tomcat 3.2 standalone + SSL - Help please I have followed the instructions in server.xml for configuring SSL with Tomcat. When I try to access the SSL connection at http://ip.add.re.ss:8443, the server thinks about it, then my browser (IE5) displays and empty certificates box for me the select the certificate I want to use. The certificate I want to use is the one created by following the tomcat-ssl-howto. I specified a keystore directory when using the keytool command. Perusing the Tomcat archives revealed nothing useful, but the OpenSSL FAQ produced this interesting little tidbit: "What will typically happen is that when a server requests authentication it will either not include your certificate or tell you that you have no client certificates (Netscape) or present you with an empty list box (MSIE). The reason for this is that when a server requests a client certificate it includes a list of CAs names which it will accept. Browsers will only let you select certificates from the list on the grounds that there is little point presenting a certificate which the server will reject. The solution is to add the relevant CA certificate to your servers "trusted CA list". How you do this depends on the server sofware in uses." Does this mean Tomcat needs to be configured to present the certificate? If so, how and where? Thanks in advance. Dion Vansevenant Internetwork Administrator MRO.com
Re: Tomcat 3.1 standalone - how to resolve ~user requests???
[EMAIL PROTECTED] wrote: [Sorry for the repost - but I'm stumped on this one. I've looked in the online docs, etc.] How do I get a *standalone* Tomcat 3.1 server to resolve ~user requests? The Apache 1.3.11 server handles ~user requests fine (UserDir public_html). Is there something that needs to be added to jakarta-tomcat/conf/server.xml or a command line argument that lets Tomcat know what '~' expand to? '~' expands to /dc/home NOT /home on our systems. What is Tomcat's equivalent of Apache's UserDir public_html? Example: http://asterix:8081/~bryan Apache handles this fine. Tomcat complains that ~bryan directory is not found. I don't think that Tomcat does handle that sort of requests. As stated somewhere in the docs Tomcat is not a webserver replacement, so why should one like to have web-server functionallity? Also I wouldn't use the Tomcat standalone in a production environment. Try to get rid of that setup, place Tomcat behind a web server like Apache that that handles that kind of stuff and let Tomcat do what it's design for: handle applications. br Wolfgang -- KPNQwest Austria GmbH., A-1150 Wien, Diefenbachgasse 35 Ing. Wolfgang Trexler [EMAIL PROTECTED] Web-Technik Business Solutions Tel.: +43 (1) 899 33 - 141, Fax: +43 (1) 899 33 -10 141
