Re: public_html config not working
Caldarale, Charles R wrote: From: Aryeh Friedman [mailto:aryeh.fried...@gmail.com] Subject: public_html config not working I took following from cutting and pasting from O'Reilly's Defenative Tomcat and put it inside each of my virtual hosts (as shown the default Host) and then I get resource unavaible for any request to ~user but the rest of the (virtual) host works: http://www.catb.org/~esr/faqs/smart-questions.html At the bare minimum, tell us the Tomcat version you're using, the JVM it's running on, and the platform - we're not mind readers. If you tried the above on Windows, it will certainly fail. The real doc for that feature of the current Tomcat version is here: http://tomcat.apache.org/tomcat-6.0-doc/config/host.html#User%20Web%20Applications Tomcat 6.0.20, JDK 1.6 update 3 (with FreeBSD patch 4), FreeBSD 7.2-RELEASEpl1 (development machine) and 8.0-RELEASE (production machine) I also forgot to note I had it working fine on localhost but it seems to not like virtual hosts - 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: Tomcat dies suddenly
> From: fatzopilot [mailto:fatzopi...@gmx.net] > Subject: Re: Tomcat dies suddenly > > Before that, my tomcat died several times without throwing any error > because of a lack of physical memory. Was this because of the infamous Linux OOM killer? Were there any system log entries? If so, where? - 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: Tomcat dies suddenly
It does not relate to your problem (and probably won't solve it) but I just wanted to point out that I made good experiences using -XX:+UseCompressedOops on 64bit systems to reduce bloat which might be another issue in your case. It kept the memory footprint about 30% lower. Before that, my tomcat died several times without throwing any error because of a lack of physical memory. -- View this message in context: http://old.nabble.com/Tomcat-dies-suddenly-tp27377457p27386307.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat on Ubuntu 8.04 VPS and presumably multiple socket problems
Rainer, Thanks for clarification. There are a lot of misleading configuration 'tweaks' roaming around which do not seem to have any effect (or at least not in recent versions). The minimal config now works well for me. Cheers fatzopilot Rainer Jung-3 wrote: > > On 30.01.2010 17:41, fatzopilot wrote: >>> 2nd issue: mod_jk does not work. I think I replayed multiple >>> instructions >>> to >>> set it up multiple times but in all cases it finally says "Could not >>> find >>> a >>> worker for worker name=myWorker" >> >> Solved by using the procedure described here (till item 11): >> http://ubuntuforums.org/showthread.php?t=971517 >> >> I now use (for worker.properties): >> workers.tomcat_home=/usr/share/tomcat5.5 > > This attribute doesn't do anything, the line can be deleted. > >> workers.java_home=/usr/lib/jvm/java-1.5.0-sun > > This attribute doesn't do anything, the line can be deleted. > >> ps=/ > > This attribute doesn't do anything, the line can be deleted. > >> worker.list=myWorker >> worker.myWorker.port=8009 >> worker.myWorker.host=localhost >> worker.myWorker.type=ajp13 >> worker.myWorker.lbfactor=1 > > OK, ver ybasic but should work. > >> which before was >> workers.list=myWorker,ajp13 >> workers.myWorker.type=ajp13 >> workers.myWorker.host=localhost >> workers.myWorker.port=8009 > > The problem was the plural "workers", which was wrong. After fixing this > your original configuration should have worked, at least after dropping > the non-defined worker "ajp13" from worker.list. > > Regards, > > Rainer > > - > 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/Tomcat-on-Ubuntu-8.04-VPS-and-presumably-multiple-socket-problems-tp27332135p27386170.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dies suddenly
George, Thanks for your reply. I will check that IPV6 is disabled... can't remember for certain. I have had the problem on both openSuse and Slackware which has lead me to believe the problem is in the JVM. I guess I could try compiling the JVM from source on the target machine. I ran memTest86 for 30 hours on the first server I encountered the problem with (the first server with Slackware and 64 bit java that I brought up) and nothing showed up. I then, redid that machine with openSuse (thought the problem might be Slackware) but openSuse failed as quickly. Thanks, Carl - Original Message - From: "George Sexton" To: "'Tomcat Users List'" Sent: Saturday, January 30, 2010 11:46 AM Subject: RE: Tomcat dies suddenly I've had this happen. Finally, I got a stack trace. In my case, there appears to be a bug in GLIBC, so when a reverse IP address lookup is done AND there is an IPV6 entry, it causes a problem. The solution appeared to be disabling IPV6 since I'm not using it. This is on OpenSuSE. It would be worth checking. You might also run MemTest86+ on it if you haven't already. George Sexton MH Software, Inc. http://www.mhsoftware.com/ Voice: 303 438 9585 -Original Message- From: Carl [mailto:c...@etrak-plus.com] Sent: Friday, January 29, 2010 12:54 PM To: Tomcat Users List Subject: Tomcat dies suddenly 6-7 weeks ago, we built up some new servers and started having sudden failures... Tomcat just stops with no error message, no system error messages, nothing that I have been able to find so far. To refresh everyone's memory, this is a new server, a Dell T110 with a Xeon 3440 processor and 4GB memory. I have turned off both the turbo mode and hyperthreading. The environment: 64 bit Slackware Linux java version "1.6.0_17" Java(TM) SE Runtime Environment (build 1.6.0_17-b04) Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode) Tomcat: apache-tomcat-6.0.20 These are the current JAVA_OPTS="-Xms1024m -Xmx1024m -XX:PermSize=368m -XX:MaxPermSize=368m" I have observed the memory usage and general performance with Java VisualVM and have seen nothing strange. I thought I was seeing GC as memory usage was going up and down but in fact it was mostly people coming onto the system and leaving it. After several hours, the memory settles to a baseline of about 375MB. Forced GC never takes it below that value and the ups and downs from the people coming onto and leaving the system also returns it to pretty much that value. The maximum memory used never was above 700MB for the entire day. The server runs well, idling along at 2-5% load, except for a quick spike during GC, serving jsp's, etc. at a reasonable speed. Without warning and with no tracks in any log (Tomcat or system) or to the console, Tomcat just shuts down. I can usually simply restart it as the ports used by Tomcat are closed... today, I needed to run shutdown.sh before I could run startup.sh (startup.sh gave no errors but would not start Tomcat until I ran shutdown.sh and that process put nothing in the logs... this is the first time this has happened.) Sometimes, the system will run for a week, sometimes for only several hours, sometimes only for a few minutes. Today, it ran until about 1:00PM and has been down four times since then. The failure (Tomcat shutting down) is not always the same place in the code (I have some debugging messages going to catalina.out.) Load does not seem to make a difference. I have tried another sever (Dell T105, AMD processor, 6GB memory) and have observed the same results. I have run memTest86 on the T110 for about 30 hours and it showed nothing. I rebuilt the T110 with SUSE linux, Java 1.6.18 and Tomcat 6.0.24... it lasted 15 minutes. I have used the same server.xml on all the installs: When Tomcat shuts down, the memory that it was using seems to still be held (as seen from top) but it is nowhere near the machine physical memory. The application has been running on an older server (Dell 600SC, 32 bit Slackware, 2GB memory) for several years and, while the application will throw exceptions now and then, it never crashed. This lead me to believe the problem had something to do with the 64 bit JVM but, with without seeing errors anywhere, I can't be certain and don't know what I can do about it except go back to 32 bit. One time, I observed the heap and permGen memory usage with Visual JVM. It was running around 600MB before I forced a GC and 375MB afterward. Speed was good. Memory usage from top was 2.4GB. Five minutes later, Tomcat stopped leaving no tracks that I could find. The memory usage from top was around 2.4GB. The memory usage from Visual JVM was still showing 400MB+ although the Tomcat process was gone. I restarted Tomcat (did not reboot) so Tomcat had been shutdown gracefully enough to close the ports (8080, 8443, 443.) Tomcat sta
Re: Tomcat on Ubuntu 8.04 VPS and presumably multiple socket problems
On 30.01.2010 17:41, fatzopilot wrote: 2nd issue: mod_jk does not work. I think I replayed multiple instructions to set it up multiple times but in all cases it finally says "Could not find a worker for worker name=myWorker" Solved by using the procedure described here (till item 11): http://ubuntuforums.org/showthread.php?t=971517 I now use (for worker.properties): workers.tomcat_home=/usr/share/tomcat5.5 This attribute doesn't do anything, the line can be deleted. workers.java_home=/usr/lib/jvm/java-1.5.0-sun This attribute doesn't do anything, the line can be deleted. ps=/ This attribute doesn't do anything, the line can be deleted. worker.list=myWorker worker.myWorker.port=8009 worker.myWorker.host=localhost worker.myWorker.type=ajp13 worker.myWorker.lbfactor=1 OK, ver ybasic but should work. which before was workers.list=myWorker,ajp13 workers.myWorker.type=ajp13 workers.myWorker.host=localhost workers.myWorker.port=8009 The problem was the plural "workers", which was wrong. After fixing this your original configuration should have worked, at least after dropping the non-defined worker "ajp13" from worker.list. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: public_html config not working
> From: Aryeh Friedman [mailto:aryeh.fried...@gmail.com] > Subject: public_html config not working > > I took following from cutting and pasting from O'Reilly's Defenative > Tomcat and put it inside each of my virtual hosts (as shown the > default Host) and then I get resource unavaible for any request to > ~user but the rest of the (virtual) host works: > > directoryName="public_html" > userClass="org.apache.catalina.startup.PasswdUserDatabase"> > http://www.catb.org/~esr/faqs/smart-questions.html At the bare minimum, tell us the Tomcat version you're using, the JVM it's running on, and the platform - we're not mind readers. If you tried the above on Windows, it will certainly fail. The real doc for that feature of the current Tomcat version is here: http://tomcat.apache.org/tomcat-6.0-doc/config/host.html#User%20Web%20Applications - 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: Tomcat dies suddenly
I've had this happen. Finally, I got a stack trace. In my case, there appears to be a bug in GLIBC, so when a reverse IP address lookup is done AND there is an IPV6 entry, it causes a problem. The solution appeared to be disabling IPV6 since I'm not using it. This is on OpenSuSE. It would be worth checking. You might also run MemTest86+ on it if you haven't already. George Sexton MH Software, Inc. http://www.mhsoftware.com/ Voice: 303 438 9585 > -Original Message- > From: Carl [mailto:c...@etrak-plus.com] > Sent: Friday, January 29, 2010 12:54 PM > To: Tomcat Users List > Subject: Tomcat dies suddenly > > 6-7 weeks ago, we built up some new servers and started having sudden > failures... Tomcat just stops with no error message, no system error > messages, nothing that I have been able to find so far. > > To refresh everyone's memory, this is a new server, a Dell T110 with a > Xeon 3440 processor and 4GB memory. I have turned off both the turbo > mode and hyperthreading. > > The environment: > > 64 bit Slackware Linux > > java version "1.6.0_17" > Java(TM) SE Runtime Environment (build 1.6.0_17-b04) > Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode) > > Tomcat: apache-tomcat-6.0.20 > > These are the current JAVA_OPTS="-Xms1024m -Xmx1024m -XX:PermSize=368m > -XX:MaxPermSize=368m" > > I have observed the memory usage and general performance with Java > VisualVM and have seen nothing strange. I thought I was seeing GC as > memory usage was going up and down but in fact it was mostly people > coming onto the system and leaving it. After several hours, the memory > settles to a baseline of about 375MB. Forced GC never takes it below > that value and the ups and downs from the people coming onto and > leaving the system also returns it to pretty much that value. The > maximum memory used never was above 700MB for the entire day. > > The server runs well, idling along at 2-5% load, except for a quick > spike during GC, serving jsp's, etc. at a reasonable speed. Without > warning and with no tracks in any log (Tomcat or system) or to the > console, Tomcat just shuts down. I can usually simply restart it as > the ports used by Tomcat are closed... today, I needed to run > shutdown.sh before I could run startup.sh (startup.sh gave no errors > but would not start Tomcat until I ran shutdown.sh and that process put > nothing in the logs... this is the first time this has happened.) > > Sometimes, the system will run for a week, sometimes for only several > hours, sometimes only for a few minutes. Today, it ran until about > 1:00PM and has been down four times since then. > > The failure (Tomcat shutting down) is not always the same place in the > code (I have some debugging messages going to catalina.out.) > > Load does not seem to make a difference. > > I have tried another sever (Dell T105, AMD processor, 6GB memory) and > have observed the same results. I have run memTest86 on the T110 for > about 30 hours and it showed nothing. > > I rebuilt the T110 with SUSE linux, Java 1.6.18 and Tomcat 6.0.24... it > lasted 15 minutes. I have used the same server.xml on all the > installs: > > > > > SSLEngine="on" /> > > > > > > > > className="org.apache.catalina.mbeans.ServerLifecycleListener" /> > > className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" > /> > > > > > > > > > type="org.apache.catalina.UserDatabase" > > description="User database that can be updated and saved" > > factory="org.apache.catalina.users.MemoryUserDatabaseFactory" > > pathname="conf/tomcat-users.xml" /> > > > > > > > > > > > > > > > > > > maxHttpHeaderSize="8192" > > maxThreads="600" minSpareThreads="25" maxSpareThreads="75" > > enableLookups="false" redirectPort="8443" scheme="http" > acceptCount="100" > > connectionTimeout="2" disableUploadTimeout="true" /> > > > > > > > > > > maxThreads="600" minSpareThreads="25" maxSpareThreads="75" > > enableLookups="false" disableUploadTimeout="true" > > acceptCount="100" scheme="https" secure="true" > > clientAuth="false" sslProtocol="TLS" SSLEnabled="true" > > keystoreFile="/usr/local/certs/tomcat_keystore.ks" > keystorePass="jellybean"/> > > > > > > > maxThreads="600" minSpareThreads="25" maxSpareThreads="75" > > enableLookups="false" disableUploadTimeout="true" > > acceptCount="100" scheme="https" secure="true" > > clientAuth="false" sslProtocol="TLS" SSLEnabled="true" > > keystoreFile="/usr/local/certs/tomcat_keystore.ks" > keystorePass="jellybean"/> > > > > > > > > enableLookups="false" redirectPort="443" protocol="AJP/1.3" /> > > > > > > > > > > > > > > > > > > > > > resourceName="UserDatabase"/> > > > > > unpackWARs="true" autoDeploy="true" deployOnStartup="true" > > xmlValidation="false" xmlNamespaceAware="false"> > > > > > > > > > > > > > > > > > > When Tomcat shuts down, the memory that it was using see
Re: Tomcat on Ubuntu 8.04 VPS and presumably multiple socket problems
Hi Chris, Thank you for your response and time. > Okay. Generally, it's considered polite to ask a single question in a > single thread. Next time, just post them separately. You are right and I would have done that but thought the issues might be connected and caused by some low level system problem (firewall etc.) thence I bundled them. Luckily, meanwhile all issues are gone. Not sure what actually caused them but I will post my assumptions. > 1st issue: I cannot connect to a socket server embedded in a webapp and > listening on port 1 any more in all cases. If I do it from a mobile > device, it works, if i do it from my laptop over a dsl connection (router > in > between), a channel is opened and instantly closed. This seemed to be caused by connecting too fast to the socket server. Lowering the sending frequency solved the issue. > 2nd issue: mod_jk does not work. I think I replayed multiple instructions > to > set it up multiple times but in all cases it finally says "Could not find > a > worker for worker name=myWorker" Solved by using the procedure described here (till item 11): http://ubuntuforums.org/showthread.php?t=971517 I now use (for worker.properties): workers.tomcat_home=/usr/share/tomcat5.5 workers.java_home=/usr/lib/jvm/java-1.5.0-sun ps=/ worker.list=myWorker worker.myWorker.port=8009 worker.myWorker.host=localhost worker.myWorker.type=ajp13 worker.myWorker.lbfactor=1 which before was workers.list=myWorker,ajp13 workers.myWorker.type=ajp13 workers.myWorker.host=localhost workers.myWorker.port=8009 > 3rd issue: GWT-RPC calls do not get delivered any more to the browser on > my > laptop. After having solved 1) I switched back to IPV6. Not sure if exactly this caused the calls to work again but now they work :) Cheers and sorry for bugging fatzopilot -- View this message in context: http://old.nabble.com/Tomcat-on-Ubuntu-8.04-VPS-and-presumably-multiple-socket-problems-tp27332135p27385269.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
public_html config not working
I took following from cutting and pasting from O'Reilly's Defenative Tomcat and put it inside each of my virtual hosts (as shown the default Host) and then I get resource unavaible for any request to ~user but the rest of the (virtual) host works: Any help? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Slackware 64
Chuck, Thanks for the reply. I was attempting to see if anyone had problems with 64 bit Java and 64 bit Slackware like I have been having and figured out a work around. I agree the settings are heavily dependent on the application. We have plenty of memory. It was suggested on a Java list that I add 'System.addShutdownHook(Thread)' to see if I can distinguish between exit() and halt() or some form of JVM abort. I should get to that later today but am looking for all the ammunition I can get to beat this problem. Thanks, Carl - Original Message - From: "Caldarale, Charles R" To: "Tomcat Users List" Sent: Saturday, January 30, 2010 10:19 AM Subject: RE: Slackware 64 From: Carl [mailto:c...@etrak-plus.com] Subject: Slackware 64 Has anyone successfully used Tomcat with Slackware 64 and Sun's 64 bit Java? If so, what were your Java options, particularly the ones relating to GC? Appropriate heap sizing, choice of GC algorithm, and other GC-related parameters are almost entirely dependent on the characteristics of *your* webapps and processing requirements; unless someone has an identical set of webapps and identical load patterns, anyone else's settings are irrelevant. You will need to insure that the total active process space (of which the Java heap is only a part) does not exceed the available RAM on the system, or you'll get into page thrashing pretty quickly. - 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: Slackware 64
> From: Carl [mailto:c...@etrak-plus.com] > Subject: Slackware 64 > > Has anyone successfully used Tomcat with Slackware 64 and Sun's 64 bit > Java? If so, what were your Java options, particularly the ones > relating to GC? Appropriate heap sizing, choice of GC algorithm, and other GC-related parameters are almost entirely dependent on the characteristics of *your* webapps and processing requirements; unless someone has an identical set of webapps and identical load patterns, anyone else's settings are irrelevant. You will need to insure that the total active process space (of which the Java heap is only a part) does not exceed the available RAM on the system, or you'll get into page thrashing pretty quickly. - 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: [/jakarta/isapi_redirect.dll] is not a servlet url
On 07.12.2009 16:40, magillagorilla wrote: Yes, my worker files are in the path I have specified in the registry. I am confused by this as well. I don't know where that worker name is coming from. The workers.minimal settings I posted are the ones I am using. If indeed the redirector is looking for a worker called ajp13 then, yes, it is not finding it. awarnier wrote: magillagorilla wrote: ... [Fri Dec 04 12:56:25 2009] [0160:3124] [debug] HttpExtensionProc::jk_isapi_plugin.c (1084): could not get a worker for name ajp13 [Fri Dec 04 12:56:25 2009] [0160:3124] [error] HttpExtensionProc::jk_isapi_plugin.c (1109): could not get a worker for name ajp13 ... I don't really know what the problem is, but I am intrigued by the above 2 lines in your logs. It looks as if mod_jk is looking for a worker whose /name/ is ajp13, but that does not seem to be reflected in the configuration files that you quoted. Are you sure that the configuration files you listed are really the ones that are being used ? If it can't find the worker configuration, it uses an "automatic" worker named ajp13 pointing at localhost:8009. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mod_jk codepage in header values
On 29.01.2010 22:20, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mirko, On 1/29/2010 4:02 AM, Mirko Solic wrote: Secondly i try to define JkEnvVar directive for non existent environment variable and i added also default value with some no ISO-8859-1 characters. My conf file is in utf8 encoding so default value should also be in utf8 encoding. I'd be interested in how Apache httpd reads the httpd.conf file. If it reads the file in utf-8 encoding, then this could be a problem with mod_jk. If it reads it using ISO-8859-1 or US-ASCII or something like that, then the data is already broken before mod_jk gets ahold of it. You might want to re-post your question by saying that UTF-8 data is incorrectly transmitted to request /attributes/ and see if any of the mod_jk devs can take a look at that. Apache env vars are simple C strings, i.e. sequences of single byte chars. They are copied and forwarded as such by mod_jk when configured using JkEnvVar as request attributes. I also expect any strings in the Apache config are read as such strings (at least on all platforms not having an exotic native charset like EBCDIC). The values should not get decoded or encoded in any way as long as they are only Apache environment variables. So I expect you can forward any binary garbage you like, as long as you make sure the code putting it into the environment variables doesn't already do any encoding or decoding. Now: it seems that Tomcat is by default assuming it needs to transform the binary AJP data stream for request attributes into ISO-8859-1 decoded Java strings. I'm not 100% sure here, but this is the likely the most important part of the game. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Slackware 64
Has anyone successfully used Tomcat with Slackware 64 and Sun's 64 bit Java? If so, what were your Java options, particularly the ones relating to GC? TIA, Carl
