AW: Memory leaks?
As far as I know the Oracle JDBC driver does not follow the specificiation. You should close your all objects in the following order: 1) ResultSet 2) Statement 3) Connection -Ursprüngliche Nachricht- Von: Tim Funk [mailto:[EMAIL PROTECTED] Gesendet am: Freitag, 5. September 2003 13:02 An: Tomcat Users List Betreff: Re: Memory leaks? The JDBC spec states that when a connection is closed, all dependent assets should also be closed. So if you are using a pool, make sure your pool is compliant since the connection is never closed until the pool closes it. When garbage collection runs is a whole different story. But its just good coding to close your ResultSet, Statements as soon as your done with them. -Tim Nikola Milutinovic wrote: But depending on the DB, it can cause problems from the DB with too many open ResultSets... I had an issue with performance testing where everything but ResultSets were being closed and the Oracle DB started throwing errors after about 500 queries. Better safe than sorry. Well, from what I know, in general (not Oracle specific). If you open a connection within some scope (Servlet, JSP, any other class), then create a statement and finally a result set, shouldn't deleting the most upper scope cause all these lower levels be closed and garbage collected? With Servlets and JSP, of course, you have no control whatsoever as to when they will be put out of service. But suppose you are tidy and do a close on the connection - shouldn't that clean-up the underlying Statement(s) and ResultSet(s)? Even with connection pooling, this should work. Nix. - 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]
How to configure Tomcat to suppress adding port to URL??????
Hi Folks, is it possible to configure Tomcat 4.0 to suppress the port into the url adress (URL rewriting etc)? If yes who and in which config file? I need this due to Tomcat should run into a specical security zone and the firewall maps a specific port to my tomcat server. Therefore I would like to force Tomat not returing the Port into the URL's. Bye lot's of Thx Toby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to configure Tomcat to suppress adding port to URL??????
Uho! Does this mean that tomcat _must_ run as root user (on Solaris) due to ports lower that 1024 are not accessible by a user without root privileges. I guess the solaris admin would'nt be happy if a cricial service that may be attacked runs as root. Mhm. Any advice? Can I run tomcat without being root but using 80 or 433 ports? Thx a lot for any comments!!! Bye Toby -Original Message- From: Barney Hamish [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 12, 2003 11:29 AM To: 'Tomcat Users List' Subject: RE: How to configure Tomcat to suppress adding port to URL?? Unless tomcat is running on port 80 (the default port for HTTP) the URL _must_ include the port number otherwise the browser assumes that the webserver is running on Port 80 (which is apparently not the case). Try configuring tomcat to run on port 80 instead of 8080 (or whatever you've got it set to) in the server.xml file. Hamish -Original Message- From: Rademacher Tobias [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 12, 2003 10:26 AM To: '[EMAIL PROTECTED]' Subject: How to configure Tomcat to suppress adding port to URL?? Hi Folks, is it possible to configure Tomcat 4.0 to suppress the port into the url adress (URL rewriting etc)? If yes who and in which config file? I need this due to Tomcat should run into a specical security zone and the firewall maps a specific port to my tomcat server. Therefore I would like to force Tomat not returing the Port into the URL's. Bye lot's of Thx Toby - 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: The future of Tomcat and java.nio
Hi Folks, you can wrap a ServletInputStream or ServlertOuputStream with a Channel. Just use: java.nio.Channels.newChannel(inStream); So you are able to use nio into your servlets. I understand that's hard to port form old io to nio. But when you are able to use 1.4+ and you are also able to benefit from nio. nio is interesting for file upload/file download because if you use it wisely you can write fast and memory-safe filehandlings (mapped files does not wast JVM memory...). Other tomcat performace is quite okay. I guess nio would only help to make the container more stable which make the tandem to apache not longer relevant. As the tandem works fine - why should we replace it... Bye Toby -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 2:23 PM To: Tomcat Users List Subject: RE: The future of Tomcat and java.nio Howdy, This is a common, and will become even more prevalent, question. ;) Mr. Schnack's answer explains a big part of it: right now we still have a lot of users using JDK's older than 1.4. A JDK 1.4 requirement is not possible for the 4.x branch of tomcat. For Tomcat 5.x, there may be some discussion about this requirement, but I doubt it's going to happen. I also think most people working on tomcat recognize that the Apache http is great at what it does: so why re-invent the wheel? Especially when we barely have enough time to keep our wheel (tomcat) rolling... NIO fits in, IMHO (and I'm not speaking for any other developers) as a cool thing to do once we have a JDK 1.4 requirement, but insufficient by itself to make JDK 1.4 required. Yoav Shapira Millennium ChemInformatics -Original Message- From: Felipe Schnack [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 6:14 AM To: Tomcat Users List Subject: RE: The future of Tomcat and java.nio Yes... would be really cool, I took a look at these packages... but I think probably tomcat will implement them in a year or more, 1.3 is being used by a lot of people yet. It seems like Java 1.4's NIO package offers some very high-performance IO capabilities, such as select loops, which could allow Java to serve static content as fast as Apache can. Will Tomcat be going in the direction of using a NIO-based connector that might incorporate these high-performance features? -- 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]
Which Apache Connector works and which is recommend for Tomcat 4.1.12?
Hi Folks, we want to use Apache and Tomcat as tandem you recommend. We currently use Apache 1.3.27 and Tomcat 4.1.12 and JDK 1.4.1 on Solaris. Could be please give me a tip which kind of connector we should use. There are already 3 (!) kind of connectors: - mod_jk - mod_jk2 - mod_webapp Which will work and which will you recommend with the above mentioned version/configuration in mind? The documenation seems to be a little bit old. Does tomcat still generate the script mod_jk.conf-auto? It doesn't seem so?!? Is this different in mod_jk2? Where is mod_webapp documentation? Do you have a link? Which connetor will work with next version of tomcat e.g 5.x? Questions about Questions. Thx a lot for your advise. Bye Tobias Rademacher -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
