Prblm: Tomcat doesn't start on boot, JAVA_HOME not defined. Manually works fine.
Dear subscribers. I have a problem that my Tomcat 4.0.4 installation doesn't start on boot. In the boot.msg file I get a record stating that the JAVA_HOME environment variable is not defined and therefore Tomcat can't start. The strange thing is that the JAVA_HOME is defined in the profile.local file. If I log on directly after the boot and run the tomcat startup script from /etc/rc.d manually the Tomcat server starts as expected. Therefore I suspect that the problem is either that profile.local is evaluated after the Tomcat startup script when booting or the profile.local environment variables aren't available during boot for some reason. Any help on this matter would be greatly appreciated. Kind regards, Ola Theander -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Problm. building tomcat 4.0.4 jk connector for use with Apache 2.0.39. JDK 1.4.x?
Hi Shanmugampl. Thanks for your answer. I've had some progress since my last mail. I can now compile the part of the mod_jk connector that ANT is responsible for, i.e. the jar files. The problem was that servlet.jar was missing in the CLASSPATH. But now I have a new problem, according to the documentation I've found, after building the jar files with ant, I should run ant install. The problem is that ant then complains Target 'install' does not exist in this projekt. Any idea why this is the case? Kind regards, Ola -Original Message- From: shanmugampl [mailto:[EMAIL PROTECTED]] Sent: den 24 juli 2002 06:10 To: Tomcat Users List Subject: Re: Problm. building tomcat 4.0.4 jk connector for use with Apache 2.0.39. JDK 1.4.x? I have integrated Apache2.0.39 and Tomcat4.0.4 using mod_jk. I followed these steps for generating mod_jk.so 1. Took the source available at http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4 .0.4/src/jakarta-tomcat-connectors-4.0.4-src.tar.gz 2. Move to the Install Dir/jk/native directory and run the buildconf.sh. This will create the configure file 3. Run this file by specifying the -with-apxs option. Point this to your apache 2.0.39 apxs. 4. execute the commands make and make install. 5. You will find the mod_jk.so file created in the Install Dir/jk/native/apache-2.0 directory. Hope this helps. Thanks Shanmugam.PL eric wrote: Ola, I get the same result only it's mod_jk.c not compatable with this version of Apache. I'm trying to get Apache 2.0.39 and Tomcat 4.0.4 to work. If you get it to work please post how you did it here. Good luck! Eric On Monday 22 July 2002 23:16, Ola Theander wrote: Dear subscribers. I have a problem building the 4.0.4 JK connector so I can integrate my Tomcat installation with Apache 2. I've tested the webapp connector with Apache 2.0.36 but since I upgraded to 2.0.39 I get the now infamous message mod_dev.c not compatible with Therefore I like to switch to the JK connector and I also hope that the JK connector will work with Apache 2.0.39. There are also other reasons why I will change to the jk connector. I've learned to understand that it's much more mature and the webapp connector doesn't have any real advantages. The problem is that the build process chokes since it not able to find the javax.servlets.* packages. I don't know if this is because I use JDK 1.4.0 or some kind of configuration error. I've started with changing the build.properties file in the jk library. But after trying to build with Ant I figured that some helper files was needed before the build could succeed. It complained about not finding some tomcat-coyote.jar file to copy, so I started the build from the connector's source root folder and then it stopped when it failed to find the javax.servlets.* packages mentioned above. Am I totally on the wrong track here? There where also a few messages after the Package javax.servlets does not exist complaining about deprecated methods in the javax.servlets package but that might perhaps be an inherited problem? Any help on this matter would be greatly appreciated. Kind regards, Ola Theander -- To unsubscribe, e-mail: mailto:tomcat-user- [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]
Prblm: ant install fails after building mod_jk jars for tomcat-4.0.4 connectors.
Dear subscribers. I have a problem regarding the ant install part after I've built the jk (AJP13) connector for jakarta-tomcat-connectors-4.0.4. When I run ant install I get an error message Target 'install' does not exist in this project. Any idea why this is the case? The preceding build process seems to work fine. Kind regards, Ola Theander -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Prblm: ant install fails after building mod_jk jars for tomcat-4.0.4 connectors (more info).
Dear subscribers. I've noticed, when I examined the build.xml file in the jk directory, that the target install has been removed. I compared the file to the build.xml in the 4.0.2 version of the connector source and in that version the install target is there. Is there any particular reason why the install target been removed? How is it supposed to be installed now? Kind regards, Ola Theander -Original Message- From: Ola Theander [mailto:[EMAIL PROTECTED]] Sent: den 24 juli 2002 23:32 To: [EMAIL PROTECTED] Subject: Prblm: ant install fails after building mod_jk jars for tomcat-4.0.4 connectors. Dear subscribers. I have a problem regarding the ant install part after I've built the jk (AJP13) connector for jakarta-tomcat-connectors-4.0.4. When I run ant install I get an error message Target 'install' does not exist in this project. Any idea why this is the case? The preceding build process seems to work fine. Kind regards, Ola Theander -- To unsubscribe, e-mail: mailto:tomcat-user- [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]
Problm. building tomcat 4.0.4 jk connector for use with Apache 2.0.39. JDK 1.4.x?
Dear subscribers. I have a problem building the 4.0.4 JK connector so I can integrate my Tomcat installation with Apache 2. I've tested the webapp connector with Apache 2.0.36 but since I upgraded to 2.0.39 I get the now infamous message mod_dev.c not compatible with Therefore I like to switch to the JK connector and I also hope that the JK connector will work with Apache 2.0.39. There are also other reasons why I will change to the jk connector. I've learned to understand that it's much more mature and the webapp connector doesn't have any real advantages. The problem is that the build process chokes since it not able to find the javax.servlets.* packages. I don't know if this is because I use JDK 1.4.0 or some kind of configuration error. I've started with changing the build.properties file in the jk library. But after trying to build with Ant I figured that some helper files was needed before the build could succeed. It complained about not finding some tomcat-coyote.jar file to copy, so I started the build from the connector's source root folder and then it stopped when it failed to find the javax.servlets.* packages mentioned above. Am I totally on the wrong track here? There where also a few messages after the Package javax.servlets does not exist complaining about deprecated methods in the javax.servlets package but that might perhaps be an inherited problem? Any help on this matter would be greatly appreciated. Kind regards, Ola Theander -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Problm. building tomcat 4.0.4 jk connector for use with Apache 2.0.39. JDK 1.4.x?
Hi Robert. Thanks for you answer. As far as I can see there are only binaries for Windows and Solaris and I'm running SuSE Linux 8.0. Do you perhaps know where I can find binaries for the Linux platform? Kind regards, Ola Theander -Original Message- From: Robert L Sowders [mailto:[EMAIL PROTECTED]] Sent: den 22 juli 2002 23:36 To: Tomcat Users List Cc: [EMAIL PROTECTED] Subject: Re: Problm. building tomcat 4.0.4 jk connector for use with Apache 2.0.39. JDK 1.4.x? Here is a precompiled binary and also tips on building. http://www.acg-gmbh.de/mod_jk/ Ola Theander [EMAIL PROTECTED] 07/22/2002 02:16 nite Please respond to Tomcat Users List To: [EMAIL PROTECTED] cc: Subject:Problm. building tomcat 4.0.4 jk connector for use with Apache 2.0.39. JDK 1.4.x? Dear subscribers. I have a problem building the 4.0.4 JK connector so I can integrate my Tomcat installation with Apache 2. I've tested the webapp connector with Apache 2.0.36 but since I upgraded to 2.0.39 I get the now infamous message mod_dev.c not compatible with Therefore I like to switch to the JK connector and I also hope that the JK connector will work with Apache 2.0.39. There are also other reasons why I will change to the jk connector. I've learned to understand that it's much more mature and the webapp connector doesn't have any real advantages. The problem is that the build process chokes since it not able to find the javax.servlets.* packages. I don't know if this is because I use JDK 1.4.0 or some kind of configuration error. I've started with changing the build.properties file in the jk library. But after trying to build with Ant I figured that some helper files was needed before the build could succeed. It complained about not finding some tomcat-coyote.jar file to copy, so I started the build from the connector's source root folder and then it stopped when it failed to find the javax.servlets.* packages mentioned above. Am I totally on the wrong track here? There where also a few messages after the Package javax.servlets does not exist complaining about deprecated methods in the javax.servlets package but that might perhaps be an inherited problem? Any help on this matter would be greatly appreciated. Kind regards, Ola Theander -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-user- [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]
Questions about web solution based on Tomcat Apache.
Dear subscribers. I have two questions about using Tomcat 4.x Apache 2.x as a base for web application development: 1) A solution typically consists of html, jsp pages and servlets. Is it possible to store html, jsp and servlets based on the logical structure of the solution and have Tomcat process only based on the file extension or must all jsp and servlet files be collected in the folder pointed out by the WebAppDeploy attribute in httpd.conf? I.e. if I have a solution where I store customer data in a database I'll probably have at least a form page for registering a new customer, a list view where I list all customers and a servlet to store submitted customer data in a database. In a simple case the form page would be a html page and the list view an jsp page. If these files where to be grouped logically, i.e. by task, the form page, the jsp list page and the servlet should be in the same directory on disk but as I understand it Apache/Tomcat integration requires me to have the html pages in one directory structure for access by Apache and jsp/servlets in another structure, pointed out by WebAppDeploy, for access by Tomcat. Is this correct? With a logical grouping of files mentioned above I mean a directory structure like this: Customer Web |-| | customers || new_customer_from.html || list_customers.jsp || store_new_user.class | |-| companies 2) As far as I know there are two connectors for integrating Tomcat and Apache, Warp and AJP. When I experimented I've used the warp connector, but I don't really know the difference between the two besides that they utilize different protocols. If I can get some more information on this matter I'll be grateful. Kind regards, Ola Theander -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Questions about web solution based on Tomcat Apache.
Hi John. Thanks for your answer. Unfortunately I'm not sure that I understand you completely. Regarding your answer to question 1, I want Apache to serve html, image and other static content while Tomcat processes the dynamic content such as jsp pages, i.e. I don't want to use Tomcat to serve static content, i.e. that means the use of either the AJP or Warp connector. Does the use of these connectors require that I separate the static content files from the files for dynamic content? Kind regards, Ola -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: den 19 juli 2002 14:09 To: 'Tomcat Users List' Subject: RE: Questions about web solution based on Tomcat Apache. 1) Yes. Tomcat can serve images and HTML, that is the purpose of the Coyote HTTP connector, which is installed with tomcat by default. It was on my installations. 2) The difference is #1. If you want to divide static content and dynamic content, you want AJP (mod_jk). The current WARP implementation (mod_webapp) does not differentiate between static and dynamic content. It may in the future. I hope it does, though I've had zero problems with mod_jk on both tomcat 3 and 4. With mod_webapp, all content is served by tomcat, apache is not involved except as a request receiver. John Turner [EMAIL PROTECTED] -Original Message- From: Ola Theander [mailto:[EMAIL PROTECTED]] Sent: Friday, July 19, 2002 7:23 AM To: [EMAIL PROTECTED] Subject: Questions about web solution based on Tomcat Apache. Dear subscribers. I have two questions about using Tomcat 4.x Apache 2.x as a base for web application development: 1) A solution typically consists of html, jsp pages and servlets. Is it possible to store html, jsp and servlets based on the logical structure of the solution and have Tomcat process only based on the file extension or must all jsp and servlet files be collected in the folder pointed out by the WebAppDeploy attribute in httpd.conf? I.e. if I have a solution where I store customer data in a database I'll probably have at least a form page for registering a new customer, a list view where I list all customers and a servlet to store submitted customer data in a database. In a simple case the form page would be a html page and the list view an jsp page. If these files where to be grouped logically, i.e. by task, the form page, the jsp list page and the servlet should be in the same directory on disk but as I understand it Apache/Tomcat integration requires me to have the html pages in one directory structure for access by Apache and jsp/servlets in another structure, pointed out by WebAppDeploy, for access by Tomcat. Is this correct? With a logical grouping of files mentioned above I mean a directory structure like this: Customer Web |-| | customers || new_customer_from.html || list_customers.jsp || store_new_user.class | |-| companies 2) As far as I know there are two connectors for integrating Tomcat and Apache, Warp and AJP. When I experimented I've used the warp connector, but I don't really know the difference between the two besides that they utilize different protocols. If I can get some more information on this matter I'll be grateful. Kind regards, Ola Theander -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-user- [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]
