Bug#460398: After upgrading libapache2-mod-jk from 1.2.25-2 to 1.2.26-1 apache stoped forwarding requests to tomcat.
Hi, Le samedi 12 janvier 2008 12:41:02, go...@oles.biz a écrit : Package: libapache2-mod-jk Version: 1:1.2.25-2 Severity: normal Apache http server do not forward requests to tomcat and failed with error The requested URL // was not found on this server. It's very strange behavior for me. Does libapache2-mod-jk 1.2.26-1 requires different configuration from 1.2.25-2 ? It's my configuration: NameVirtualHost *:80 NameVirtualHost *:443 JkWorkersFile /etc/libapache2-mod-jk/workers.properties JkOptions +ForwardKeySize +ForwardURICompat JkMount /dir1/* ajp13_worker JkMount /dir2/* ajp13_worker VirtualHost /VirtualHost . I'm trying to cleanup issues in libapache2-mod-jk package and this issue popped up on my radar :) I can confirm that there was a change/fix in upstream handling of JkMount copy from global scope to VirtualHost in 1.2.26. From upstream changelog [1], there was a SVN revision [2] that add new value All for JkMountCopy directive and this will switch the default of JkMountCopy from Off to On for all virtual servers. So previously ( 1.2.25) having a JkMount directive inside your global scope should have copied this to every child virtualhost. 1.2.26 fixed this issue and now provide a way to enable your expected behavior : - set JkMountCopy All in you global scope - set JkMountCopy On in each VirtualHost where you want to enable global scope JkMount I'll had some warning/docs regarding this into libapache2-mod-jk in unstable. [1] http://tomcat.apache.org/connectors-doc/miscellaneous/changelog.html [2] http://svn.apache.org/viewvc?view=revisionrevision=580809 Cheers, -- Damien - Debian Developper http://wiki.debian.org/DamienRaudeMorvan signature.asc Description: This is a digitally signed message part.
Bug#460398: bugs libapache2-mod-jk on lenny 32 bits with filer 8To
submitter 590075 maheus mleh...@cvf.fr found 590075 found 590075 1:1.2.26-2+lenny1 thanks On Thu, May 06, 2010 at 02:55:35PM +0200, maheus wrote: On lenny 32 bits with remote nfs 8To if workers.properties located on filer with value inode very high (probably 2^31) then workers.properties is not found by apache I recompile the libapache2-mod-jk sources with CFLAGS=$CFLAGS -D_FILE_OFFSET_BITS=64 and it solves the problem. I guess this relates to a totally different problem, so I've cloned it to #590075, hoping it will be treated there separately. Hope this helps. Best regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#460398: Another victim
On Wed, Jul 23, 2008 at 01:22:37PM +0100, Matthew Exley wrote: Just wanted to say that I'm having the same problem with my own just-installed mod_jk installation. The connector is ignoring all JkMount directives in a global (in my case /etc/apache2/conf.d/mod_jk.conf) configuration, and instead these must be applied within each VirtualHosts definition. Indeed, the docs says : file:///usr/share/doc/libapache-mod-jk-doc/reference/apache.html ... You can use the JkMount directive at the top level or inside VirtualHost sections of your httpd.conf file. ... My 2 cents, Best regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#460398: bugs libapache2-mod-jk on lenny 32 bits with filer 8To
Package: libapache2-mod-jk Version: 1:1.2.26-2+lenny1 Followup-For: Bug #460398 Sorry for my bad english On lenny 32 bits with remote nfs 8To if workers.properties located on filer with value inode very high (probably 2^31) then workers.properties is not found by apache I recompile the libapache2-mod-jk sources with CFLAGS=$CFLAGS -D_FILE_OFFSET_BITS=64 and it solves the problem. -- System Information: Debian Release: 5.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libapache2-mod-jk depends on: ii apache2 2.2.9-10+lenny7 Apache HTTP Server metapackage ii apache2-mpm-prefork [apa 2.2.9-10+lenny7 Apache HTTP Server - traditional n ii apache2.2-common 2.2.9-10+lenny7 Apache HTTP Server common files ii libc62.7-18 GNU C Library: Shared libraries libapache2-mod-jk recommends no packages. Versions of packages libapache2-mod-jk suggests: pn libapache-mod-jk-doc none (no description available) pn tomcat5.5 none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#460398: Another victim
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just wanted to say that I'm having the same problem with my own just-installed mod_jk installation. The connector is ignoring all JkMount directives in a global (in my case /etc/apache2/conf.d/mod_jk.conf) configuration, and instead these must be applied within each VirtualHosts definition. - -- Matthew Exley[EMAIL PROTECTED] Men are like Lava Lamps. Fun to look at, but not all that bright Paused: Snyper by Hybrid (rated 8/10) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkiHIo0ACgkQ0tj02rSlysIXeACeNekB2pRSLE92rsymW3U0zPR8 1vAAn1jj19zm+ANkdQXvcddXAjHDSJLx =2Ruo -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460398:
I have this bug also/too in 1.2.26-2. smime.p7s Description: S/MIME cryptographic signature
Bug#460398: Same here
On Tue, Jan 15, 2008 at 01:13:53PM +0100, Ralf Hildebrandt wrote: I have exactly the same problem, the config that used to work perfectly with 1.2.25-2 won't work with 1.2.26-1! I have just uploaded 1.2.26-2. Can you please test if this fixes it for you? Thank in advance. Cheers, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460398: Same here
I have exactly the same problem, the config that used to work perfectly with 1.2.25-2 won't work with 1.2.26-1! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460398: After upgrading libapache2-mod-jk from 1.2.25-2 to 1.2.26-1 apache stoped
After some experiments, I found that in case of virtual hosts JkMount must be inside every VirtualHost tag. Versions prior 1.2.26 allow single JkMount for all virtual hosts. What is this ? Bug ? Feature ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460398: After upgrading libapache2-mod-jk from 1.2.25-2 to 1.2.26-1 apache stoped forwarding requests to tomcat.
Package: libapache2-mod-jk Version: 1:1.2.25-2 Severity: normal Apache http server do not forward requests to tomcat and failed with error The requested URL // was not found on this server. It's very strange behavior for me. Does libapache2-mod-jk 1.2.26-1 requires different configuration from 1.2.25-2 ? It's my configuration: NameVirtualHost *:80 NameVirtualHost *:443 JkWorkersFile /etc/libapache2-mod-jk/workers.properties JkOptions +ForwardKeySize +ForwardURICompat JkMount /dir1/* ajp13_worker JkMount /dir2/* ajp13_worker VirtualHost /VirtualHost . VirtualHost /VirtualHost Regards Georgi -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libapache2-mod-jk depends on: ii apache2 2.2.6-3Next generation, scalable, extenda ii apache2-mpm-prefork [apache2] 2.2.6-3Traditional model for Apache HTTPD ii apache2.2-common 2.2.6-3Next generation, scalable, extenda ii libc6 2.7-5 GNU C Library: Shared libraries libapache2-mod-jk recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
