Your message dated Fri, 23 Oct 2015 03:46:03 +0200
with message-id <1976896.OHRq8Vx7hr@bagend>
and subject line Closing bug
has caused the Debian Bug report #581790,
regarding libapache2-mod-jk: tomcat auto-configure could be easier
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
581790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-jk
Version: 1:1.2.28-2
Severity: wishlist

webserver_howto/apache.html of libapache-mod-jk-doc describes how to connect
apache2 and tomcat. According to that page in the "Using Tomcat auto-configure"
 section it should be as simple as adding the following line to the Engine tag 
of the /etc/tomcat6/server.xml :
  <Listener className="org.apache.jk.config.ApacheConfig" 
     modJk="/usr/lib/apache2/modules/mod_jk.so" />

Doing that and restarting tomcat6 results in a failure, since it tries to write 
files to locations in which it can't write since they don't exist.

I got it working file the following Listener tag:
  <Listener className="org.apache.jk.config.ApacheConfig" 
     modJk="/usr/lib/apache2/modules/mod_jk.so" 
     jkConfig="/etc/libapache2-mod-jk/mod_jk-auto.conf" 
     workersConfig="/etc/libapache2-mod-jk/workers.properties"
     jkWorker="ajp13_worker" jkLog="/var/log/tomcat6/" />

The link to the "Tomcat docs website" in that section was quite helpful though.

After I'd figured it out, I read the README.Debian which pointed to the 
httpd_example_apache2.conf, but that explains the/a debian way to use 
"Custom mod_jk configuration". But in my situation I have both apache2 and
tomcat on the same machine, so I went for the auto-configure variant.

There are a couple of ways to fix this and I'll leave it up to the maintainers 
to choose which one(s).
1. Update libapache-mod-jk-doc to mention that auto-configure doesn't work as 
   described there and the user should use the custom configuration option. 
   Optionally mention the README.Debian there, since I/most people(?) expect
   to find all info in a -doc package. 
   Note 1: If it applies to tomcat6 as well, please mention that. If not please
   specify what to do when using tomcat6.
   Note 2: libapache2-mod-jk-doc would make for a more logical package name IMO.
2. Use debconf or sth like that to set the package up (including 
   workers.properties, see below for my workers.java_home value).
3. Extend the README.Debian, so it includes the configuration for 
auto-configure.
4. Provide a manpage for this package which explains how to set it up. For help 
   that's the first place to check I thought. It wasn't until later that I 
found 
   the README.Debian.

If you have question or need more info, don't hesitate to ask.

Regards,
  Diederik

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libapache2-mod-jk depends on:
ii  apache2-mpm-prefork [apache2] 2.2.15-5   Apache HTTP Server - traditional n
ii  apache2.2-common              2.2.15-5   Apache HTTP Server common files
ii  libc6                         2.10.2-8   Embedded GNU C Library: Shared lib

libapache2-mod-jk recommends no packages.

Versions of packages libapache2-mod-jk suggests:
ii  libapache-mod-jk-doc          1:1.2.28-2 Documentation of libapache2-mod-jk
ii  tomcat6                       6.0.26-1   Servlet and JSP engine

-- Configuration Files:
/etc/libapache2-mod-jk/workers.properties changed:
workers.tomcat_home=/usr/share/tomcat6
workers.java_home=/usr/lib/jvm/java-6-sun
ps=/
worker.list=ajp13_worker
worker.ajp13_worker.port=8009
worker.ajp13_worker.host=localhost
worker.ajp13_worker.type=ajp13
worker.ajp13_worker.lbfactor=1
worker.loadbalancer.type=lb
worker.loadbalancer.balance_workers=ajp13_worker


-- no debconf information



--- End Message ---
--- Begin Message ---
I'm hereby closing the bug as it was a user error and furthermore I have no 
interest in this package/bug anymore.

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to