Created attachment 10475 [details] JK module for connecting Apache to Tomcat
Created attachment 10476 [details] JK module for connecting Apache to Tomcat
Created attachment 10737 [details] JK module for connecting Apache to Tomcat Added to allow for the module to work with minimal configuration. insinto /etc/tomcat doins ${FILESDIR}/tomcat-apache.conf doins ${FILESDIR}/workers.properties
Created attachment 10738 [details] tomcat-apache.conf files This file should be placed in the fiels directory.
Created attachment 10739 [details] workers.properties file. This file should be placed in the fiels directory.
Created attachment 10961 [details] JK module for connecting Apache to Tomcat Changed /etc/tomcat to /opt/tomcat/conf.
Created attachment 10962 [details] tomcat-apache.conf file. Changed path from /etc/tomcat to /opt/tomcat/conf.
Created attachment 10963 [details] worker.properties file. Changed /etc/tomcat to /opt/tomcat/conf.
Created attachment 10964 [details] JK module for connecting Apache to Tomcat Changed /etc/tomcat to /opt/tomcat/conf.
I will take this on. Already working on it in #18353.
Will this be limited to Apache 2.0 or will it also support 1.3?
how about adding the statement "bevore apache" in the "depend" section of the tomcat init script to force tomcat to load bevore apache? something like this: depend() { need net use dns logger mysql postgresql bevore apache } i had trouble loading apache if i used the jk module and did not load tomcat bevore apache.
I didn't have any problems with starting apache or tomcat in any order. What does your apache configuration for jk look like? This is mine. LoadModule jk_module extramodules/mod_jk.so JkWorkersFile "/etc/tomcat/workers.properties" JkLogFile "/var/log/tomcat/mod_jk.log" JkLogLevel info JkMount /examples ajp13 JkMount /examples/* ajp13 JkMount /servlet ajp13 JkMount /servlet/* ajp13
Brett Simpson: I used the binary modules mod_jk-1.3-eapi.so and mod_jk-1.3-noeapi.so when I got that problem. But now I rewrote your ebuild to fit more to my needs. I will attach it into this bugzilla thread. I did not used the complete connector source package like you, because it is 1.7MB big and for the jk module you only need the small package wich is about 361KB. Another thing I enabled is the additional, but optional SSL support and full support for Apache 2.x. I did not do anything with your tomcat-apache.conf and/or workers.properties (I remarked that part. But since you posted that bugzilla message, I leave it to you to do what every you want with the ebuild I am proposing.) Another thing wich is still missing in my ebuild is the support for JNI. I will add that later if you want me to do it. Anyway... have a look at the ebuild, maybe you like it more then yours? cheers SteveB
Brett Simpson: I used the binary mod_jk-1.3-eapi.so and mod_jk-1.3-noeapi.so when I got that error. But what I did now is, that I wrote a new ebuild to fit more to my needs. It is basicly doing the same thing as yours, except that it does not download the full 1.7MB connectors source. I just download the small package (wich is about 300KB), because for mod_jk you don't need the full sources of all connectors. Another thing I added is the additional, but optional support for mod_ssl and full support for Apache 2. I did not do anything with the conf and workers file (I added that part into my ebuild, but remarked it). Since you submitted this bugzilla bug, I leave it up to you, to do whatever you like whit the ebuild I am suggesting. Another thing wich is still missing is the additional and optional support for JNI. If you want, I can add that as well. Anyway... have a look at the proposed ebuild. Maybe you like it and we can replace yours or merge it with yours. I think the link for the ebuild is: http://bugs.gentoo.org/attachment.cgi?id=11701&action=view cheers SteveB
I tried your ebuild out but it couldn't find http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v4.1.24/src/jakarta-tomcat-connectors-jk-4.1.24-src.tar.gz If you go to http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/ you will notice there is no v4.1.24 src. Was it removed recently?
Brett: Please read the 3th line of the ebuild! You need to name the ebuild with a version number 1.2.3 (I used net-www/mod_jk-1.2.3.ebuild), because the JK part of the connectors in tomcat has the version number 1.2.3 and not the same version number (4.1.24) as tomcat. cheers SteveB
Created attachment 11725 [details] Ebuild from tp22a@softhome.net I used 1.2.3 for the ebuild name and it worked on my install without any issues. Since this is a better ebuild than mine I'm obsoleting file 10964. Brett
Okay... since you like my ebuild for mod_jk, I took the time to include JNI support and install additional documentation (if requested by the use flags). Have a look at it. I think there is nothing more I can add to this ebuild anymore. cheers SteveB
Go ahead and add jni suppor. I would like to give it a try.
Created attachment 11754 [details] added more info for user (especialy for non SSL user)
Created attachment 11755 [details] more verbose version of tomcat-apache.conf
Okay. I added JNI support and polished up the output for the end user. new ebuild [mod_jk-1.2.3-r2.ebuild]: http://bugs.gentoo.org/attachment.cgi?bugid=19094&action=enter This time I took the time and added more information to the tomcat-apache.conf. This version does not do anything special. It has just more information about each of the configuration statements: http://bugs.gentoo.org/attachment.cgi?bugid=19094&action=enter The only thing i would like to have changed in the workers.properties file is: change: #workers.tomcat_home=c:\tomcat workers.tomcat_home=/opt/tomcat to: #workers.tomcat_home=c:\tomcat #workers.tomcat_home=/opt/tomcat workers.tomcat_home=$CATALINA_HOME cheers SteveB
agahhaaarrrr!! I am stupid! Bugzilla is not so intuitive for me as it should be! new ebuild [mod_jk-1.2.3-r2.ebuild]: http://bugs.gentoo.org/attachment.cgi?id=11754&action=view new tomcat-apache.conf: http://bugs.gentoo.org/attachment.cgi?id=11755&action=view cheers SteveB
I obsoleted 11725 and 10962 in favor of SteveBs 11754 and 11755. It worked great for me. Tried it by emerging mod_jk and it installed tomcat, apache, ssl without a hitch. Brett
Created attachment 11766 [details] added pkg_config, using now apachedelmod and apacheaddmod to modify apache.conf, mod_jk now uses APACHE_OPTS from /etc/conf.d/apache (-D JK) net-www/mod_jk-1.2.3-r3.ebuild - added pkg_config - using now apachedelmod and apacheaddmod to modify apache.conf - mod_jk now uses APACHE_OPTS from /etc/conf.d/apache (-D JK)
Created attachment 11767 [details] removed LoadModule, since this is now handled by the mod_jk.1.2.3-r3.ebuild it self removed LoadModule statement, since the new mod_jk.1.2.3-r3.ebuild allows the end user to modify apache.conf by using the ebuild config method.
What can I say? Once again a new ebuild revision. I think this will be my last revision, since I don't know what to add more to this ebuild or change. I hope you find it now more user-friendly. cheers SteveB PS: Please re-read the ebuild for any english typing errors, since english is not my native language.
Created attachment 11782 [details, diff] This is a patch that includes some spelling corrections for the ebuild. Tested your r3 ebuild on another machine that didn't have apache, tomcat, or mod_jk installed. Everything worked great! Brett
Created attachment 11816 [details] spelling correction 12.05.2003: net-www/mod_jk-1.2.3-r4.ebuild - corrected spelling (thx to Brett Simpson, simpsonb@impmail.dnsalias.com) - taking care of 'use doc' in pkg_postinst
added now another ebuild with correction. http://bugs.gentoo.org/attachment.cgi?id=11816&action=view cheers SteveB
Created attachment 11857 [details] net-www/mod_jk-1.2.3-r5.ebuild I readed the Apache2 ebuild and saw, that some stuff is diffrend then for Apache1. I tryed to take care of this in this ebuild, but I am not sure if it will work under Apache2. Can someone try this with Apache2 and tell me if it is working or not? cheers SteveB # Revisions: 12.05.2003: net-www/mod_jk-1.2.3-r5.ebuild # - fixed some stuff with Apache2 (I am still not sure if # everything is okay. Don't have Apache2 installed. I just have # readed the apache2 ebuild, but not installed it.) # 12.05.2003: net-www/mod_jk-1.2.3-r4.ebuild # - corrected spelling (thx to Brett Simpson, simpsonb@impmail.dnsalias.com) # - taking care of 'use doc' in pkg_postinst # 10.05.2003: net-www/mod_jk-1.2.3-r3.ebuild # - added pkg_config # - using now apachedelmod and apacheaddmod to modify apache.conf # - mod_jk now uses APACHE_OPTS from /etc/conf.d/apache (-D JK) # 10.05.2003: net-www/mod_jk-1.2.3-r2.ebuild # - added more info for user (especialy for non SSL user) # 09.05.2003: net-www/mod_jk-1.2.3-r1.ebuild # - added doc IUSE flag # - added jni IUSE flag (this use flag does not officialy exists) # to install mod_jk with JNI support do the following: USE='jni' emerge mod_jk # - added various config flags if jni is used # - polished up some ebuild parts # 08.05.2003: net-www/mod_jk-1.2.3.ebuild # - initial ebuild
Created attachment 11963 [details, diff] mod_jk-jk-native-configure.in.patch Patch configure.in to fix problem with Apache2
Created attachment 11964 [details] mod_jk-1.2.3-r6.ebuild # 14.05.2003: net-www/mod_jk-1.2.3-r6.ebuild # - added --with-java-platform=2 (we force anyway >=virtual/jdk-1.2) # - fixed econf problem with Apache2 (using now "--with-apxs" instead of "--with-apxs2") # - added patch for configure.in if using Apache2 # - fixed some stuff with Apache2 (this time i tested it with Apache2) # - changed the way pkg_config and pkg_postrm checks for apache2 USE flag (this fixes # problems where the user installed this module with "USE='apache2' emerge mod_jk" # but did not have apache2 in their make.conf
We need more testers for APACHE2 and mod_jk!!! If any one is reading this and has apache2 and tomcat installed, please download this ebuild and try to build and install mod_jk and post a message in bugzilla if it is working or not. It would be nice to know where we still have problems with this ebuild and where it is working. cheers SteveB
I tested apache2 with mod_jk-1.2.3-r6.ebuild and found that the apacheaddmod doesn't work since apacheaddmod doesn't seem to get installed with apache2. Otherwise the module installs and works fine. Brett
Created attachment 11982 [details] mod_jk-1.2.3-r7.ebuild # 14.05.2003: net-www/mod_jk-1.2.3-r7.ebuild # - Added a replacement for apachedelmod/apacheaddmod, written in sed # - Added RDEPEND to grep and sed, since we use it so heavy in this ebuild I can not belive it! Such a nice tool like apachedelmod and apacheaddmod not installed for Apache2? Anyway... I am now doing it with SED if I don't find apachedelmod and/or apacheaddmod installed on the target computer. Thx Brett for helping getting this ebuild better. cheers SteveB btw: Does Apache2 need the following statement in apache2.conf? (I did not added that one into apache2.conf, since the original apache2.conf file does not have a single line with "AddModule" in it): <IfDefine JK> AddModule mod_jk.c </IfDefine>
Seemed to install ok but starting apache 2.0 gave me this error. [Mon May 12 20:59:31 2003] [notice] Digest: generating secret for digest authentication ... [Mon May 12 20:59:31 2003] [notice] Digest: done [Mon May 12 20:59:32 2003] [notice] Apache/2.0.45 (Gentoo/Linux) configured -- resuming normal operations [Mon May 12 20:59:49 2003] [error] [client 127.0.0.1] File does not exist: /home/httpd/htdocs/favicon.ico [Wed May 14 16:14:23 2003] [error] (22)Invalid argument: apr_global_mutex_lock(jk_log_lock) failed mod_jk: jk_log_to_file [Wed May 14 16:14:23 2003] [jk_worker.c (118)]: Into wc_close failed: Bad file descriptor [Wed May 14 16:15:15 2003] [error] (22)Invalid argument: apr_global_mutex_lock(jk_log_lock) failed mod_jk: jk_log_to_file [Wed May 14 16:15:15 2003] [jk_worker.c (118)]: Into wc_close failed: Bad file descriptor [Wed May 14 16:15:36 2003] [error] (22)Invalid argument: apr_global_mutex_lock(jk_log_lock) failed mod_jk: jk_log_to_file [Wed May 14 16:15:36 2003] [jk_worker.c (118)]: Into wc_close failed: Bad file descriptor [Wed May 14 16:28:53 2003] [error] (22)Invalid argument: apr_global_mutex_lock(jk_log_lock) failed mod_jk: jk_log_to_file [Wed May 14 16:28:53 2003] [jk_worker.c (118)]: Into wc_close failed: Bad file descriptor
Apache 2.0 doesnt need AddModule statements. I also figured out why I was getting those errorson my laptop. env showed that blackdown-jdk-1.3.1 was in use so I emerged blackdown-jdk-1.4.1 and ran /usr/bin/java-config --set-system-vm=blackdown-jdk-1.4.1 and source /etc/profile Maybe a require jdk 1.4.1 or greater is needed before this ebuild should run and something that will double check the env to be sure the path is correct.
Created attachment 11994 [details] mod_jk-1.2.3-r8.ebuild # 15.05.2003: net-www/mod_jk-1.2.3-r8.ebuild # - cleanup of local variables # - added patch for apache2 to work with jk # (from CVS jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c) # - added JAVA version and JDK check (requested by Brett Simpson, simpsonb@impmail.dnsalias.com) # - increased requirement for jdk to 1.4.1 (requested by Brett Simpson, simpsonb@impmail.dnsalias.com)
Created attachment 11995 [details, diff] mod_jk-jk-native-apache_2.0-mod_jk-rev-1.70.2.1-patch Patch to update jk/native/apache-2.0/mod_jk.c to revision 1.70.2.1 and allow apache2 to work with mod_jk.
Brett: I searched the jarkata-tomcat-connectors mailing list for a issue with mod_jk and apache2 and found something posted by a person called "glenn". I included his patch for jk/native/apache-2.0/mod_jk.c (new revision of file is 1.70.2.1) and now it is working :) I hope "bug-hunter Brett" does not find other stuff :), but if you find something, please post it. cheers SteveB My Apache2 debug output while starting Apache (when you start apache2 the first time with mod_jk, then you will get another output. the mod_jk module will genearte some special stuff, but I restarted my server serval time during the test of the new mod_jk. sorry): [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module access_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module auth_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module auth_anon_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module auth_dbm_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module auth_digest_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module include_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module log_config_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module env_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module mime_magic_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module cern_meta_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module expires_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module headers_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module usertrack_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module unique_id_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module setenvif_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module proxy_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module proxy_connect_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module proxy_ftp_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module proxy_http_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module mime_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module status_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module autoindex_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module asis_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module info_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module cgi_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module cgid_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module jk_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module vhost_alias_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module negotiation_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module dir_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module imap_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module actions_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module speling_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module userdir_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module alias_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module rewrite_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module file_cache_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module echo_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module charset_lite_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module cache_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module disk_cache_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module mem_cache_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module ext_filter_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module case_filter_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module case_filter_in_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module deflate_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module logio_module [Thu May 15 00:53:37 2003] [debug] mod_so.c(290): loaded module ssl_module [Thu May 15 00:53:37 2003] [notice] Digest: generating secret for digest authentication ... [Thu May 15 00:53:37 2003] [notice] Digest: done [Thu May 15 00:53:39 2003] [notice] Apache/2.0.45 (Gentoo/Linux) mod_jk/1.2.3 mod_ssl/2.0.45 OpenSSL/0.9.6i configured -- resuming normal operations
Created attachment 11999 [details] tomcat-apache.conf Removed loadmodule section since its present in apache2.conf and apache.conf. Brett
Tested mod_jk-1.2.3-r8.ebuild with apache and apache2 and it looks good for x86 stable. Brett
Brett: I think your new created tomcat-apache.conf (http://bugs.gentoo.org/attachment.cgi?id=11999&action=view) is the same as my old version (http://bugs.gentoo.org/attachment.cgi?id=11767&action=view) Schould I obsolete my version? cheers SteveB
My mistake. I obsoleted the tomcat-apache.conf I just submitted.
Brett: No problem :) I hope we get now some ppl to test this ebuild on apache 1.x and apache 2.x. Would be nice to see that the ebuild works out for others and it would be nice to see this ebuild moving into stable. cheers SteveB
Created attachment 12014 [details] mod_jk-1.2.3-r9.ebuild # 15.05.2003: net-www/mod_jk-1.2.3-r9.ebuild # - fixed a typo in pkg_postrm # - fixed again spelling errors # - added checks in pkg_config and pkg_postrm to check for proper add/del of JK entries
Created attachment 12018 [details] mod_jk-1.2.3-r10.ebuild # 15.05.2003: net-www/mod_jk-1.2.3-r10.ebuild # - check if all files in ${FILESDIR} are there (it is so easy to miss downloading them in bugzilla)
Created attachment 12071 [details] mod_jk does not install emerge /usr/portage/net-www/mod_jk/mod_jk-1.2.3-r10.ebuild Calculating dependencies ...done! >>> emerge (1 of 1) net-www/mod_jk-1.2.3-r10 to / >>> md5 ;-) jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz >>> Unpacking source... >>> Unpacking jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz to /var/tmp/portage/mod_jk-1.2.3-r10/work * Applying mod_jk-jk-native-configure.in.patch... * Failed Patch: mod_jk-jk-native-configure.in.patch! * * Include in your bugreport the contents of: * * /var/tmp/portage/mod_jk-1.2.3-r10/temp/mod_jk-jk-native-configure.in.patch-7855.out !!! ERROR: net-www/mod_jk-1.2.3-r10 failed. !!! Function epatch, Line 354, Exitcode 0 !!! Failed Patch: mod_jk-jk-native-configure.in.patch!
Here is the output I get when I try to emerge mod_jk the content of the output is in the attachement "mod_jk does not install" Thx, Ghi Calculating dependencies ...done! >>> emerge (1 of 1) net-www/mod_jk-1.2.3-r10 to / >>> md5 ;-) jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz >>> Unpacking source... >>> Unpacking jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz to /var/tmp/portage/mod_jk-1.2.3-r10/work * Applying mod_jk-jk-native-configure.in.patch... [ ok ] * Applying mod_jk-jk-native-apache_2.0-mod_jk-rev-1.70.2.1-patch... * Failed Patch: mod_jk-jk-native-apache_2.0-mod_jk-rev-1.70.2.1-patch! * * Include in your bugreport the contents of: * * /var/tmp/portage/mod_jk-1.2.3-r10/temp/mod_jk-jk-native-apache_2.0-mod_jk-rev-1.70.2.1-patch-14471.out !!! ERROR: net-www/mod_jk-1.2.3-r10 failed. !!! Function epatch, Line 354, Exitcode 0 !!! Failed Patch: mod_jk-jk-native-apache_2.0-mod_jk-rev-1.70.2.1-patch!
Ghi: I think it has something to do with the way you saved the patch file (you need to save it in unix format!). If I do that on my computer, the patching works without problems: spok / # USE='apache2 doc jni ssl' emerge -pv mod_jk These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] net-www/mod_jk-1.2.3-r11 [1.2.3-r8] +apache2 +doc +jni +ssl spok / # USE='apache2 doc jni ssl' emerge -v mod_jk Calculating dependencies ...done! >>> emerge (1 of 1) net-www/mod_jk-1.2.3-r11 to / >>> md5 ;-) jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz >>> Unpacking source... >>> Unpacking jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz to /var/tmp/portage/mod_jk-1.2.3-r11/work * Applying mod_jk-jk-native-configure.in.patch... [ ok ] * Applying mod_jk-jk-native-apache_2.0-mod_jk-rev-1.70.2.1-patch... [ ok ] >>> Source unpacked. libtoolize --force --automake --copy aclocal automake -a --foreign -i --copy automake: configure.in: installing `scripts/build/unix/install-sh' automake: configure.in: installing `scripts/build/unix/mkinstalldirs' automake: configure.in: installing `scripts/build/unix/missing' autoconf I used a new ebuild, wich I did not send to bugzilla till now. I am still working on it. When I am finished, I will submit it. cheers SteveB
Created attachment 12077 [details, diff] mod_jk-jk-native-apache_2.0-mod_jk-rev-1.70.2.1.patch same old patch as before, just renamed it to be *.patch instead of *-patch
Created attachment 12078 [details] mod_jk.conf Config file for mod_jk. Added <IfDefine JK>...<IfDefine> to avoid errors when checking apache.conf/apache2.conf with apachectl/apache2ctl.
Created attachment 12079 [details] mod_jk-1.2.3-r11.ebuild # 16.05.2003: net-www/mod_jk-1.2.3-r11.ebuild # - fixed a typo in output for user (changed # worker.properties to workers.properties) # - simplyfing ebuild # - replaced tomcat-apache.conf with mod_jk.conf # - installing *.conf and workers.properties file # into apache and not into tomcat (we are installing # an apache module and not a tomcat module) # - changed the way how jvm version gets checked
Created attachment 12087 [details] Patch not applied SteveB, Tried the last ebuild, still reporting the same issue. Thx, Ghi PS: let me know if you need more info. apache 2.0.45 is already installed before I launch the ebuild >>> md5 ;-) jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz >>> Unpacking source... >>> Unpacking jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz to /var/tmp/portage/mod_jk-1.2.3-r11/work * Applying mod_jk-jk-native-configure.in.patch... [ ok ] * Applying mod_jk-jk-native-apache_2.0-mod_jk-rev-1.70.2.1.patch... * Failed Patch: mod_jk-jk-native-apache_2.0-mod_jk-rev-1.70.2.1.patch! * * Include in your bugreport the contents of: * * /var/tmp/portage/mod_jk-1.2.3-r11/temp/mod_jk-jk-native-apache_2.0-mod_jk-rev-1.70.2.1.patch-8281.out !!! ERROR: net-www/mod_jk-1.2.3-r11 failed. !!! Function epatch, Line 354, Exitcode 0 !!! Failed Patch: mod_jk-jk-native-apache_2.0-mod_jk-rev-1.70.2.1.patch!
Ghi: You have absolutly right! It is not working anymore! the reason for it is, that the source code got changed without changing the version number!!! Proof: # ebuild /usr/local/portage/net-www/mod_jk/mod_jk-1.2.3-r11.ebuild unpack # grep -i "Version:" /var/tmp/portage/mod_jk-1.2.3-r11/work/jakarta-tomcat-connectors-jk-1.2.3-src/jk/native/apache-2.0/mod_jk.c * Version: $Revision: 1.70.2.2 $ * But when I was doing the patch the version was: Version: $Revision: 1.70 $ another proof (old file): vulcan root # ls -lah /usr/portage/distfiles/jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz -rw-r--r-- 1 root root 361K Apr 29 04:20 /usr/portage/distfiles/jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz vulcan root # md5sum /usr/portage/distfiles/jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz 97f127011175ba2c67c642e8b6327669 /usr/portage/distfiles/jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz new file: vulcan root # ls -lah /usr/portage/distfiles/jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz -rw-r--r-- 1 root root 361K May 16 02:19 /usr/portage/distfiles/jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz vulcan root # md5sum /usr/portage/distfiles/jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz 4c2c2a4e6a6ad8a912afaffbff173227 /usr/portage/distfiles/jakarta-tomcat-connectors-jk-1.2.3-src.tar.gz anyway... i am going to create a -r12 revision of the ebuild without the patch! but first i need to test it. :) cheers SteveB
Created attachment 12106 [details] mod_jk-1.2.3-r12.ebuild # 18.05.2003: net-www/mod_jk-1.2.3-r12.ebuild # - removing patch: # mod_jk-jk-native-apache_2.0-mod_jk-rev-1.70.2.1.patch # - i can not belive it! they changed the content of # the source code, without changing the version no. # before md5sum was: 97f127011175ba2c67c642e8b6327669 # and now it is: 4c2c2a4e6a6ad8a912afaffbff173227 # they modified serval things wich makes the patch # mod_jk-jk-native-apache_2.0-mod_jk-rev-1.70.2.1.patch # obsolete.
Hi SteveB, The ebuild installs like a charm, now. Thx for the work. Cheers, Ghi
I tried the ebuild ad came across follwing problems: 1. root@notebook mod_jk # emerge mod_jk-1.2.3-r12.ebuild Calculating dependencies \ emerge: there are no masked or unmasked ebuilds to satisfy ">=virtual/jdk-1.4.1". !!! Error calculating dependencies. Please correct. after removing the line from the ebuild I tried again. 2. root@notebook mod_jk # emerge -pv mod_jk-1.2.3-r12.ebuild These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] net-www/apache-1.3.27-r4 [2.0.45] -ipv6 -pam [ebuild N ] net-www/mod_ssl-2.8.14 [ebuild N ] net-www/mod_jk-1.2.3-r12 +apache2 -doc -jni +ssl I want to use apache2, but It will emerge apache-1.3 too unless I remove ssl from the USE-flags. everything else works just perfect. Thank you.
Created attachment 12123 [details] mod_jk-1.2.3-r13.ebuild # 18.05.2003: net-www/mod_jk-1.2.3-r13.ebuild # - set jdk requirement down to >=virtual/jdk-1.4 # - install mod_ssl only if apache2 is not used, because # mod_ssl requires =net-www/apache-1.3.27* # ACCEPT_KEYWORDS='~x86' USE='ssl jni doc apache2' emerge -pe mod_jk | grep -i "mod_ssl\|apache\|tomcat\|jdk\|mod_jk" [ebuild N ] dev-java/blackdown-jdk-1.4.1 [ebuild N ] net-www/tomcat-4.1.24 [ebuild N ] net-www/apache-2.0.45 [ebuild N ] net-www/mod_jk-1.2.3-r13 # USE='ssl jni doc -apache2' emerge -pe mod_jk | grep -i "mod_ssl\|apache\|tomcat\|jdk\|mod_jk" [ebuild N ] dev-java/blackdown-jdk-1.4.1 [ebuild N ] net-www/tomcat-4.1.24 [ebuild N ] net-www/apache-1.3.27-r3 [ebuild N ] net-www/mod_ssl-2.8.14 [ebuild N ] net-www/mod_jk-1.2.3-r13
Is there a time frame for when mod_jk or mod_jk2 will be accepted into portage? I'm currently using mod_jk-1.2.3-r13 and all seems fine. I also have another ebuild I'm going to submit that depends on mod_jk. I can change this dependancy to mod_jk2 but I need to know where things are going with this bug and the mod_jk2 one before doing so. Thanks, Brett
Moving this again to java@gentoo.org, so everyone out there can help.
*** Bug 36169 has been marked as a duplicate of this bug. ***
That dupe bug has an updated ebuild for mod_jk-1.2.5
Please move assigning the env vars (JAVA_HOME and CATALINA_HOME) into a separate function (set_envvars) that is invoked at the start of pkg_setup and src_compile. Portage doesn't like it when you invoke programs in the "global space". Thanks for the contribution!
Created attachment 41532 [details] mod_jk 1.2.6 ebuild This package seems to have got a LOT easier to build. Basically started again from scratch. Tested this ebuild with apache 1.3.31 and apache 2.0.51 + tomcat 5.0.28 Look forward to some feedback on how it goes from others with differnent version of tomcat.
www-apache/mod_jk2-2.0.4 is already in the tree. Is there a need for this one too? Please reopen the bug if any one of you think so.
Please reopen (I don't seem to be able to) as the mod_jk2 serie has been abandoned. See JK2 is officially unsupported http://jakarta.apache.org/tomcat/connectors-doc/news/20041100.html#20041115.1
Yes, you are correct, we'll need to support this one as well (or instead?).
Created attachment 47676 [details] mod_jk-1.2.8 ebuild Modified previous attachment mod_jk-1.2.6.ebuild for the current version. I had to download the tarball manually to /usr/portage/distfiles, added my arch (~amd64), and removed the dependency on Tomcat-5. Someone with more expertise on ebuilds will need to restore the dependency, but it builds fine now. Both apache and Tomcat are running without errors, but I don't know of a simple test for the connector. Suggestions?
Russ, that one does not work for me: Making all in common make[1]: Entering directory `/var/tmp/portage/mod_jk-1.2.8/work/jakarta-tomcat-connectors-1.2.8-src/jk/native/common' /bin/sh /usr/lib/apache2/build/libtool --silent --mode=compile i686-pc-linux-gnu-gcc -I/usr/include/apache2 -O3 -march=athlon-xp -pipe -fomit-frame-pointer -O3 -march=athlon-xp -pipe -fomit-frame-pointer -pthread -DHAVE_APR -I/var/tmp/portage/apache-2.0.52-r1/work/httpd-2.0.52/srclib/apr/include -O3 -march=athlon-xp -pipe -fomit-frame-pointer -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I /opt/blackdown-jdk-1.4.2.01/include -I /opt/blackdown-jdk-1.4.2.01/include/ -c jk_ajp12_worker.c /bin/sh /usr/lib/apache2/build/libtool --silent --mode=compile i686-pc-linux-gnu-gcc -I/usr/include/apache2 -O3 -march=athlon-xp -pipe -fomit-frame-pointer -O3 -march=athlon-xp -pipe -fomit-frame-pointer -pthread -DHAVE_APR -I/var/tmp/portage/apache-2.0.52-r1/work/httpd-2.0.52/srclib/apr/include -O3 -march=athlon-xp -pipe -fomit-frame-pointer -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I /opt/blackdown-jdk-1.4.2.01/include -I /opt/blackdown-jdk-1.4.2.01/include/ -c jk_connect.c libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' make[1]: *** [jk_ajp12_worker.lo] Error 1 make[1]: *** Waiting for unfinished jobs.... libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' make[1]: *** [jk_connect.lo] Error 1 make[1]: Leaving directory `/var/tmp/portage/mod_jk-1.2.8/work/jakarta-tomcat-connectors-1.2.8-src/jk/native/common' make: *** [all-recursive] Error 1 !!! ERROR: www-apache/mod_jk-1.2.8 failed. !!! Function src_compile, Line 28, Exitcode 2 !!! emake failed !!! If you need support, post the topmost build error, NOT this status message.
I don't know what to tell you Jakub. I've used the ebuild I attached for both amd64 and x86 (athlon-xp). Are you using apache 2.0 or 1.3? I'm using apache-2.0.52-r1.
Russ, I know it
Russ, I know it´s probably not your ebuild´s fault. There are tons of "unable to infer tagged configuration" bugs concerning libtool, but these are all marked as fixed or duplicate but the problem is NOT fixed. I´m really out of ideas how to solve this. :-(
OK, Bug 77921 seems to be reopened now. Hopefully someone will _really_ fix this annoying one.
reassigning to /me cause i'll start maintaining tomcat.
Russ, could you have a look at this comment: http://bugs.gentoo.org/show_bug.cgi?id=77921#c17 from SpanKY? I
Russ, could you have a look at this comment: http://bugs.gentoo.org/show_bug.cgi?id=77921#c17 from SpanKY? I´m really lost as for what to do with this damned libtool thing. Nobody wants to solve this one. :-(
the libtool bug you speak of has nothing to do with this original bug file a *NEW* bug for the apache2 maintainers
SpanKY, thank you very much. You were right, this is Apache2 bug. Managed to find a workaround - see http://bugs.gentoo.org/show_bug.cgi?id=81260#c1 Sorry for bothering you.
Created attachment 50889 [details] mod_jk-1.28.8.ebuild I was unable to get the mod_jk ebuild to download, I had to add a '/jk-${PV}/' to the SRCURI.
Wrong version on that last ebuild Joshua. It should have been 1.2.8, right? If you need more testers it might be a good idea to announce this ebuild in the appropriate forum thread: http://forums.gentoo.org/viewtopic.php?p=2140544#2140544
Created attachment 53227 [details] mod_jk-1.2.8.ebuild At first - thx for the ebuild! Second - unfortunatelly it doesn't work for me out-of-the-box. I had dificulties to compile it with apache 2.0.53 from portage. So tweaked it a bit (ok - and changed it a little ;-) ) and now it works (for me...). I do not know: - will it work with apache-1.x (I don't use it) - will it work any other arch then x86 - or will it work with another versions of apache.... I just know that it works for me ;) PS. mod_jk.conf is same for apache-1 and apache-2? Don't know it either... Hope you find it useful! Best regards, Przemek
i'll start to work on this now, i think it will be ready in the next few days.
I've completly rewritten the ebuild with the help of beu and trapni. It's now based on the apache-module eclass. thanks for all your effort, though.
Created attachment 56445 [details, diff] patch for mof_jk.conf mod_jk ebuild installs mod_jk.so in modules not extra modules, and workers.properties file should be in apache conf, since it's part of it.
Created attachment 56446 [details, diff] wrong path to tomcat installation tomcat installed from portage is placed in /opt/tomcat5, not /opt/tomcat
i've modifies all these files so your patches arent necessary. take a look into the files in the tree before patching. :)
When I look at http://bugs.gentoo.org/attachment.cgi?id=10963&action=view I see there workers.tomcat_home=/opt/tomcat not /opt/tomcat5. And http://bugs.gentoo.org/attachment.cgi?id=12078&action=view sill ponts to extramodules/mod_jk.so instead to modules/mod_jk.so, plus JkWorkersFile /opt/tomcat/conf/workers.properties points to old tomcat directory, and wrong workers.properties file, since it's provided by ebuild.
Comment #88: Err, if you would actually look into _portage tree_ then it would be much better. Don
Comment #88: Err, if you would actually look into _portage tree_ then it would be much better. Don´t patch what´s patched.
