Specifying SMTP port in server.xml
Hello, I've googled and searched the archives... The docs for tomcat 4.1 state: WARNING - The default configuration assumes that there is an SMTP server listing on port 25 on localhost. If this is not the case, edit the $CATALINA_HOME/conf/server.xml file, and modify the parameter value for the mail.smtp.host parameter to be the host name of an SMTP server on your network. Now, I've got more SSH tunnels for stuff than you can shake a stick at, and it just so happens that the SMTP server I want to use is localhost listening on port X. I tried the format of: hostname:port for the mail.smtp.host param I also tried to see if there was a mail.smtp.port param Neither of these seemed to work. Any help is greatly appreciated... I can always dig into the code :-) Thanks, -Troy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Repost: Double Login
Are you using cookies or URL re-writing for session identifier? Are you doing anything funky with domain names or other such trickery which would cause your cookie to not be available upon doing the forward? -Troy -Original Message- From: Nathan McMinn [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 9:07 AM To: [EMAIL PROTECTED] Subject: Repost: Double Login Hi all, Some of you had been kind enough to assist with this issue I posted previously. I had thought it was fixed, but it has appeared again. Any ideas? I recently switched a web application from a memory realm to a JDBC realm for authentication. After making the switch, the web app now requires that users log in twice. The app is running with SSL, and using Basic authentication. The Login.jsp page listed in the XML below as the welcome file simply sets up session objects, etc. The first login occurs before the Login.jsp page will load. Once all of the session setup is complete, the Login.jsp page forwards the user to the application's main menu. It is at this point that the system asks for another login. Has anyone seen this behavior before? I've already searched Google, JGuru, etc etc. This is the current web.xml for the application having the problem. Any help would be greatly appreciated. Thanks.. Nathan McMinn web-app mime-mapping extensionjs/extension mime-typetext/javascript/mime-type /mime-mapping welcome-file-list welcome-fileLogin.jsp/welcome-file /welcome-file-list security-constraint display-nameWWEX Security Constraint/display-name web-resource-collection web-resource-nameDELETED/web-resource-name !-- Define the context-relative URL(s) to be protected -- url-pattern/*/url-pattern /web-resource-collection auth-constraint !-- Anyone with one of the listed roles may access this area -- role-nameuser/role-name /auth-constraint user-data-constraint transport-guaranteeCONFIDENTIAL/transport-guarantee /user-data-constraint /security-constraint login-config auth-methodBASIC/auth-method realm-nameDELETED/realm-name /login-config /web-app -- 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]
Tomcat 4.x and Java Processes
I've been looking all over for the answer to this and can't seem to find a good answer. My basic question is that when I start up a *very* basic tomcat config (JMX Support, HTTP Listener, one engine, one host, once context) I get several java processes that look the same: root 5865 0.0 5.7 227380 29548 ? S15:02 0:02 /usr/java/jdk/bin/java -Djava.endorsed.dirs= -classpath /usr/java/jdk/lib/tools.jar:/var/tomcat4/bin/bootstrap.jar -Dcatalina.base=/var/tomcat4 -Dcatalina.home=/var/tomcat4 -Djava.io.tmpdir=/var/tomcat4/temp org.apache.catalina.startup.Bootstrap start So, why are there so many processes? I set minProcessors=1 maxProcessors=1 for the Coyote HTTP connector to reduce the number of JVMs related to this... In the WebSphere world a JVM is synonymous with an Application Server, which services the requests for the modules (WAR/EAR) installed into the appserver. Any insight would be greatly appreciated. -Troy [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat 4.x and Java Processes
Yes, sorry, I forgot to mention that. Are there options for threading on linux? I think on Solaris, you can do green or native threads. If so, would a change in this setting reduce the JVM to a single pid? Thanks for the quick reply! -Troy -Original Message- From: Ben Ricker [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 3:13 PM To: Tomcat Users List Subject: Re: Tomcat 4.x and Java Processes Are you using Linux? Linux shows in-process threads as processes. If you are running Linux, then you are seeing threads within the Java process. You would expect to see a number of threads even with your simple config. Ben Ricker On Tue, 2003-01-07 at 14:07, Troy J. Kelley wrote: I've been looking all over for the answer to this and can't seem to find a good answer. My basic question is that when I start up a *very* basic tomcat config (JMX Support, HTTP Listener, one engine, one host, once context) I get several java processes that look the same: root 5865 0.0 5.7 227380 29548 ? S15:02 0:02 /usr/java/jdk/bin/java -Djava.endorsed.dirs= -classpath /usr/java/jdk/lib/tools.jar:/var/tomcat4/bin/bootstrap.jar -Dcatalina.base=/var/tomcat4 -Dcatalina.home=/var/tomcat4 -Djava.io.tmpdir=/var/tomcat4/temp org.apache.catalina.startup.Bootstrap start So, why are there so many processes? I set minProcessors=1 maxProcessors=1 for the Coyote HTTP connector to reduce the number of JVMs related to this... In the WebSphere world a JVM is synonymous with an Application Server, which services the requests for the modules (WAR/EAR) installed into the appserver. Any insight would be greatly appreciated. -Troy [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Ben Ricker [EMAIL PROTECTED] Wellinx.com -- 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.x and Java Processes
Thanks. Nope, doesn't really bother me at all just trying to learn a bit more is all. The thing that got me thinking about this in the first place is that on an older version of Tomcat (4.1.12?) the init.d script for stopping tomcat supplied with the RPM wasn't killing off all of the processes... I'll move on now - thanks Ben. -Troy -Original Message- From: Ben Ricker [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 3:31 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.x and Java Processes On Tue, 2003-01-07 at 14:21, Troy J. Kelley wrote: Yes, sorry, I forgot to mention that. Are there options for threading on linux? I think on Solaris, you can do green or native threads. If so, would a change in this setting reduce the JVM to a single pid? Thanks for the quick reply! -Troy Nope. An application like Tomcat, or the JVM for that matter, will always be multi-threaded. Green or Native has to do with how exactly the threads are created (I forgot the exact differences). What is the big deal with seeing multiple Java processes? Are you worried about RAM? Note that the threads all have the same memory allocation. You do not add those up; the shared memory is just that: shared amongst all of the threads. I would just forget about it and move on. You will not get a single PID. Well, I tale that back. Never say never when it comes to Unix; you might be able to list the Parent PIDS only by messing with the 'ps' options. I have never done that myself, so I suggest, if you feel the need, to look through the man pages for 'ps'. HTH, Ben Ricker -Original Message- From: Ben Ricker [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 3:13 PM To: Tomcat Users List Subject: Re: Tomcat 4.x and Java Processes Are you using Linux? Linux shows in-process threads as processes. If you are running Linux, then you are seeing threads within the Java process. You would expect to see a number of threads even with your simple config. Ben Ricker On Tue, 2003-01-07 at 14:07, Troy J. Kelley wrote: I've been looking all over for the answer to this and can't seem to find a good answer. My basic question is that when I start up a *very* basic tomcat config (JMX Support, HTTP Listener, one engine, one host, once context) I get several java processes that look the same: root 5865 0.0 5.7 227380 29548 ? S15:02 0:02 /usr/java/jdk/bin/java -Djava.endorsed.dirs= -classpath /usr/java/jdk/lib/tools.jar:/var/tomcat4/bin/bootstrap.jar -Dcatalina.base=/var/tomcat4 -Dcatalina.home=/var/tomcat4 -Djava.io.tmpdir=/var/tomcat4/temp org.apache.catalina.startup.Bootstrap start So, why are there so many processes? I set minProcessors=1 maxProcessors=1 for the Coyote HTTP connector to reduce the number of JVMs related to this... In the WebSphere world a JVM is synonymous with an Application Server, which services the requests for the modules (WAR/EAR) installed into the appserver. Any insight would be greatly appreciated. -Troy [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Ben Ricker [EMAIL PROTECTED] Wellinx.com -- 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: HELP, PLEASE! Tomcat creates too many threads!
Cool. This is part of what I was looking for in my post. Thanks Craig. You rule. -Troy -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 3:28 PM To: Tomcat Users List Subject: RE: HELP, PLEASE! Tomcat creates too many threads! On Tue, 7 Jan 2003, Denise Mangano wrote: Date: Tue, 7 Jan 2003 09:31:01 -0500 From: Denise Mangano [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Subject: RE: HELP, PLEASE! Tomcat creates too many threads! I am curious about the same thing. My app isn't fully up and operational yet so I do not know for sure if I suffer from the same problem, but I have noticed that while doing some testing new threads are getting started, and it usually takes a restart to get rid of them. I've seen this question posted a few times, but haven't noticed any 'resolution' or possible solutions. Can anyone recommend things to check for, settings to make, or perhaps any documentation on the issue? Is it possible that this could be a JSDK 1.4 issue? It's the only common link I've noticed between my set up and other posters with this problem. Tomcat creates threads as follows: * One thread per Host element if you turn on autoDeploy -- should not have this on a production system. * One thread per Context element if you use reloading -- should not have this on a production system. * One thread per Context element for session expiration -- required. * One thread per processor in your Connector elements. At startup it will create the number of threads you configure for minProcessors. The number will increase (up to the configured maxProcessors value) but never decrease. For most people, tuning maxProcessors is the easiest way to control the number of threads Tomcat creates, since that is where most of them come from. Be aware, though, that reducing this number also limits the number of simultaneous requests your app will handle, since each simultaneous request requires a processor thread. If you're running behind Apache (via JK or JK2), you probably also want to comment out the stand-alone connector on port 8080. Likewise, if you're running Tomcat standalone, you don't need the JK connector on 8009. Thanks :) Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. Craig -- 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]
