Re: Solaris Sparc Performance Problem
second delays add up. I like Linux a lot myself but the bosses here feel more comfortable with more traditional business models, and besides shouldn't Java run best on a Sparc with Solaris? I am perplexed as to what the problem is and would greatly appreciate any help or ideas I can get. This may NOT be the place for this discussion but since the question was asked about Java running best on Sparc with Solaris ... On the contrary the JVM is only as good as the supporting components that it runs on. In particular the threads library that it sits on. Plus all the other components all others have mentioned here like tcpip stack, name server etc. if you factor in networking components. The JVM may not run best on Solaris. If you are interested in performances of JVMs go to www.tpc.org or www.volano.com They both publish JVM numbers. I was told (and this might be a biased information, so discretion is adviced and apologies to whoever is offended) that Suns JVM performance was bad enough last year compared to IBM's they (Sun) had to pull out their numbers from the SPECjbb benchmarks from www.tpc.org just my 2 cents -- Freddie Mendoza [EMAIL PROTECTED] Search Engine for Cheap Books http://satori.com/cheapbooks
tomcat 3.2 or 3.2.1 problem
Anyone experience this with 3.2 or 3.2.1? Tomcat seem to stop communicating. It is stil running but it's just stop communicating via port 8080 or through apache. When I first start tomcat, I can invoke my servlet. After about 2 or more invocations, I cannot communicate with tomcat anymore via apache or port 8080. I have to restart it. I also noticed a lot of TIME_WAIT connections between 127.0.0.1.8007 and 127.0.0.1.51677 ^ this can be any non - reserved port number How can I debug tomcat to see why this is happening? Actually how can I even tell if Tomcat is still trying to accept connections? Oh yeah the same happens when I just go through the examples. After about 2 or 3 invocations of some servlets , the above happens. I'm not solaris 7. I've tried both jdk 1.1.7 and 1.2.2 And I've tried binaries and building tomcat myself. -- Freddie Mendoza [EMAIL PROTECTED] Search Engine for Cheap Books http://satori.com/cheapbooks
Tomcat / Apache jserv automatic startup
Hi y'all Tomcat development team, I've been a long time advocate of starting Tomcat from Apache automatically. In fact I've been doing this since pre-3.0 days. It's worked flawlessly for me until 3.2. I assume this is because this is a low priority for everyone. Anyway I think slowly the protocol that starts/monitors Tomcat from ap_jserv is slowly going away. As an example the JSERV_PING does not seem to work anymore. It leaves a connection open to Tomcat and slowly eats away the socket file descriptors until the system runs out. But I found a workaround for now by modifying code in the mod_jserv. This way it seem to work again for 3.2. Shortly I will be updating my HOWTO for 3.2. So I guess the question(s) are : 1. Will automatic startup of Tomcat be included in a plan sometime in the future even for mod_jk? 2. Maybe someone can point me to the module in Tomcat where the Apj_xx protocol is handled and I probably can help drop something in there. Or may even be something pluggable. There's been a few users who have been asking for this for a while but all I can say is that the code is changing so much that it's hard to keep up with. One day my howto works the next day it doesn't. One of the big advantages of having this is that its nice to just have one startup procedure for Apache and Tomcat. It's also nice to be able to do something like "apachectl restart" or "apachectl start/stop" to restart/stop/start both Apache and Tomcat. thanks, -- Freddie Mendoza [EMAIL PROTECTED] Search Engine for Cheap Books http://satori.com/cheapbooks
Re: [SECURITY] Security Vulnerabilities in Tomcat 3.1 and 3.2
Tomcat 3.2 final has the following security vulnerabilities that have subsequently been fixed in the CVS repository: * A URL like "http://localhost:8080/examples//WEB-INF/web.xml" can expose sensitive information (note the double slash after "examples"). * The "Show Source" custom tag used to display JSP source code can be used to expose sensitive information in WEB-INF. I was not privi to a few of the original posts regarding this. Is the vulnerability only exposed if one can access the tomcat port directly? So if I blocked all access to say port 9090 (where my tomcat port is) from any foreign machines, then it is safe? Or is the vulnerability exposed even when accessing tomcat via apache port 80? -- Freddie Mendoza [EMAIL PROTECTED]
