apache 1.3, mod_jk 1.2, jakarta 4.1.12, and cookies
In tomcat 3.3 if I had a load balanced worker the cookie set had a .worker_name appended to the end of it. I'm trying to set up tomcat 4.1.12 with mod_jk 1.2 and apache 1.3 and the cookie no longer has the worker name appended to the end of it and (I believe as a result) my session doesn't stick to one server. Has anyone else seen this behavior? Is it a tomcat bug or a configuration directive that I'm missing somewhere? Please cc me as I'm not subscribed to the list. Thanks, Jason -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat 4.0.4 RPM Red Hat Install Problems
Some of the dependancy RPMs are on www.jpackage.org. I think the one that provides update-alternatives is jpackage-utils. The update-alternatives is derived from Debian, but is used in this case to determine a jaxp parser (and is also present in RH 7.3). You'll probably need some other RPMs, which should also be on the jpackage site. Jason -Original Message- From: BOLIN,RON (HP-USA,ex1) [mailto:[EMAIL PROTECTED]] Sent: Mon 7/22/2002 6:58 AM To: 'Tomcat Users List' Cc: Subject:RE: Tomcat 4.0.4 RPM Red Hat Install Problems I downloaded the latest Tomcat 4.0.4 RPMS and tried to install them on my Red Hat 7.2 system the same way I did for Tomcat 4.0.3. However, the new 4.0.4 RPMS have a dependancy on /usr/sbin/update-alteratives - which to my knowledge does not come with RH, but instead comes with Debian Linux. Did the Tomcat team decide to switch their RPMS to Debian? If so what is the workaround to get Tomcat 4.0.4 RPMS to install on RH? Will I need to install some Debain RPMS on RH now? Thanks -Ron -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] winmail.dat -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Distribution Policy? Where did the RPMs go?
Don't take me as a definitive source as I'm not a commiter (or even a developer) but I believe there is work to make the RPMs for tomcat4 more FHS compliant. There is also some debate as to how FHS compliance should be achieved (proper directory structure, symlinking in post-install, etc.). This is not a small task, so the RPMs may be a bit delayed as compared to how quickly they were posted in the past. And I do not believe the RPMs are built via the same build tasks that produce the other platform binaries, although that seems like a worthwhile goal to move towards if possible. Rest assured though that tomcat RPMs have not been dropped from the plans as far as I've seen, and if they have been I'll start building some. :-) Jason -Original Message- From: Eddie Bush [mailto:[EMAIL PROTECTED]] Sent: Friday, June 21, 2002 12:01 PM To: Tomcat Users Mailing List Subject: Distribution Policy? Where did the RPMs go? Note: This is a slightly reworded posting from yesterday. I got no response, and really wanted one. I'm reposting because I'm assuming nobody that knew saw it - and that it's so far down in the stack now they will not see it. Hi - just curious if there would be no more RPM distributions past 4.0.3. That's the last version I see one for. I rather like the RPMs myself and would like to see them continue. Did someone accidentally comment out that part of the Ant script? =) I certainly hope you all haven't decided to no longer build RPM distributions =( Anyone know what is up? Thanks! Eddie -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: tyrex build issues
I think I saw something on the tomcat-dev list about backing out changes to Tyrex. You may want to look at the tomcat-dev archives or try building from CVS. Hope this helps, Jason -Original Message- From: chad kellerman [mailto:[EMAIL PROTECTED]] Sent: Monday, June 03, 2002 9:50 AM To: Tomcat Users List Subject: tyrex build issues Hello everyone, I am trying to build tomcat 4 from source. I followed the Building.txt file but when I issue the ant commands my build fails at tyrex naming. Here are the errors: Note: sun.tools.javac.Main has been deprecated. [javac] /usr/local/jakarta-tomcat-4.0.3/catalina/src/share/org/apache/naming/factory/TyrexTransactionFactory.java:75: Class tyrex.tm.Tyrex not found in import. [javac] import tyrex.tm.Tyrex; The are about three of these erros then I get the ever popular build failed: 4 errors, 2 warnings BUILD FAILED Can anyone give me some insite to what I ma doing wrong? THanks for the help. --chad -- Chad Kellerman -- 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: Incomplete RPM Tomcat Distribution?
Keith, You may get some discussion going on this list but I think this may be one you want to transfer to tomcat-dev. My suspicion is that the tyrex packages are available either as a separate package (from the tyrex distributors or http://www.jpackage.org/) or indeed there is some licensing issue. I haven't looked at the RPM of tomcat that you're referencing, but I do know that the 4.0.4b2 RPMs had a spec file in them, as I have rebuilt them and submitted patches back to Henri on a couple of items. If the spec file is missing from the 4.0.3 RPMs, it is an oversight that can be easily corrected and probably will be if you mention it to him. Hope this helps, Jason -Original Message- From: Keith Irwin [mailto:[EMAIL PROTECTED]] Sent: Fri 5/24/2002 12:59 PM To: Tomcat Users List Cc: Subject:Incomplete RPM Tomcat Distribution? Folks-- I've recently been struggling with Tomcat's default connection pool mechanism as have many people of late. What I discovered was this: The binary tarball distribution of Tomcat 4.0.3 contains the necessary jars (tyrex, the tyrex hooks in naming-factory.jar, a later version of jdbc optional package, etc). I was able to move my application to this version of Tomcat and with a few tweaks (ie, moving my jdbc libs from tomcat's lib directory to its common/lib directory so that tomcat itself could access them) I got connection pooling working as per the JNDI-HowTo on the jakarta site. HOWEVER: The RPM distribution of Tomcat 4 does not contain any of the classes and jars necessary to get this working. Some questions: Is there a good reason for this? (IE, is there some sort of licensing issue with tyrex that prevents it being distributed?) Is this the place to talk about packaging issues or should I try over at the tomcat-developers list? (I'd rather speak to a larger audience than just Henri Gomez, the packager.) Are there plans to fix this? I'm faced with this bizarre situation: I work in an environment in which we must have our code packaged in RPMS. It would be so much nicer if we could use already packaged software maintained by others and then, when we install our own apps, we can just tweak these standard, known configurations. In other words, really leveraging open source for all it's worth. ;) But because of this connection pool stuff, I have to either 1) use a third party lib (and poolman throws a concurrancy exception when I close connections after a transaction against postgres) and this a third party configuration method, or 2) have my application install RPM replace half the libs the standard Tomcat RPM installs. I'm not even sure this is possible as replacing another RPM's files might be considered a conflict. WHAT I REALLY WANT TO DO is make the Tomcat 4.X RPM better. Another interesting wrinkle is that the Tomcat source distribution doesn't contain the RPM spec file, nor does it contain half the libraries it depends on. You have to download them as per the build instructions. So, I'm not sure how to submit a patch against anything to get what I need. Suggestions? Should I create my own RPM package for tomcat for private use? Regardless, I'd like to see an RPM distribution that enables connection pooling. Keith -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] winmail.dat Description: application/ms-tnef -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
