Re: SSL only working on localhost
problem solved the firewall exceptions were not config'ed correctly it seems the 443 inbound packet was hitting the box but not hitting tomcat itself (due to fw dropping the packets) i do however wonder for future ref, the best way to turn more logging-on for ssl (even though in this case, logging would not have helped much ...except it would have been more obvious that tomcat was NOT seeing the ssl attempts by the remote clients at all ) better logging ideas are welcomed. (as this might benefit others also) I was hoping the global debug logging level would have showm a bit more on the ssl connections, etc ...but i dont think it did that fyi Tomcat 6.0.13 Java 1.6.017 From: Guifre Bosch Fabregas guifre.bo...@gmail.com To: Tomcat Users List users@tomcat.apache.org; p...@pidster.com Sent: Wed, December 2, 2009 8:13:58 AM Subject: Re: SSL only working on localhost Can you see your page from another computer without SSL? What's your OS? Is it possible that the problem is the Firewall. Can you see the port 80 and 443 are open? 2009/12/2 Pid p...@pidster.com On 02/12/2009 12:41, Michael Dockery wrote: I have gotten ssl w/self-signed cert working on tomcat 6 a few times in the past. I am trying it again on a different server I am using port 443 when i attempt https://localhost via a browswer on the server itself the browser is properly presented with the cert warning (as i expected) however, when i try to access https from another computer, it just hangs... (and therefore NO cert warning) i have wiresharked the server, and can see the inbound 443 connections, so the firewall does not seem to be the issue. (note: the other computers are on the same subnet/lan) i have tried browsing to the servers ip, netbios name, fqdn/dns with always the same result (below): ---http is fine (the home page appears) ---however httpS does not do anything (unless i browse from the server itself to itself) further the logs do not show anything interesting and i have the log level set to debug. ideas? Idea: describe Tomcat, JVM, OS - precise versions please. Supply server.xml in use, comments removed. p - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to get java process id of a user running tomcat
i agree with Chuck and would add these commands for consideration on a windows box netstat -ano will show the pid of any java job which is tied to a tcp port likewise (on windows only): wmic process get /all /value is another win vista/win7/xp pro+ command which will show all the output from all pid's including the command line options or more specifically something like this: wmic process where commandline like '%java%' get commandline, processid hope this helps someone out there From: Caldarale, Charles R chuck.caldar...@unisys.com To: Tomcat Users List users@tomcat.apache.org Sent: Wed, December 2, 2009 9:32:18 AM Subject: RE: How to get java process id of a user running tomcat From: Pierre Goupil [mailto:goupilpie...@gmail.com] Subject: Re: How to get java process id of a user running tomcat jps -mlv will give you the PIDs of all running Java processes. Plus it's a part of the standard SUN JVM. But not for the OP, who is running an unsupported version of Tomcat on an unsupported JVM that predates the jps tool. As Pid suggested, the correct thing to do is to fix the webapp so it properly manages the threads it has started. Attack the problem, not the symptom. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
Re: Quotes appended cookie generated in Tomcat 6.0
Rajat Gupta05 wrote: Hi, I have recently upgraded to Tomcat 6.0.16 and I am observing a strange thing that quotes get appended to the cookie value. Is there some configuration in Tomcat with which we can remove these quotes? Probably not. Due to some security issues with cookie handling the parsing and generation of cookies has been made more spec compliant. I suspect you are using a v0 cookie with invalid characters hence Tomcat is automatically converting it to a v1 cookie and quoting it. I could give a more precise answer if you provided the cookie headers concerned. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Basic and Form Authentication
Hi. I got some (as yet partial) answers on this on the Apache httpd forum. Check out this : http://httpd.apache.org/docs/trunk/mod/mod_auth_form.html In summary, and subject to more confirmation by the Apache developers : A series of new Apache modules is due to appear in Apache 2.4 (the next production release version). They include mod_session and mod_auth_form, which should provide a generic form-based authentication framework. These modules are currently available in the test version of Apache (2.34). I do not know yet if they are, or can be, back-ported for Apache 2.2.14, the current production version. But all in all, it seems that this provides the as-yet missing standard form-based authentication framework which would be needed by the original poster on this thread, if he wanted to resolve his issue by using an httpd front-end (which he uses anyway for other purposes right now). Well, at least it would be a start. It remains to be seen in detail how one would set this up under Apache httpd. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
TID 170878 Re: How to get java process id of a user running tomcat
You have emailed Webjam Customer Support. To send a message to the intended recipient, please use their email address (if known) OR Go to their network, click on their network name (top left-hand side of the top bar) and click on the 'Contact the editor' link to send a message. Alternatively find their username within the network you both use, click on this to view their Mini-profile to 'Send message'. === i agree with Chuck and would add these commands for consideration on a windows box netstat -ano will show the pid of any java job which is tied to a tcp port likewise (on windows only): wmic process get /all /value is another win vista/win7/xp pro+ command which will show all the output from all pid's including the command line options or more specifically something like this: wmic process where commandline like '%java%' get commandline, processid hope this helps someone out there From: Caldarale, Charles R chuck.caldar...@unisys.com To: Tomcat Users List users@tomcat.apache.org Sent: Wed, December 2, 2009 9:32:18 AM Subject: RE: How to get java process id of a user running tomcat From: Pierre Goupil [mailto:goupilpie...@gmail.com] Subject: Re: How to get java process id of a user running tomcat jps -mlv will give you the PIDs of all running Java processes. Plus it's a part of the standard SUN JVM. But not for the OP, who is running an unsupported version of Tomcat on an unsupported JVM that predates the jps tool. As Pid suggested, the correct thing to do is to fix the webapp so it properly manages the threads it has started. Attack the problem, not the symptom. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. -- Kind regards * * * Webjam Customer Services Webjam - your social networks made easy www.webjam.com
Re: How to get java process id of a user running tomcat
Am Wed, 2 Dec 2009 12:00:06 +0530 schrieb raj kumar bprajkumar...@gmail.com: When i ran tomcat and shut it down my java process is not closing along with shutdown.i need to kill it explicitly. So I would like to BTW: How much memory is reserved for your Tomcat-JVM ($JAVA_OPTS) and how much memory has your server available? Regards, Tobias. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Https loadbalancing??
Chris, You're right - nice one. I'd always put in the extra properties into my connector config the proxyport , redirect port whether it was secure or not. but it works as you described if you don't tell it all the extra settings. Nice thanks D On 02/12/09 21:29, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David, On 11/25/2009 6:06 AM, David Cassidy wrote: If you want your tomcat to ever know that its getting a secure request you'll need 2 ajp connectors - one as the default is not secure the other needs to say i'm secure otherwise when you do a transport-guarantee in your web.xml your client will be in an infinite loop as tomcat never sees a secure request I call BS on this one: the AJP protocol can indicate whether a particular request is secure or not: the use of two AJP connectors is certainly not required. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksW3EsACgkQ9CaO5/Lv0PAN9wCfdXpMwAdvSiQRaWe0ptpDwogl o9AAoI4p/4P+4jKHS6lqlPpBoZmdXwo+ =kMRn -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Https loadbalancing??
It would be interesting if you are running on non-standard ports (ie not 80 and 443 ) to see what happens D On 03/12/09 13:40, David Cassidy wrote: Chris, You're right - nice one. I'd always put in the extra properties into my connector config the proxyport , redirect port whether it was secure or not. but it works as you described if you don't tell it all the extra settings. Nice thanks D On 02/12/09 21:29, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David, On 11/25/2009 6:06 AM, David Cassidy wrote: If you want your tomcat to ever know that its getting a secure request you'll need 2 ajp connectors - one as the default is not secure the other needs to say i'm secure otherwise when you do a transport-guarantee in your web.xml your client will be in an infinite loop as tomcat never sees a secure request I call BS on this one: the AJP protocol can indicate whether a particular request is secure or not: the use of two AJP connectors is certainly not required. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksW3EsACgkQ9CaO5/Lv0PAN9wCfdXpMwAdvSiQRaWe0ptpDwogl o9AAoI4p/4P+4jKHS6lqlPpBoZmdXwo+ =kMRn -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: IIS 6 Tomcat Connector isapi_redirect-1.2.28.dll not being called 404 2 1260 error
I was 2 days trying to make it working on my Windows 2003 server. Following the right minimum procedure: On my server (IIS 5.0) I've installed tomcat in D:\Program Files\Apache Software Foundation\Tomcat 6.0. Then I've downloaded isapi_redirect-1.2.28.dll. I've renamed it in isapi_redirect.dll and put in D:\Program Files\Apache Software Foundation\jakarta. Then I've inserted the following keys in the registry creating the following file .reg file: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta ISAPI Redirector\1.0] extension_uri=/jakarta/isapi_redirect.dll log_level=debug log_file=D:\\Program Files\\Apache Software Foundation\\Tomcat 6.0\\logs\\isapi_redirect.log worker_file=D:\\Program Files\\Apache Software Foundation\\Tomcat 6.0\\conf\\worker.properties worker_mount_file=D:\\Program Files\\Apache Software Foundation\\Tomcat 6.0\\conf\\uriworkermap.properties I created worker.properties in D:\Program Files\Apache Software Foundation\Tomcat 6.0\conf containing the following text: ps=\ worker.list=myworker worker.myworker.type=ajp13 worker.myworker.port=8009 worker.myworker.host=localhost I created uriworkermap.properties in D:\Program Files\Apache Software Foundation\Tomcat 6.0\conf containing the following text: #*Begin uriworkermap.properties* # #Simple worker configuration file # #Mount the Servlet context to the ajp13 worker # /Management/*=myworker Using the IIS management console, add a new virtual directory to your IIS web site. The name of the virtual directory must be jakarta. Its physical path should be the directory where you placed isapi_redirect.dll (in our example it is c:\tomcat\bin\win32\i386). While creating this new virtual directory assign it with execute access. Using the IIS management console, add isapi_redirect.dll as a filter in your IIS web site. The name of the filter should reflect its task (I use the name tomcat), its executable must be our D:\Program Files\Apache Software Foundation\jakarta\isapi_redirect.dll. Using the IIS management console, add the Jakarta Isapi Redirector to the Web Service Extensions. Right-click on Web Service Extensions and choose Add a new Web Service Extension. Enter tomcat for the Extension Name. Add the isapi_redirect.dll to the required files. Check the Set extension status to Allowed. Click on OK. Restart IIS (stop + start the IIS service), make sure that the tomcat filter is marked with a green up-pointing arrow. That's all, you should now start Tomcat and ask IIS to serve you the /examples context. Try http://localhost/examples/jsp/index.html for example and execute some of the JSP examples. FOREBACK Dianne wrote: Dear User Group: I cannot get IIS 6 to use the Tomcat connector to redirect requests. I followed the directions in http://tomcat.apache.org/connectors-doc/webserver_howto/iis.html configuring the registry by hand. This should be a relatively simple task but I am obviously overlooking something. The following environment is being used, Tomcat 6.0, JDK 6.0.18, JRE 1.6.0_13, Apache Tomcat Connectors isapi_redirect-1.2.28.dll which I downloaded and did not rebuild, IIS 6 on Windows Server 2003. I've triple checked the registry settings and can open every single directory. The isapi.log file is not being created. (It appears that the dll is not being called.) The filter does show as being loaded (green) with high priority. IIS log file gives a 404 error. Tomcat is working fine. The uriworkermap.properties contains the following entries and I've tried testing a .jsp example going through the IIS port. It does pull up when I use Tomcat directly. /localhost/examples/*=ajp13 /localhost/examples=ajp13 The workers.properties file contains worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 I've searched and am at a loss. Any help is very much appreciated. Thank you. This e-mail, and any files transmitted with it, may contain confidential and/or privileged material and is intended only for the person or entity to which it is addressed. If you are not the intended recipient, any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information is prohibited. If you have received this email in error, please notify the sender immediately and delete this material from all known records. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- View this message in context: http://old.nabble.com/IIS-6-Tomcat-Connector-isapi_redirect-1.2.28.dll-not-being-called-404-2-1260-error-tp23339494p26626849.html Sent from the Tomcat - User mailing list archive at Nabble.com.
Re: Tomcat Https loadbalancing??
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David, On 12/3/2009 8:42 AM, David Cassidy wrote: It would be interesting if you are running on non-standard ports (ie not 80 and 443 ) to see what happens I do that, and it works just fine. AJP doesn't use the proxyPort stuff because the HTTP port isn't being changed. All that is necessary if you are using mod_proxy_http because the HTTP port often changes between Apache httpd (listening on port 80 to the outside world) and Tomcat (listening to, say, 8080 only to the internal network). In this case, Tomcat is convinced that the real port number being used is 8080 and would return URLs to the client using :8080 appended to them. Without using proxyName and proxyPort, Tomcat might return bad URLs to the user. The 'secure' attribute is necessary, here, if you are terminating SSL somewhere else but still consider the (non-encrypted) HTTP connection going to Tomcat to be secure. The AJP connector does in fact have proxyName and proxyPort attributes available, but I believe they are either superfluous, or auto-filled by the incoming HTTP request, anyway. In both cases, the default redirectPort is 443. I think if you are using HTTP connectors, your claim is true: to support both secure and non-secure channels where both channels are actually non-secure HTTP, you'll need two Connectors: one with secure=true and one with secure=false (or unspecified, and it defaults to false). - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksXzfYACgkQ9CaO5/Lv0PAGYwCgkwzr/s+M50PG1qnXDECwcZdq HK8An0chpHBpxTMpi5awXScqpAtR5OHk =GWlN -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
[ANN] PSI Probe: A community-driven fork of Lambda Probe
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, (Apologies if this has been announced before; I couldn't find any mention of it in the archives. It's not even my project, so who am I to be announcing it?) I found this while looking around this morning: http://code.google.com/p/psi-probe/ They don't appear to have any more recent releases than Lambda Probe did (their current version is 1.7b which matches the last release of Lambda Probe... it seems reasonable that they'd keep the version number in-line with the past project), but at least is looks like there is some activity. Anyone who wants to lend a hand should head on over and volunteer. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksX0Y8ACgkQ9CaO5/Lv0PDrkwCghdTDk1Qmh/JWJYBPmCz9nqmo 3XgAn2g2/KBFNsKHA5Fly+dDpzMGMPx2 =Zojh -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Manage log files in a cluster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paolo, On 12/1/2009 11:37 AM, Paolo Santarsiero wrote: Hi, I have a cluster with many tomcat and I want to manage the log's files on a centralized basis in order to collect, display, analyze and manage all files of logs from a single client. Do you know a system that allows me to do? Many thanks. Another option would be to use log4j as your logging system (which Tomcat supports, with a bit of work) and use the SyslogAppender to send your log messages to syslog. Syslog already includes the ability for remote logging, aggregating, etc. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksX0uoACgkQ9CaO5/Lv0PArlwCgrfc9xlBUQFgCvM69EQwFgbkY 8C8An2TMKcnzLNcn+FIozWHZCDh782j/ =uGan -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Schema or DTD for the context.xml
Is there a schema or DTD for the context.xml file? Thanks, Lance Campbell Project Manager/Software Architect/DBA Web Services at Public Affairs 217-333-0382
Re: Schema or DTD for the context.xml
On 03/12/2009 15:43, Campbell, Lance wrote: Is there a schema or DTD for the context.xml file? Nope. It's possible to use custom classes for various parts of Tomcat's internals, each of which may utilise custom attributes as specified by the author. Thus a schema becomes problematic to write. The best guide, (as ever), is the docs: http://tomcat.apache.org/tomcat-6.0-doc/config/context.html p Thanks, Lance Campbell Project Manager/Software Architect/DBA Web Services at Public Affairs 217-333-0382 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
mod_jk socket_timeout setting
I'm using apache 2.2.11, mod_jk 1.2.28, and jboss as my application server. I wrote an Apache module which worked fine in my local environment. When I moved to integration though I saw a 502 error. The cause appeared to be that the socket_timeout setting for the workers was set to 2. My co-worker and I are disagreeing over what the socket_timeout directive does. I used wireshark and it looked like the actual body response had to come back within that certain time. If it didn't then a retry was done. If the body response still didn't come back then the 502 appeared. My co-worker says though that the socket_timeout directive is only for the tcp handshake. It looked like to me it actually was for the body response. Can someone please verify what that directive does? Thank you for your time, Dan
RE: How to get java process id of a user running tomcat
Hi Me being the one who made the ridiculous suggestion of using ps, am now enlightened and will be using jps -mlv and spreading the word... That being said is there any opinions about the soundness of using the Redhat/Centos startup/shutdown script for Tomcat? Regards -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: 02 December 2009 20:40 To: Tomcat Users List Subject: Re: How to get java process id of a user running tomcat -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Phani, On 12/2/2009 1:30 AM, raj kumar wrote: When i ran tomcat and shut it down my java process is not closing along with shutdown. See others' responses for why you should have to do this. Otherwise... i need to kill it explicitly. So I would like to know how to identify the java process of the logged in user who started the server. so that i can kill the process id from the shutdown.sh script itself. You won't be using the shutdown.sh script to kill Tomcat unless you hack it up to do that. I'd recommend against that. What I would recommend is using the CATALINA_PID environment variable helpfully documented in bin/catalina.sh: # Environment Variable Prequisites [...] # CATALINA_PID(Optional) Path of the file which should contains # the pid of catalina startup java process, when # start (fork) is used Try setting this environment variable to something like /var/run/tomcat.pid and you should get a file in that location containing the pid of the Java process started by Tomcat. Then, you can do something like: $ kill -9 `cat /var/run/tomcat.pid` Forget all these ridiculous suggestions of running 'ps' and grepping the output for all kinds of crazy strings. That may or may not work at all. The above strategy was intended by the Tomcat developers to be used to capture the PID of the Java process, so go ahead and use that. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksW0KwACgkQ9CaO5/Lv0PA7uQCgxBiy3snTbF49e8FXPp/+qARn qncAoI4/CLEItiHOiZxCioRfpHcCiGZ5 =AP2a -END PGP SIGNATURE- __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
Re: How to get java process id of a user running tomcat
On 03/12/2009 17:09, gerhardus.geldenh...@gta-travel.com wrote: Hi Me being the one who made the ridiculous suggestion of using ps, am now enlightened and will be using jps -mlv and spreading the word... That being said is there any opinions about the soundness of using the Redhat/Centos startup/shutdown script for Tomcat? No idea how it works, but presumably it was written to shutdown the server, ergo it should be reasonable to use it as intended. If Tomcat doesn't stop, find out why. p Regards -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: 02 December 2009 20:40 To: Tomcat Users List Subject: Re: How to get java process id of a user running tomcat -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Phani, On 12/2/2009 1:30 AM, raj kumar wrote: When i ran tomcat and shut it down my java process is not closing along with shutdown. See others' responses for why you should have to do this. Otherwise... i need to kill it explicitly. So I would like to know how to identify the java process of the logged in user who started the server. so that i can kill the process id from the shutdown.sh script itself. You won't be using the shutdown.sh script to kill Tomcat unless you hack it up to do that. I'd recommend against that. What I would recommend is using the CATALINA_PID environment variable helpfully documented in bin/catalina.sh: # Environment Variable Prequisites [...] # CATALINA_PID(Optional) Path of the file which should contains # the pid of catalina startup java process, when # start (fork) is used Try setting this environment variable to something like /var/run/tomcat.pid and you should get a file in that location containing the pid of the Java process started by Tomcat. Then, you can do something like: $ kill -9 `cat /var/run/tomcat.pid` Forget all these ridiculous suggestions of running 'ps' and grepping the output for all kinds of crazy strings. That may or may not work at all. The above strategy was intended by the Tomcat developers to be used to capture the PID of the Java process, so go ahead and use that. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksW0KwACgkQ9CaO5/Lv0PA7uQCgxBiy3snTbF49e8FXPp/+qARn qncAoI4/CLEItiHOiZxCioRfpHcCiGZ5 =AP2a -END PGP SIGNATURE- __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: How to get java process id of a user running tomcat
Thanks for the reply, Out of interest the man page for jps states: NOTE: This utility is unsupported and may not be available in future versions of the JDK. It is not currently available on Windows 98 and Windows ME platforms. This might just be a entry that has not been removed... and the utility is supported... and available in future versions. -Original Message- From: Pid [mailto:p...@pidster.com] Sent: 03 December 2009 17:37 To: users@tomcat.apache.org Subject: Re: How to get java process id of a user running tomcat On 03/12/2009 17:09, gerhardus.geldenh...@gta-travel.com wrote: Hi Me being the one who made the ridiculous suggestion of using ps, am now enlightened and will be using jps -mlv and spreading the word... That being said is there any opinions about the soundness of using the Redhat/Centos startup/shutdown script for Tomcat? No idea how it works, but presumably it was written to shutdown the server, ergo it should be reasonable to use it as intended. If Tomcat doesn't stop, find out why. p __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
RE: mod_jk socket_timeout setting
From: dan lahey [mailto:dlahey...@gmail.com] Subject: mod_jk socket_timeout setting I used wireshark and it looked like the actual body response had to come back within that certain time. My co-worker says though that the socket_timeout directive is only for the tcp handshake. Unlikely, since that's pretty much invisible to user code. Can someone please verify what that directive does? I can't really answer that, but I can quote previous responses from Rainer: Don't use socket_timeout. Use version 1.2.28 and socket_connect_timeout. http://marc.info/?l=tomcat-userm=125897176719328w=2 More information: http://marc.info/?l=tomcat-userm=125675257720614w=2 And more detail: socket_timeout is a difficult beast and I generally do not recommend using it. mod_jk uses it in some special situations in order to be able to abort waiting for data. It is not directly 'how long a socket will be kept open'. How long a socket is kept open depends on how the socket gets used. Usually you can get away pretty good using CPing and ping_timeout, socket_connect_timeout, eventually reply_timeout with max_reply_timeouts. http://marc.info/?l=tomcat-userm=125663788907668w=2 - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: How to get java process id of a user running tomcat
From: gerhardus.geldenh...@gta-travel.com [mailto:gerhardus.geldenh...@gta-travel.com] Subject: RE: How to get java process id of a user running tomcat Out of interest the man page for jps states: NOTE: This utility is unsupported and may not be available in future versions of the JDK. That disclaimer is present on pretty much every JDK tool that Sun provides, other than those absolutely required for development, such as javac. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
Re: How to get java process id of a user running tomcat
gerhardus.geldenh...@gta-travel.com wrote: Thanks for the reply, Out of interest the man page for jps states: NOTE: This utility is unsupported and may not be available in future versions of the JDK. It is not currently available on Windows 98 and Windows ME platforms. This might just be a entry that has not been removed... and the utility is supported... and available in future versions. Note the key word may, instead of will. They're just saying they aren't promising to give it to you in the future; they aren't saying they won't. D - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to get java process id of a user running tomcat
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gerhardus, On 12/3/2009 12:09 PM, gerhardus.geldenh...@gta-travel.com wrote: Me being the one who made the ridiculous suggestion of using ps, am now enlightened and will be using jps -mlv and spreading the word... I would still use CATALINA_PID and not use any kind of process listing along with pattern matching. You're bound to miss cases and kill the wrong process(es). That being said is there any opinions about the soundness of using the Redhat/Centos startup/shutdown script for Tomcat? If you are using a package-managed version of Tomcat, using their scripts would seem to be essential. Hopefully, those package-managed scripts ultimately call Tomcat's built-in scripts to be as compatible as possible. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksYGf8ACgkQ9CaO5/Lv0PBmgACgwwi78qECCPUUH8eSzwzvkb7V Gw0Ani1Yc8pO60wb4l4OydFje67EF0Lh =XuDH -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6 and Apache2 VS Tomcat 6 alone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter, Since my ears (eyes?) are burning... On 11/24/2009 6:09 AM, Peter Crowther wrote: 2009/11/24 TheGrailer ken...@gmail.com: The most compelling argument from the Apache2 and Tomcat 6-friend was indeed the static content part. http://tomcat.markmail.org/message/il33wqqjb2dok6xz might be illuminating - along with the discussion around it on that thread. I suspect Chris will be making his own comments on this thread, as he knows his benchmarking results better than anyone! Yes, I'm getting ready to get back into that benchmarking... that field has laid fallow for quite a while and I just freed-up a dev server to do some testing, so I'm basically formalizing everything, properly documenting it so that my tests can easily be repeated, and upgrading to Tomcat 6.0.20 for all testing, etc. Anyhow, the upshot from all the testing I've done is that if you are using small files ( 32KiB), all connectors (in Tomcat) in all configurations perform about the same: this includes using Tomcat-native (aka APR, which is the httpd code mentioned elsewhere). If the argument is that httpd is faster by definition, then using the APR connector with Tomcat ought to be just as fast, so you get no discernible performance boost by using httpd out front. My data has httpd versus Tomcat+APR+sendFile in a dead heat for nearly all file sizes, with Tomcat+APR winning at certain points, losing at others. I suspect this is just noisy data that can be attributed to a cron job or two running during the tests. If you want my advice, use the APR Connector and make sure you specify sendFile=true and you'll be able to prove your httpd fanboy wrong. :) - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksYHVgACgkQ9CaO5/Lv0PDnWwCgrGi12feuuHICV0QB8TGDg7aG ppsAniVmIsuzEHDPOD6LlqJlVi/vHkRE =OANy -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Performance Problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter, On 11/20/2009 5:32 AM, Peter Crowther wrote: Why are they in the Session rather than anywhere else? Why do they exist at all? To improve performance, of course! - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksYHtcACgkQ9CaO5/Lv0PAIygCdHvfJ5y/bxrIXkmNiVSmiQdUh LEIAn0j4KR5U6YSEII8VsPUAS0/hzy9/ =/xSs -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Migrating from Tomcat 5.5.25 to 6.0.22
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris, On 11/19/2009 3:10 PM, Christopher Gross wrote: The machine that I run Tomcat on isn't on the internet, and it isn't a local machine. I can try to copy it over again, it will just take some time to do that. If there are other methods that may work, I'd like to try them first. Unfortunately, it looks like you have broken your installation and it would be best to start over fresh. Note that copying your old conf/server.xml from 5.5.25 into conf/server.xml in your new TC 6.0.20 install wil likely lead to problems (it certainly did for me when I gave it a shot just now). Instead, start with the stock server.xml (and maybe make a backup copy just in case) and merge-in any changes you actually need from your old server.xml file. You may find that all you need to do is change the Connector configuration and leave everything else alone. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksYH84ACgkQ9CaO5/Lv0PABBwCcD36RoUlPxQeUZs0DgOh41IPj 9HEAoLiqjZzYRpM0IU/K6Z9IFRLV8CC0 =BfhI -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: cluster deployment by context descriptors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paolo, On 11/20/2009 5:36 AM, Paolo Santarsiero wrote: So I must configure vhost under apache for a specific webapp and then create context descriptor for specific tomcats under default host (ex. under tom1 and tom2 and not under tom3). Or must I create vhost under specific tomcats too? No, you just have to use different load-balancing configurations for each set of webapps you want to deploy differently. Let's say you have 2 webapps: A and B. Let's say you have 6 app servers: 1, 2, 3, 4, 5, and 6. Let's say you have the following deployments: Server Webapps 1 A 2 B 3 A 4 B 5 A, B 6 A, B You will want to set up your workers to load balance webapp A separately from webapp B, maybe like this: workers.properties - -- worker.list=lbA, lbB worker.lbA.type=lb worker.lbA.balance_workers=server1, server3, server5, server6 worker.lbB.type=lb worker.lbB.balance_workers=server2, server4, server5, server6 // now, configure the serverX workers in some obvious way httpd.conf - -- JkMount /webappA|/* lbA JkMount /webappB|/* lbB This should protect you from sending your requests to the wrong server. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksYKZwACgkQ9CaO5/Lv0PAptACgmd+CBgY6Ku0/X21q7TtepHTY X24AoIEiPy6MvmJWNIUq1I/yjZ91qBSp =73aU -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Https loadbalancing??
Some of this is also explained in http://tomcat.apache.org/connectors-doc/generic_howto/proxy.html On 03.12.2009 15:40, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David, On 12/3/2009 8:42 AM, David Cassidy wrote: It would be interesting if you are running on non-standard ports (ie not 80 and 443 ) to see what happens I do that, and it works just fine. AJP doesn't use the proxyPort stuff because the HTTP port isn't being changed. All that is necessary if you are using mod_proxy_http because the HTTP port often changes between Apache httpd (listening on port 80 to the outside world) and Tomcat (listening to, say, 8080 only to the internal network). In this case, Tomcat is convinced that the real port number being used is 8080 and would return URLs to the client using :8080 appended to them. Without using proxyName and proxyPort, Tomcat might return bad URLs to the user. The 'secure' attribute is necessary, here, if you are terminating SSL somewhere else but still consider the (non-encrypted) HTTP connection going to Tomcat to be secure. The AJP connector does in fact have proxyName and proxyPort attributes available, but I believe they are either superfluous, or auto-filled by the incoming HTTP request, anyway. In both cases, the default redirectPort is 443. I think if you are using HTTP connectors, your claim is true: to support both secure and non-secure channels where both channels are actually non-secure HTTP, you'll need twoConnectors: one with secure=true and one with secure=false (or unspecified, and it defaults to false). - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksXzfYACgkQ9CaO5/Lv0PAGYwCgkwzr/s+M50PG1qnXDECwcZdq HK8An0chpHBpxTMpi5awXScqpAtR5OHk =GWlN -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
tomcat6 + php
Hi What is the recommended way of using php with tomcat6. is it better to use Apache for the static/php pages or can we just use tomcat? currently we have different web sites on different servers (runing tomcat 5.5) as we are looking at moving to tomcat6 I would like to combine these.. cheers Stephen - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: tomcat6 + php
From: newsletter [mailto:newslet...@energyts.com] Subject: tomcat6 + php What is the recommended way of using php with tomcat6. is it better to use Apache for the static/php pages or can we just use tomcat? Tomcat will handle static pages perfectly well. As far as PHP goes, we've had good results (sorry, can't quantify that) using Quercus: http://wiki.caucho.com/Quercus:_Tomcat Whether or not that's sufficient for your use of PHP is up to you to decide. Using httpd for PHP certainly has a strong track record. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 5 vs 6 Context useNaming Behavior
We have a legacy application that's been running on the 5.5.X versions for several years. This application manipulates the JNDI context in such a manner that would now be considered unusual. In a nutshell, it's because the application framework was written concurrent with and prior to development of current standards. The application instantiates the context, creates and binds it's own JDBC pool, etc. with no relevant edits to any of Tomcat's configuration files. As long as useNaming is set to false for the Context in 5.5.X, this works splendidly. In 6.0.20, no matter the setting (true/false), we get the same Exception as when useNaming is set to true in 5.5.X: javax.naming.NamingException: Name comp is not bound in this Context Relevant snippet: System.setProperty(java.naming.factory.initial, com.telesoft.naming.BasicInitCtxFactory); Context context = new InitialContext(); context.rebind(java:comp/env/appName,this.appName); Is there a known/related useNaming bug or have I missed some new configuration nugget? Many thanks in advance. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 5 vs 6 Context useNaming Behavior
From: Scott Dudley [mailto:sc...@telesoft.com] Subject: Tomcat 5 vs 6 Context useNaming Behavior We have a legacy application that's been running on the 5.5.X versions for several years. Under what JVM? And platform? The application instantiates the context, creates and binds it's own JDBC pool, etc. with no relevant edits to any of Tomcat's configuration files. What does it do with exceptions during the context instantiation? In 6.0.20, no matter the setting (true/false), we get the same Exception as when useNaming is set to true in 5.5.X: What JVM for 6.0.20? Is there a known/related useNaming bug or have I missed some new configuration nugget? Can't say. Can you post your server.xml and relevant Context element? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [Solved+Question]SessionListener not being invoked
Chris, This seems to be the source of the problem. Just to be sure I'm on target, I'll run through a few details, and then I have a follow-on question. My tomcat-6.0.20/ conf/context.xml is the one shipped with the download: Context !-- Default set of monitored resources -- WatchedResourceWEB-INF/web.xml/WatchedResource !-- Uncomment this to disable session persistence across Tomcat restarts -- !-- Manager pathname= / -- !-- Uncomment this to enable Comet connection tacking (provides events on session expiration as well as webapp lifecycle) -- !-- Valve className=org.apache.catalina.valves.CometConnectionManagerValve / -- /Context And the app-specific context doesn't say anything about Manager: Context path= debug=5 reloadable=true crossContext=true Resource name=jdbc/sb_data auth=Container type=javax.sql.DataSource maxActive=100 maxIdle=30 maxWait=1 username=X password=X driverClassName=com.mysql.jdbc.Driver url=jdbc:mysql://localhost:3306/sb_data validationQuery=select 1/ /Context So I understand http://tomcat.apache.org/tomcat-6.0-doc/config/manager.html : A Manager element MAY be nested inside a Context component. If it is not included, a default Manager configuration will be created automatically, which is sufficient for most requirements. to say that the app will get a default Manager, which is the Standard Implementation: Tomcat provides two standard implementations of Manager for use - the default one stores active sessions In addition, under the Standard Implementation pathname attribute, I found: Absolute or relative (to the work directory for this Context) pathname of the file in which session state will be preserved across application restarts, if possible. The default is SESSIONS.ser. Poking around, I found SESSIONS.ser in ~work/Catalina/localhost/ strongbrain. Being naturally short-tempered and brutish, I simply deleted ~work/Catalina/localhost/ , and restarted Tomcat. Then when I connected to the app with a browser, I got the desired: INFO: Server startup in 3728 ms Enter sessionCreated +SessionListener: isNew=true baseprefix=/strongbrain/ configBean.bp=/strongbrain/ Great! So now the question is this: Is the simplest principled, patient, and gentle way of suppressing session persistence for my particular app to add the following Manager config element to my webapp's context.xml? Manager pathname= / And if I wanted all apps to suppress persistence, then I would just uncomment that in ~conf/context.xml. Many thanks! Ken Bowen On Dec 2, 2009, at 12:31 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ken, On 12/1/2009 2:36 PM, Ken Bowen wrote: No, we always create a session (or want to). The only %@ in the welcome page are %@ page contentType=text/html;charset=UTF-8 language=java % %@ taglib uri=http://tiles.apache.org/tags-tiles; prefix=tiles % %@ taglib uri=http://java.sun.com/jstl/core_rt; prefix=c % As I mentioned at the end of the initial email, this all works (i.e., as session is created) when I run the same welcome page with the same SessionListener and the indicated change to the context-param ; and run it as webapps/strongbrain/ instead of webapps/ROOT. That's what's so mysterious. Obviously, something else is being changed too. But sessions have never been optional in this app. I didn't quite understand your original report, but is it possible that one of these clients already has a valid session and therefore a new one isn't being created? That might be possible, even after a webapp/container restart if you have Tomcat configured to persist sessions across such restarts (which is the default configuration). - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksWpHgACgkQ9CaO5/Lv0PBaUQCfbcuQ+bgTQKudElNSi0i9Y8eX x1wAoKyA9rQPGuJ5AzFw0GIvuHhJt7X8 =gOgm -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: [Solved+Question]SessionListener not being invoked
From: Ken Bowen [mailto:kbo...@als.com] Subject: Re: [Solved+Question]SessionListener not being invoked Context path= debug=5 reloadable=true crossContext=true Note that the path attribute is not allowed (if your Context element is in a standard location), and the debug attribute hasn't been used in some years. Use conf/logging.properties to set the desired logging level. Is the simplest principled, patient, and gentle way of suppressing session persistence for my particular app to add the following Manager config element to my webapp's context.xml? Manager pathname= / Yes, that is the documented and recommended way: Restart persistence may be disabled by setting this attribute to an empty string. The above quote is taken from: http://tomcat.apache.org/tomcat-6.0-doc/config/manager.html And if I wanted all apps to suppress persistence, then I would just uncomment that in ~conf/context.xml. Also true. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [Solved+Question]SessionListener not being invoked
Thanks Chuck. One question: What does it mean to say the path attribute is not allowed? (My context.xml is in META-INF). Should I be seeing a complaint when Tomcat starts the app? --Ken On Dec 3, 2009, at 10:42 PM, Caldarale, Charles R wrote: From: Ken Bowen [mailto:kbo...@als.com] Subject: Re: [Solved+Question]SessionListener not being invoked Context path= debug=5 reloadable=true crossContext=true Note that the path attribute is not allowed (if your Context element is in a standard location), and the debug attribute hasn't been used in some years. Use conf/logging.properties to set the desired logging level. Is the simplest principled, patient, and gentle way of suppressing session persistence for my particular app to add the following Manager config element to my webapp's context.xml? Manager pathname= / Yes, that is the documented and recommended way: Restart persistence may be disabled by setting this attribute to an empty string. The above quote is taken from: http://tomcat.apache.org/tomcat-6.0-doc/config/manager.html And if I wanted all apps to suppress persistence, then I would just uncomment that in ~conf/context.xml. Also true. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: [Solved+Question]SessionListener not being invoked
From: Ken Bowen [mailto:kbo...@als.com] Subject: Re: [Solved+Question]SessionListener not being invoked One question: What does it mean to say the path attribute is not allowed? (My context.xml is in META-INF). Should I be seeing a complaint when Tomcat starts the app? Unfortunately, Tomcat won't complain about it (although I think it should). The path attribute is only valid when the Context element is nested inside of a Host element in conf/server.xml - which is very strongly discouraged. Using a path attribute in any other circumstance is not permitted, but not diagnosed. At best, it will confuse anyone looking at your configuration, possibly thinking that something meaningful is being done with it. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [Solved+Question]SessionListener not being invoked
Thanks. This project has been sputtering along for a fair number of years, and my context.xml almost certainly began life inside conf/ server.xml. I would be fairly confident in betting that I moved it out on earlier advice from you, but that I didn't clean it up then. Well, I have now. Cheers, Ken On Dec 3, 2009, at 11:02 PM, Caldarale, Charles R wrote: From: Ken Bowen [mailto:kbo...@als.com] Subject: Re: [Solved+Question]SessionListener not being invoked One question: What does it mean to say the path attribute is not allowed? (My context.xml is in META-INF). Should I be seeing a complaint when Tomcat starts the app? Unfortunately, Tomcat won't complain about it (although I think it should). The path attribute is only valid when the Context element is nested inside of a Host element in conf/server.xml - which is very strongly discouraged. Using a path attribute in any other circumstance is not permitted, but not diagnosed. At best, it will confuse anyone looking at your configuration, possibly thinking that something meaningful is being done with it. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: [Solved+Question]SessionListener not being invoked
From: Ken Bowen [mailto:kbo...@als.com] Subject: Re: [Solved+Question]SessionListener not being invoked This project has been sputtering along for a fair number of years, and my context.xml almost certainly began life inside conf/server.xml. Once upon a time, I believe Context elements had to be in server.xml, but that predates my Tomcat experience. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [Solved+Question]SessionListener not being invoked
Caldarale, Charles R wrote: From: Ken Bowen [mailto:kbo...@als.com] Subject: Re: [Solved+Question]SessionListener not being invoked This project has been sputtering along for a fair number of years, and my context.xml almost certainly began life inside conf/server.xml. Once upon a time, I believe Context elements had to be in server.xml, but that predates my Tomcat experience. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. Tomcat 3 did it that way. I think the idea of moving the context elements out to their own file started in tomcat 4 but that was a long time ago and my memory is a little fuzzy. --David - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
