Mod_jk

I have a java application that currently runs on a standalone tomcat server. I have also had it running on apache using the mod_jk jakarta connector. Since the application needs to run on port 80, can i install the mod_jk on the http server for oracle????

Yes, you should be able to configure mod_jk to work with Oracle HTTP Server (OHS). OHS is based on Apache so any mod that works in Apache will work with OHS as well. You can follow the same instructions to configure it with OHS that you used to configure it with generic Apache.
Note that Oracle has following support policy regarding non-Oracle provided modules (including mod_jk):
Oracle provides technical support for modules included in the Oracle distribution (OHS). Oracle does not support modules obtained from any other source, including the Apache Software Foundation. Oracle HTTP Server will still be supported when non-Oracle provided modules are included. If it is suspected that the non-Oracle provided modules are contributing to reported problems, customers may be requested to reproduce the problems without those modules being included.
Thanks
Shail

Similar Messages

Mod_jk in combination with mod_rewrite

My question is wtf doesn't this work?
I'm using apache 1.3.27 and jboss-3.0.4_tomcat-4.1.12
mod_jk works fine. I tried adding in mod_rewrite and now when I go to a page that gets rewritten, the mod_jk doesn't SEE the new URI. Instead, it still uses the old URI. IS THIS PROBLEM NOT FIXED IN TOMCAT-4.1.12?? That's the only explanation I can think of. I have tried putting mod_jk before mod_rewrite and vice-versa. Here's another question...... when people say to put mod_jk before mod_rewrite in the httpd.conf file, do they mean put the entire set of directives before, or just the LoadModule statement? I've tried several ways.
Anyway, here is my httpd.conf file. Any suggestions to get this far-more-painful-than-it-needs-to-be process working? Is it a Servlet 2.2 requirement that these configs be hard to use?
ServerTokens Prod
# Based upon the NCSA server configuration files originally by Rob McCool.
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://www.apache.org/docs/> for detailed information about
# the directives.
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
# After this file is processed, the server will look for and process
# /etc/httpd/conf/srm.conf and then /etc/httpd/conf/access.conf
# unless you have overridden these with ResourceConfig and/or
# AccessConfig directives here.
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do not begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "/usr/local/apache" will be interpreted by the
# server as "/usr/local/apache/logs/foo.log".
### Section 1: Global Environment
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
# ServerType is either inetd, or standalone. Inetd mode is only supported on
# Unix platforms.
ServerType standalone
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation
# (available at <URL:http://www.apache.org/docs/mod/core.html#lockfile>);
# you will save yourself a lot of trouble.
# Do NOT add a slash at the end of the directory path.
ServerRoot "/etc/httpd"
# The LockFile directive sets the path to the lockfile used when Apache
# is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or
# USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left at
# its default value. The main reason for changing it is if the logs
# directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL
# DISK. The PID of the main server process is automatically appended to
# the filename.
LockFile /var/run/httpd.lock
# PidFile: The file in which the server should record its process
# identification number when it starts.
PidFile /var/run/httpd.pid
# ScoreBoardFile: File used to store internal server process information.
# Not all architectures require this. But if yours does (you'll know because
# this file will be created when you run Apache) then you must ensure that
# no two invocations of Apache share the same scoreboard file.
ScoreBoardFile logs/apache_runtime_status
# In the standard configuration, the server will process httpd.conf (this
# file, specified by the -f command line option), srm.conf, and access.conf
# in that order. The latter two files are now distributed empty, as it is
# recommended that all directives be kept in a single file for simplicity.
# The commented-out values below are the built-in defaults. You can have the
# server ignore these files altogether by using "/dev/null" (for Unix) or
# "nul" (for Win32) for the arguments to the directives.
#ResourceConfig conf/srm.conf
#AccessConfig conf/access.conf
# Timeout: The number of seconds before receives and sends time out.
Timeout 300
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
KeepAlive On
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
MaxKeepAliveRequests 100
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
KeepAliveTimeout 15
# Server-pool size regulation. Rather than making you guess how many
# server processes you need, Apache dynamically adapts to the load it
# sees --- that is, it tries to maintain enough server processes to
# handle the current load, plus a few spare servers to handle transient
# load spikes (e.g., multiple simultaneous requests from a single
# Netscape browser).
# It does this by periodically checking how many servers are waiting
# for a request. If there are fewer than MinSpareServers, it creates
# a new spare. If there are more than MaxSpareServers, some of the
# spares die off. The default values are probably OK for most sites.
MinSpareServers 8
MaxSpareServers 32
# Number of servers to start initially --- should be a reasonable ballpark
# figure.
StartServers 16
# Limit on total number of servers running, i.e., limit on the number
# of clients who can simultaneously connect --- if this limit is ever
# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a brake to keep a runaway server from taking
# the system with it as it spirals down...
MaxClients 256
# MaxRequestsPerChild: the number of requests each child process is
# allowed to process before the child dies. The child will exit so
# as to avoid problems after prolonged use when Apache (and maybe the
# libraries it uses) leak memory or other resources. On most systems, this
# isn't really needed, but a few (such as Solaris) do have notable leaks
# in the libraries. For these platforms, set to something like 10000
# or so; a setting of 0 means unlimited.
# NOTE: This value does not include keepalive requests after the initial
# request per connection. For example, if a child process handles
# an initial request and 10 subsequent "keptalive" requests, it
# would only count as 1 request towards this limit.
MaxRequestsPerChild 1000
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, in addition to the default. See also the <VirtualHost>
# directive.
#Listen 3000
#Listen 12.34.56.78:80
#Listen 80
# BindAddress: You can support virtual hosts with this option. This directive
# is used to tell the server which IP address to listen to. It can either
# contain "*", an IP address, or a fully qualified Internet domain name.
# See also the <VirtualHost> and Listen directives.
#BindAddress *
# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available before they are used.
# Please read the file http://httpd.apache.org/docs/dso.html for more
# details about the DSO mechanism and run `httpd -l' for the list of already
# built-in (statically linked and thus always available) modules in your httpd
# binary.
# Note: The order in which modules are loaded is important. Don't change
# the order below without expert advice.
# Example:
# LoadModule foo_module modules/mod_foo.so
#LoadModule mmap_static_module modules/mod_mmap_static.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
<IfDefine HAVE_BANDWIDTH>
LoadModule bandwidth_module modules/mod_bandwidth.so
</IfDefine>
<IfDefine HAVE_THROTTLE>
LoadModule throttle_module modules/mod_throttle.so
</IfDefine>
#LoadModule env_module modules/mod_env.so
LoadModule config_log_module modules/mod_log_config.so
#LoadModule agent_log_module modules/mod_log_agent.so
#LoadModule referer_log_module modules/mod_log_referer.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule mime_module modules/mod_mime.so
#LoadModule negotiation_module modules/mod_negotiation.so
LoadModule status_module modules/mod_status.so
LoadModule info_module modules/mod_info.so
#LoadModule includes_module modules/mod_include.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule dir_module modules/mod_dir.so
#LoadModule cgi_module modules/mod_cgi.so
#LoadModule asis_module modules/mod_asis.so
#LoadModule imap_module modules/mod_imap.so
#LoadModule action_module modules/mod_actions.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
# Thu 05 Jun 2003 10:12:02 AM PDT <[email protected]>
LoadModule jk_module /usr/local/lib/apache/mod_jk.so.ap1.3.27-eapi.rh72
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule access_module modules/mod_access.so
LoadModule auth_module modules/mod_auth.so
LoadModule anon_auth_module modules/mod_auth_anon.so
LoadModule db_auth_module modules/mod_auth_db.so
#LoadModule auth_any_module modules/mod_auth_any.so
#LoadModule dbm_auth_module modules/mod_auth_dbm.so
#LoadModule auth_ldap_module modules/mod_auth_ldap.so
#LoadModule mysql_auth_module modules/mod_auth_mysql.so
#LoadModule auth_pgsql_module modules/mod_auth_pgsql.so
#LoadModule digest_module modules/mod_digest.so
#LoadModule proxy_module modules/libproxy.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule example_module modules/mod_example.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
<IfDefine HAVE_PERL>
LoadModule perl_module modules/libperl.so
</IfDefine>
<IfDefine HAVE_PHP>
LoadModule php_module modules/mod_php.so
</IfDefine>
<IfDefine HAVE_PHP3>
LoadModule php3_module modules/libphp3.so
</IfDefine>
<IfDefine HAVE_PHP4>
LoadModule php4_module modules/libphp4.so
</IfDefine>
<IfDefine HAVE_DAV>
LoadModule dav_module modules/libdav.so
</IfDefine>
<IfDefine HAVE_ROAMING>
LoadModule roaming_module modules/mod_roaming.so
</IfDefine>
<IfDefine HAVE_SSL>
LoadModule ssl_module modules/libssl.so
</IfDefine>
<IfDefine HAVE_PUT>
LoadModule put_module modules/mod_put.so
</IfDefine>
<IfDefine HAVE_PYTHON>
LoadModule python_module modules/mod_python.so
</IfDefine>
# Thu 05 Jun 2003 10:12:02 AM PDT <[email protected]>
#Include /etc/httpd/conf/mod_jk.conf
<IfModule mod_jk.c>
JkWorkersFile /usr/local/jboss/server/default/conf/workers.properties
JkLogFile /var/tmp/jk.log
JkLogLevel warn
JkOptions ForwardKeySize ForwardURICompat -ForwardDirectories
JkMount /*.jsp ajp13
JkMount /servlet/* ajp13
JkMount /xml/servlet/* ajp13
</IfModule>
<IfModule mod_rewrite.c>
f
RewriteEngine on
RewriteLog /etc/httpd/logs/rewrite.log
RewriteLogLevel 1
RewriteRule ^/rwtest/(.*)$ /index.jsp [L]
</IfModule>
# Reconstruction of the complete module list from all available modules
# (static and shared ones) to achieve correct module execution order.
# [WHENEVER YOU CHANGE THE LOADMODULE SECTION ABOVE UPDATE THIS, TOO]
ClearModuleList
#AddModule mod_mmap_static.c
#AddModule mod_vhost_alias.c
<IfDefine HAVE_BANDWIDTH>
AddModule mod_bandwidth.c
</IfDefine>
<IfDefine HAVE_THROTTLE>
AddModule mod_throttle.c
</IfDefine>
#AddModule mod_env.c
AddModule mod_log_config.c
#AddModule mod_log_agent.c
#AddModule mod_log_referer.c
#AddModule mod_mime_magic.c
AddModule mod_mime.c
#AddModule mod_negotiation.c
AddModule mod_status.c
AddModule mod_info.c
#AddModule mod_include.c
AddModule mod_autoindex.c
AddModule mod_dir.c
#AddModule mod_cgi.c
#AddModule mod_asis.c
#AddModule mod_imap.c
#AddModule mod_actions.c
#AddModule mod_speling.c
#AddModule mod_userdir.c
AddModule mod_alias.c
AddModule mod_jk.c
AddModule mod_rewrite.c
AddModule mod_access.c
AddModule mod_auth.c
AddModule mod_auth_anon.c
AddModule mod_auth_db.c
#AddModule mod_auth_any.c
#AddModule mod_auth_dbm.c
#AddModule auth_ldap.c
#AddModule mod_auth_mysql.c
#AddModule mod_auth_pgsql.c
#AddModule mod_digest.c
#AddModule mod_proxy.c
#AddModule mod_cern_meta.c
AddModule mod_expires.c
AddModule mod_headers.c
#AddModule mod_usertrack.c
#AddModule mod_example.c
#AddModule mod_unique_id.c
AddModule mod_so.c
AddModule mod_setenvif.c
<IfDefine HAVE_PERL>
AddModule mod_perl.c
</IfDefine>
<IfDefine HAVE_PHP>
AddModule mod_php.c
</IfDefine>
<IfDefine HAVE_PHP3>
AddModule mod_php3.c
</IfDefine>
<IfDefine HAVE_PHP4>
AddModule mod_php4.c
</IfDefine>
<IfDefine HAVE_DAV>
AddModule mod_dav.c
</IfDefine>
<IfDefine HAVE_ROAMING>
AddModule mod_roaming.c
</IfDefine>
<IfDefine HAVE_SSL>
AddModule mod_ssl.c
</IfDefine>
<IfDefine HAVE_PUT>
AddModule mod_put.c
</IfDefine>
<IfDefine HAVE_PYTHON>
AddModule mod_python.c
</IfDefine>
# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
ExtendedStatus On
### Section 2: 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
# If your ServerType directive (set earlier in the 'Global Environment'
# section) is set to "inetd", the next few directives don't have any
# effect since their settings are defined by the inetd configuration.
# Skip ahead to the ServerAdmin directive.
# Port: The port to which the standalone server listens. For
# ports < 1023, you will need httpd to be run as root initially.
Port 80
## SSL Support
## When we also provide SSL we have to listen to the
## standard HTTP port (see above) and to the HTTPS port
<IfDefine HAVE_SSL>
Listen 80
Listen 443
</IfDefine>
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
# User/Group: The name (or #number) of the user/group to run httpd as.
# . On SCO (ODT 3) use "User nouser" and "Group nogroup".
# . On HPUX you may not be able to use shared memory as nobody, and the
# suggested workaround is to create a user www and use that user.
# NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
# when the value of (unsigned)Group is above 60000;
# don't use Group "#-1" on these systems!
User apache
Group apache
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents.
ServerAdmin [email protected]
# ServerName allows you to set a host name which is sent back to clients for
# your server if it's different than the one the program would get (i.e., use
# "www" instead of the host's real name).
# Note: You cannot just invent host names and hope they work. The name you
# define here must be a valid DNS name for your host. If you don't understand
# this, ask your network administrator.
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address (e.g., http://123.45.67.89/)
# anyway, and this will make redirections work in a sensible way.
# 127.0.0.1 is the TCP/IP local loop-back address, often named localhost. Your
# machine always knows itself by this address. If you use Apache strictly for
# local testing and development, you may use 127.0.0.1 as the server name.
#ServerName localhost
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "/usr/local/ourcompany/deploy/webroot"
# Each directory to which Apache has access, can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
# First, we configure the "default" to be a very restrictive set of
# permissions.
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
# This should be changed to whatever you set DocumentRoot to.
<Directory "/usr/local/ourcompany/deploy/webroot">
# This may also be "None", "All", or any combination of "Indexes",
# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".
# Note that "MultiViews" must be named explicitly --- "Options All"
# doesn't give it to you.
Options Indexes FollowSymLinks
# This controls which options the .htaccess files in directories can
# override. Can also be "All", or any combination of "Options", "FileInfo",
# "AuthConfig", and "Limit"
AllowOverride None
# Controls who can get stuff from this server.
Order allow,deny
Allow from all
</Directory>
# UserDir: The name of the directory which is appended onto a user's home
# directory if a ~user request is received.
# The path to the end user account 'public_html' directory must be
# accessible to the webserver userid. This usually means that ~userid
# must have permissions of 711, ~userid/public_html must have permissions
# of 755, and documents contained therein must be world-readable.
# Otherwise, the client will only receive a "403 Forbidden" message.
# See also: http://httpd.apache.org/docs/misc/FAQ.html#forbidden
#<IfModule mod_userdir.c>
# UserDir public_html
#</IfModule>
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#<Directory /home/*/public_html>
# AllowOverride FileInfo AuthConfig Limit
# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
# <Limit GET POST OPTIONS PROPFIND>
# Order allow,deny
# Allow from all
# </Limit>
# <LimitExcept GET POST OPTIONS PROPFIND>
# Order deny,allow
# Deny from all
# </LimitExcept>
#</Directory>
# DirectoryIndex: Name of the file or files to use as a pre-written HTML
# directory index. Separate multiple entries with spaces.
<IfModule mod_dir.c>
DirectoryIndex index.jsp index.html index.htm index.shtml index.php index.php4 index.php3 index.phtml index.cgi
</IfModule>
# AccessFileName: The name of the file to look for in each directory
# for access control information.
AccessFileName .htaccess
# The following lines prevent .htaccess files from being viewed by
# Web clients. Since .htaccess files often contain authorization
# information, access is disallowed for security reasons. Comment
# these lines out if you want Web visitors to see the contents of
# .htaccess files. If you change the AccessFileName directive above,
# be sure to make the corresponding changes here.
# Also, folks tend to use names such as .htpasswd for password
# files, so this will protect those as well.
<Files ~ "^\.ht">
Order allow,deny
Deny from all
Satisfy All
</Files>
# CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with each
# document that was negotiated on the basis of content. This asks proxy
# servers not to cache the document. Uncommenting the following line disables
# this behavior, and proxies will be allowed to cache the documents.
#CacheNegotiatedDocs
# UseCanonicalName: (new for 1.3) With this setting turned on, whenever
# Apache needs to construct a self-referencing URL (a URL that refers back
# to the server the response is coming from) it will use ServerName and
# Port to form a "canonical" name. With this setting off, Apache will
# use the hostname:port that the client supplied, when possible. This
# also affects SERVER_NAME and SERVER_PORT in CGI scripts.
UseCanonicalName On
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
<IfModule mod_mime.c>
TypesConfig /etc/mime.types
</IfModule>
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
DefaultType text/plain
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
# mod_mime_magic is not part of the default server (you have to add
# it yourself with a LoadModule [see the DSO paragraph in the 'Global
# Environment' section], or recompile the server and include mod_mime_magic
# as part of the configuration), so it's enclosed in an <IfModule> container.
# This means that the MIMEMagicFile directive will only be processed if the
# module is part of the server.
<IfModule mod_mime_magic.c>
# MIMEMagicFile /usr/share/magic.mime
MIMEMagicFile conf/magic
</IfModule>
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
HostnameLookups Off
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you do define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog logs/error_log
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you do
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and not in this file.
# CustomLog /var/log/httpd/access_log common
#CustomLog logs/access_log combined
# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#CustomLog logs/referer_log referer
#CustomLog logs/agent_log agent
# If you prefer a single logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#CustomLog logs/access_log combined
CustomLog "|/usr/sbin/cronolog -H /var/log/httpd/access /var/log/httpd/%Y/%m/access.%Y-%m-%d" combined
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (error documents, FTP directory listings,
# mod_status and mod_info output etc., but not CGI generated documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of: On | Off | EMail
ServerSignature EMail
# EBCDIC configuration:
# (only for mainframes using the EBCDIC codeset, currently one of:
# Fujitsu-Siemens' BS2000/OSD, IBM's OS/390 and IBM's TPF)!!
# The following default configuration assumes that "text files"
# are stored in EBCDIC (so that you can operate on them using the
# normal POSIX tools like grep and sort) while "binary files" are
# stored with identical octets as on an ASCII machine.
# The directives are evaluated in configuration file order, with
# the EBCDICConvert directives applied before EBCDICConvertByType.
# If you want to have ASCII HTML documents and EBCDIC HTML documents
# at the same time, you can use the file extension to force
# conversion off for the ASCII documents:
# > AddType text/html .ahtml
# > EBCDICConvert Off=InOut .ahtml
# EBCDICConvertByType On=InOut text/* message/* multipart/*
# EBCDICConvertByType On=In application/x-www-form-urlencoded
# EBCDICConvertByType On=InOut application/postscript model/vrml
# EBCDICConvertByType Off=InOut */*
# Aliases: Add here as many aliases as you need (with no limit). The format is
# Alias fakename realname
<IfModule mod_alias.c>
# Note that if you include a trailing / on fakename then the server will
# require it to be present in the URL. So "/icons" isn't aliased in this
# example, only "/icons/". If the fakename is slash-terminated, then the
# realname must also be slash terminated, and if the fakename omits the
# trailing slash, the realname must also omit it.
Alias /clipart/ "/usr/local/ourcompany/data/clipart/"
<Directory "/usr/local/ourcompany/data/clipart">
Options MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>
Alias /image_upload/ "/usr/local/ourcompany/data/labels/"
<Directory "/usr/local/ourcompany/data/labels">
Options MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>
# This Alias will project the on-line documentation tree under /manual/
# even if you change the DocumentRoot. Comment it if you don't want to
# provide access to the on-line documentation.
# Alias /manual/ "/etc/httpd/htdocs/manual/"
# <Directory "/etc/httpd/htdocs/manual">
# Options Indexes FollowSymlinks MultiViews
# AllowOverride None
# Order allow,deny
# Allow from all
# </Directory>
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "/var/www/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
</IfModule>
# End of aliases.
# Redirect allows you to tell clients about documents which used to exist in
# your server's namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Format: Redirect old-URI new-URL
# Directives controlling the display of server-generated directory listings.
<IfModule mod_autoindex.c>
# FancyIndexing is whether you want fancy directory indexing or standard
IndexOptions FancyIndexing NameWidth=*
# AddIcon* directives tell the server which icon to show for different
# files or filename extensions. These are only displayed for
# FancyIndexed directories.
AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip
AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*
AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/

Please note: I AM USING:
JkOptions ForwardKeySize ForwardURICompat -ForwardDirectories
And that's what's supposed to fix this problem in the first place, right??

Can't Build 64-bit Tomcat Connector Module (mod_jk)

I've been using the Tomcat Connector Module on my server so all requests can be logged by Apache, I only need to open port 80 on the firewall, and sites that use jsp with other technologies look more cohesive to the user.
In the past when a new version of the module was released I'd just download the source, unzip it, build it and instal it. Following the included instructions, "for the impatient Apache admins," I used:
./configure --with-apxs=/usr/sbin/apxs
to configure the build, then "make" and "sudo make install" to build and install the module.
This has always worked well (except it always installed the module in the wrong directory, which I never corrected because I liked to test the new module before I got rid of the old one), and when I moved to an Intel Mac, it continued to work. All the Apple-provided modules were universal binaries, but the i386 modules I built worked fine.
Now, with Leopard, we have a new, 64-bit Apache 2. I had been looking forward to working with Apache 2, and 64-bit is nice too, right? But now that it's here I'm not so sure.
My first disillusionment was that, when I downloaded the mod_jk source and built it using the same procedure I had been using, Apache refused to load the module, saying it had the wrong architecture. I checked the provided modules to see what architecture it wanted, and they were all universal binaries with four architectures, which didn't really narrow it down too much, but since I could rule out the ppc and ppc64 architectures, and the "wrong" one I built was i386, that left x86_64 as the only possibility.
Since I barely know what I'm doing, I'm not about to try anything crazy like building a universal binary (although I did try to follow this tutorial, but it didn't work for this project and his instructions didn't provide enough detail for me to even begin to figure out why), but I can't even figure out how to build a 64-bit binary.
I do have Xcode 3.0, so I should have the ability to build 64-bit binaries, and I have the new Java 1.6.0, which is also supposed to be 64-bit, so I should be race-ready, but when I run the configure script, specifying which Java version to use and which architecture to build:
./configure --with-apxs=/usr/sbin/apxs --with-arch-type=x86_64 --with-java-home=/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Hom e
I still end up with an i386 binary when the smoke clears, and in the log is a warning:
configure: WARNING: you should use --build, --host, --target
I'd be happy to do that if I had a clue what values to specify for them. Does anybody want to guess? Here's what it keeps taking for default values:
checking build system type... i386-apple-darwin9.2.2
checking host system type... i386-apple-darwin9.2.2
checking target system type... i386-apple-darwin9.2.2
I have a feeling I can't just substitute x86_64 for i386 (i.e. x86_64-apple-darwin9.2.2). The "x86_64-apple-darwin" part might be right, but I don't know about the 9.2.2. I've poked around the filesystem and gotten thoroughly confused. There seem to be all kinds of headers and compilers for i386 and x86_64 and something called i686, which seems to be related to x86_64 somehow, but I have no idea how to point the makefile to the right ones. I don't even know how or why it seems to be perfectly capable of finding everything it needs to build for i386 without my help, and even when I try to mislead it by suggesting I might want it to build for x86_64, it still unerringly finds all the i386 stuff and builds the module with them.
Since no one seems to provide Mac OS binaries of anything, it would be really nice to understand how to do this. I might even want to go crazy and build a 64-bit PostgreSQL or something like that, but if I can't even build a simple Apache module anymore, my hopes are fading.
If anybody is somehow clued-in on how all this stuff works, I'd really appreciate a brain-dump.
Thanks.

Thank you, that works for me too!
At first I was worried because, when I ran configure it said:
checking build system type... i386-apple-darwin9.3.0
checking host system type... i386-apple-darwin9.3.0
checking target system type... i386-apple-darwin9.3.0
But I went ahead and ran make anyway, and here's what I ended up with:
apache-2.0/mod_jk.so: Mach-O 64-bit bundle x86_64
which I could install and test. It even works!
Where did you find this information? I did a lot of digging too, but I must have been digging in the wrong places. I always like to go back to the source and see what else I can learn. Maybe then I can take another run at building a universal binary.

Mod_jk load balancing and JSESSIONID

I'm not very good with servers, in fact i'm a total newbie.
So I had someone explain to me how things work...
What I understood is this:
Apache runs on machine "Zeus" and it handles all the incoming http requests, mod_jk runs on that machine also.
mod_jk checks to see your sessionID if you've got one, and sends you to one of the 2 machine beneath it where tomcat runs. So if its the first time you log on it'll send you to the one with least load. Subsequent requests apache/mod_jk will check your JSESSIONID and send you to the corresponent machine. CORRECT?
Problem is, that in my case it doesnt.
It sends you randomly (or seemingly random) from one machine to the other thereby setting you a new SessionID each time you switch server. And this can be a nuisance.
Now I dont know if there is a problem with the server or with the JSP pages.
The only way, that i see, the JSP pages could cause this is if there is a method called to delete the sessionID. the only one I could see in the api is "session.invalidate()"
This however is nowhere to be found int JSP pages.
From the programming point of view what else could be causing it?
would session.removeAttribute("foo") do it?

The mod_jk has two methods of load balencing: round robin and sticky session
What you are seeing is the round robin where the mod_jk sends the request to the next server without looking at the session.
What you are looking for is sticky session and you need to configure this in the workers.properties file like this:
# Define workers using ajp13
worker.list=worker1,worker2,loadbalancer
worker.loadbalancer.type=lb
worker.loadbalancer.balanced_workers=worker1,worker2
worker.loadbalancer.sticky_session=true
# Set properties for worker1 (ajp13)
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=9009
worker.worker1.lbfactor=50
worker.worker1.cachesize=10
worker.worker1.cache_timeout=600
worker.worker1.socket_keepalive=1
worker.worker1.reclycle_timeout=300
# Set properties for worker2 (ajp13)
worker.worker2.type=ajp13
worker.worker2.host=localhost
worker.worker2.port=10009
worker.worker2.lbfactor=50
worker.worker2.cachesize=10
worker.worker2.cache_timeout=600
worker.worker2.socket_keepalive=1
worker.worker2.reclycle_timeout=300

Mod_jk receiving blocked requests?

Hello all,
this might not be the correct forum (excuses for that) but maybe someone has an idea what might be my problem here:
I just installed the mod_jk connector and switched logging to debug mode. When I open the log file I see the following:
[Tue Feb 14 18:00:23 2006] [27276:50880] [debug] map_uri_to_worker::jk_uri_worker_map.c (449): Attempting to map URI '/proxycheck.php' from 4 maps
[Tue Feb 14 18:00:23 2006] [27276:50880] [debug] map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context URI '/servlets-examples/*'
[Tue Feb 14 18:00:23 2006] [27276:50880] [debug] map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context URI '/jsp-examples/*.jsp'
[Tue Feb 14 18:00:23 2006] [27276:50880] [debug] map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context URI '/esriadmin/*'
[Tue Feb 14 18:00:23 2006] [27276:50880] [debug] map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context URI '/servlet/*'
[Tue Feb 14 18:00:23 2006] [27275:50880] [debug] map_uri_to_worker::jk_uri_worker_map.c (449): Attempting to map URI '/cgi-bin/iframe/autovol' from 4 maps
[Tue Feb 14 18:00:23 2006] [27275:50880] [debug] map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context URI '/servlets-examples/*'
[Tue Feb 14 18:00:23 2006] [27275:50880] [debug] map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context URI '/jsp-examples/*.jsp'
[Tue Feb 14 18:00:23 2006] [27275:50880] [debug] map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context URI '/esriadmin/*'
[Tue Feb 14 18:00:23 2006] [27275:50880] [debug] map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context URI '/servlet/*'
[Tue Feb 14 18:00:35 2006] [27272:50880] [debug] map_uri_to_worker::jk_uri_worker_map.c (449): Attempting to map URI '/ip.cgi' from 4 mapsover and over. What bothers me is the existence of the '/proxycheck.php',
'/cgi-bin/iframe/autovol' and '/ip.cgi' entries, since these are the same
requests at our apache firewall in mod_secure. These should have been
blocked, but seem to get through to the connector. So my questions are:
1. What does the 449 and 461 numbers mean?
2. Is there a security hole in our server?
3. Or is mod_jk just listening for requests on the same level as apache (in terms of hierarchy)?
If you know a forum that is better suited for this question, let me know, too.
Thanks for any reply and best regards
Jan Peters-Anders

The mod_jk has two methods of load balencing: round robin and sticky session
What you are seeing is the round robin where the mod_jk sends the request to the next server without looking at the session.
What you are looking for is sticky session and you need to configure this in the workers.properties file like this:
# Define workers using ajp13
worker.list=worker1,worker2,loadbalancer
worker.loadbalancer.type=lb
worker.loadbalancer.balanced_workers=worker1,worker2
worker.loadbalancer.sticky_session=true
# Set properties for worker1 (ajp13)
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=9009
worker.worker1.lbfactor=50
worker.worker1.cachesize=10
worker.worker1.cache_timeout=600
worker.worker1.socket_keepalive=1
worker.worker1.reclycle_timeout=300
# Set properties for worker2 (ajp13)
worker.worker2.type=ajp13
worker.worker2.host=localhost
worker.worker2.port=10009
worker.worker2.lbfactor=50
worker.worker2.cachesize=10
worker.worker2.cache_timeout=600
worker.worker2.socket_keepalive=1
worker.worker2.reclycle_timeout=300

Mod_jk.conf does not autogenerate

I can't get Tomcat 5 to generate the mod_jk.conf-auto file on start up.
I included:
</Service>
<ContextManager>
<ApacheConfig modjk="modules/mod_jk.so" jkconfig="conf/mod_jk.conf"/>
</ContextManager>
</Server>
in server.xml the conf file doesn't show up. Without it I can't get Apache to pass JSPs and servlets. What am I doing wrong?
pwp

1)Just download compiled module mod_jk.so (or mod_jk.dll for Windows)from apache.org site (in the jk_connectors);
2)Copy the file workers.properties to Apache/conf directory
3)Edit this file (especially the install path of Tomcat)
4)Include this file to httpd.conf adding lines:
<IfModule mod_jk.c>
JkMount /*.jsp ajp13
JkMount /*/servlet/ ajp13
JkWorkersFile conf/workers.properties
JkLogFile logs/mod_jk.log
JkLogLevel error
JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
</IfModule>
I think, it'll be usefull for You.

Mod_jk load error with Apache on OS X

Hello -
I have been running CF9 on OS X with a MacPorts install of Apache 2.2.21 with no issues as a "standalone" server installation. To get ready for CF10 I have ben trying to get CF10 configured with Apache. The specefic error I am getting when launching Apache is:
Cannot load /Applications/ColdFusion10/config/wsconfig/1/mod_jk.so into server: dlopen( /Applications/ColdFusion10/config/wsconfig/1/mod_jk.so, 10): Symbol not found: _apr_stat$INODE64\n Referenced from: /Applications/ColdFusion10/config/wsconfig/1/mod_jk.so\n Expected in flat namespace\n /Applications/ColdFusion10/config/wsconfig/1/mod_jk.so
I have done the following:
1. Recompiled Apache and forced a 64-bit compile
2. Uninstalled CF9
3. Uninstalld and reinsalled CF10
4. apxs is installed in /opt/local/apache2/bin (listed asa requirement in one of the documentation PDFs)
5. This is a Lion 10.7.3 with Xcode 4.2.1 currently installed
The error listed above is only a warning. Apache starts and still servers html files. I am a bit stumped and have no experience with Tomcat. Any help in finding a solution to this problem will be appreciated.
Thank you
Richard

Made progress -
Setting the max_packet_size seemed to start the 1st time CF10 admin process, just like it did with CF9 the 1st time we access the administrator. Then, it just went to a blank white screen.
mod_jk.log reports:
[error] ajp_process_callback::jk_ajp_common.c (1825): Unknow ajp protocol code: 0F
[error] ajp_process_callback::jk_ajp_common.c (2426): (cfusion) connecting to tomcat failed
Now: here is something interesting:
Look at the end of the URL when it 1st attempts to access administrator: It is index.cfm?configServer=true or index.cfm?serverConfig=true
By removing this it allows me to simply click on the "continue" option and low and behold the CF admin comes up.
I also have an issue with topnav.cfm reporting a 400 (Bad Request)
Quiting the browser and comming back to CF Admin displays the login page but after enter username and password I land on index.cfm and it goes no further.
Refreshing the page starts to rope in various admin componets.
Also, it will not process any simple cfm template reporting an internal server error.
Hopefully this has to do with this being a beta.

Mod_jk configure can't find apxs - ?!?

A developer has asked me to build an Apache 2 instance with mod_jk. This is on Solaris 8 with gcc 3.4.2. Apache2 builds, no problems.
First question: Why is mod_jk 2 deprecated while mod_jk 1 is actively being developed. Is it because the most recent versions are compatible with both Apache 1 and 2.
Second question: The configure script ignores with-apxs and with-apxs2:
./configure --with-apxs=/app/wsanders/SUNW/httpd-2.2.3/support/apxs
could not find /app/wsanders/SUNW/httpd-2.2.3/support/apxs
configure: error: You must specify a valid --with-apxs path
Permissions are fine:
$ ls -l /app/wsanders/SUNW/httpd-2.2.3/support/apxs
-rwxr-xr-x 1 wsanders wsanders 22597 Sep 26 13:54 /app/wsanders/SUNW/httpd-2.2.3/support/apxs
./configure --with-apxs2=/app/wsanders/SUNW/httpd-2.2.3/support/apxs
no apxs given
no apache given
Has anyone successfuly built this from source? Shoudl I be using mod_jk2?

We gave up and loaded the precompiled .so at the tomcat web site.
Surprisingly, it seems to work.

Mod_jk vs mod_cluster vs mod_proxy_ajp for Apache-based ATG Load Balacning

We are currently using mod_jk for load balancing our ATG Commerce Page Servers running on JBoss.
There are many nice things about mod_jk: ajp support, jkstatus adminstration ability, performance, etc.
However, there is a deficiency with mod_jk: It cannot accurately tell when a JBoss node is unavailable to serve pages! mod_jk only looks for a TCP ping response from JBoss, it does not have any ability to check a "health" page and understand situations like: App server out of memory, applicaiton not deployed even though the server is available, no threads available on the server, server shutting down or starting up, etc. From what I see, mod_jk will direct users to application servers that are in any one of these invalid states. Sending a user to a server that is not ready to serve content is not ideal.
Because of the issues with mod_jk, I have started looking at other alternatives that can:
1. More accurately determine the health of the application to load balance in a superior manner than mod_jk (i.e. tell if the app server is out of memory, deploying, going up/down, etc)
2. Meet or exceed the performance characteristics of mod_jk (which probably means continuing to use AJP)
3. Have an way to drain sessions of users on a particular node to allow for rolling deploys by taking specific Jboss nodes out of the cluster temporarily, applying the update, testing the update by directly accessing Jboss and then adding the node back into the cluster
mod_cluster looks to be a solution that fits these requirements. I think mod_proxy_ajp could also be used, but because it is not a jboss-specific apache module, some manual work would need to be done to have it read a healthcheck JSP page. I'm not sure if this is possible, but I think it might be.
Has anyone used mod_cluster or mod_proxy / mod_proxy_ajp with ATG? Any thoughts on this?
Right now I am leaning strongly towards mod_cluster. http://www.jboss.org/mod_cluster

Another important benefit of using mod_cluster is that it automatically registers new workers when they are added/removed from the cluster. Therefore its a better choice.
-Gaurav

MOD_JK configurations

Hi
We are facing problems with MOD_JK not redirecting to UI servers in case of fail over. We have 3 UI servers configured to MOD_JK. The three UI is pointed to individual MDEX.When one of the UI servers failed, the MOD_JK was not able to redirect the request to other servers. We see the log as "server not responding".
Is there any configuration that has to specifically enabled for server fail over? Also, does some one share idea on MOD PROXY? How far it will handle duing fail overs?
Below is the MOD_JK configuration
worker.server.type-ajp13
worker.server.lbfactor-1
worker.server.socket_keepalive-TRUE
worker.server.connection_pool_timeout-600
worker.vma-end-lb.type-lb
worker.vma-end-lb.balance_workers-server1,server2
worker.vma-end-lb.sticky_session-1
Tomcat Version-6
Any suggestions are welcome on how to configure the MOD_JK plugin.
Thanks
Pradeep

Your workers.properties config paste is unusual - it looks like you have a hyphen (-) instead of an equals sign (=) before each property value?
You might want to add a "redirect" directive to each worker [1]. Since you have enabled sticky-sessions, you may also want to check you have setup jvmRoute correctly [2].
Best
Brett
[1] http://tomcat.apache.org/connectors-doc/generic_howto/loadbalancers.html
[2] http://tomcat.apache.org/tomcat-6.0-doc/config/engine.html

Mod_jk for apache2, tomcat 5 and solaris 10

when i compile mod_jk in solaris 10 x86 box it shows following error:
/bin/bash /var/apache2/build/libtool --silent
--mode=compile gcc -I/usr/apache2/include -g -O2 -O
-xarch=386 -xchip=pentium -xspace -Xa -xildoff
-DSSL_EXPERIMENTAL -DSSL_ENGINE -DHAVE_APR
-I/usr/share/src/apache2/srclib/apr/include
-I/usr/share/src/apache2/srclib/apr-util/include -g
-O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS
-D_REENTRANT -I /usr/jdk/entsys-j2se/include -I
/usr/jdk/entsys-j2se/include/ -c jk_ajp12_worker.c -o
jk_ajp12_worker.lo
gcc: unrecognized option `-Xa'
gcc: unrecognized option `-KPIC'
gcc: language ildoff not recognized
gcc: jk_ajp12_worker.c: linker input file unused
because linking not done
mv: cannot access .libs/jk_ajp12_worker.lo
*** Error code 2
make: Fatal error: Command failed for target
`jk_ajp12_worker.lo'
Current working directory
/Desktop/jakarta-tomcat-connectors-1.2.14.1-src/jk/native/common
*** Error code 1
The following command caused the error:
set fnord $MAKEFLAGS; amf=$2; \
dot_seen=no; \
target=`echo all-recursive | sed s/-recursive//`; \
list='common apache-2.0'; for subdir in $list; do \
echo "Making $target in $subdir"; \
if test "$subdir" = "."; then \
dot_seen=yes; \
local_target="$target-am"; \
else \
local_target="$target"; \
fi; \
(cd $subdir && make $local_target) \
|| case "$amf" in *=*) exit 1;; k) fail=yes;; *)
exit 1;; esac; \
done; \
if test "$dot_seen" = "no"; then \
make "$target-am" || exit 1; \
fi; test -z "$fail"
make: Fatal error: Command failed for target `all-recursive'
i'm using apache 2 that is included in solaris 10 package, tomcat 5.5.17 and jakarta-tomcat-connectors-1.2.15.
please help.
mnio

Hi
i am also face problem in mod_jk for apache 2.2.0
I have done installation of apache 2.2.0 on Solaris 10_x86 .Problem in Solaris OS .But i face problem in tomcat connecter on Solaris 10_x86.
I make theses step in Solaris 10.
I download connector tomcat-connectors-1.2.25-src.tar.gz
# gunzip tomcat-connectors-1.2.25-src.tar.gz
# cd \tomcat-connectors-1.2.25-src\native
#./ buildconf.sh
# ./configure - - with - -apxs=/usr/local/apache2/bin/apxs after run this command make new file.File name is Makefile
Edit in Makefile and parameter -Wl,-brtl
Run make command for tomcat-connectors (mod_jk) compiling
bash-3.00# make
Making all in common
/usr/local/apr/build-1/libtool silent mode=compile gcc -I/usr/local/apache2/include -g -O2 -L/usr/local/lib -R/usr/local/lib -L/usr/local/ssl/lib -R/usr/local/ssl/lib -L/usr/openwin/lib -R/usr/openwin/lib -DHAVE_APR -I/usr/local/apr/include/apr-1 -I/usr/local/apr/include/apr-1 -g -O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE -I /include -I /include/ -c jk_ajp12_worker.c -o jk_ajp12_worker.lo
/usr/local/apr/build-1/libtool[384]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[384]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[709]: /usr/local/bin/sed: not found
*** Warning: inferring the mode of operation is deprecated.
*** Future versions of Libtool will require --mode=MODE be specified.
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1003]: /usr/local/bin/sed: not found
/usr/local/apr/build-1/libtool[1054]: /usr/local/bin/sed: not found
: compile: cannot determine name of library object from `'
*** Error code 1
make: Fatal error: Command failed for target `jk_ajp12_worker.lo'
Current working directory /export/home/apache/tomcat-connectors-1.2.25-src/native/common
*** Error code 1
The following command caused the error:
failcom='exit 1'; \
for f in x $MAKEFLAGS; do \
case $f in \
*=* | --[!k]*);; \
k) failcom='fail=yes';; \
esac; \
done; \
dot_seen=no; \
target=`echo all-recursive | sed s/-recursive//`; \
list='common apache-2.0'; for subdir in $list; do \
echo "Making $target in $subdir"; \
if test "$subdir" = "."; then \
dot_seen=yes; \
local_target="$target-am"; \
else \
local_target="$target"; \
fi; \
(cd $subdir && make $local_target) \
|| eval $failcom; \
done; \
if test "$dot_seen" = "no"; then \
make "$target-am" || exit 1; \
fi; test -z "$fail"
make: Fatal error: Command failed for target `all-recursive'
Please help me. My E-mail ID is [email protected]

Mod_jk child workerEnv in error state

We're using apache2, tomcat 5 on a freebsd 5.3 machine. Starting apache we're having some "mod_jk child workerEnv in error state 30" error in our httpd-error.log. The error state number is increasing. Any clues?
Cheers,
Marc

Hi Asif,
I can submit other programs successfully.
Please find the SQL extraction below:
Conflict Resolution Manager
1
1
Internal Manager
1
1
Scheduler/Prereleaser Manager
1
1
Standard Manager
8
8
PO Document Approval Manager
2
2
Receiving Transaction Manager
1
1
PA Streamline Manager
1
1
Inventory Manager
1
1
INV Remote Procedure Manager
1
1
Workflow Agent Listener Service
1
1
Workflow Mailer Service
1
1
Transportation Manager
0
0
WMS Task Archiving Manager
0
0
C AQCART Service
0
0
Session History Cleanup
1
1
UWQ Worklist Items Release for Crashed session
1
1
SFM Controller Service
0
0
SFM Order Queue Service
0
0
SFM Work Item Queue Service
0
0
SFM Fulfillment Actions Queue Service
0
0
SFM Fulfillment Element Ready Queue Service
0
0
SFM Event Manager Queue Service
0
0
SFM Inbound Messages Queue Service
0
0
SFM Timer Queue Service
0
0
SFM Application Monitoring Service
0
0
SFM SM Interface Test Service
0
0
OAM Metrics Collection Manager
1
1
Workflow Document Web Services Service
1
1
Marketing Data Mining Manager
0
0
Output Post Processor
1
1
FastFormula Transaction Manager
0
0
Regards,
Yuvraj

How-to install mod_jk in base Apache

I want to install mod_jk in Apache web server in order to forward requests to Tomcat. I tried to follow the instruction on the Apache page (WebserverHowTo) but there are too many gaps in what they say do and the default configuration of Apache on the Pro and/or Mini.
Is there a best practice for configuring Apache to forward requests to Tomcat? If so, what are the steps to enable it on OS X (10.5.6)?
Thanks in advance.

You may want to take a look at WebMin - besides an all-round great way to manage a server, it provides in depth tinkering w/Apache, albeit not so much for the faint-of-heart at times. You'll have loads of control over Apache, but deciding how to wield it can be intimidating until you've gotten settled in.
In any case, the things that are made easier far outweigh any learning curve on the few that demand more.

Adobe-modified mod_jk 1.2.37?

CF10, Update 11, RedHat Enterprise Linux 6.4, 64bit, Apache 2.2.15 (as bundled w/RHEL6.4).
I notice the Adobe-modified mod_jk is still based on the older 1.2.32 mod_jk connector. I noticed the source for this is also available now, and a trivial 5min attempt to apply the diff to the "pure" 1.2.37 has failed. I haven't really gone bit by bit through it all, although I suspect it wouldn't be too bad. It appears most of the changes are well labelled
: /* Below code changes are incorporated by Adobe Systems Incorporated
Given the slew of changes in the mod_jk ChangeLog from 1.2.32 to 1.2.37, I'd feel better if I could switch to that. But since the Adobe modifications (one of which is to support the "max_reuse_connections" in workers.properties) along w/our internal policy of using vendor-stuff for vendor-software, prevents me from simply attempting 1.2.37(pure) or 1.2.37-manually-patched-by-me.
Anyways, long story short, was wondering if/when Adobe might come out w/a 1.2.37 version of their modified mod_jk.
Thanks,
PH
PS
Tangentially, have been unsuccesful getting proxy_ajp to interface w/CF10. I have it working great under CF9. Just wondering.

- where did you get mod_jk module from ?
- did you know that web server 7 bundles tomcat like web container within and if you want to deploy web applications then you can do by simply placing the war file under <instance-root>/autodeploy directory
- web server 7 also comes with out of the box reverse proxy configuration that can act as front end and redirect requests to your back end tomcat or weblogic server etc.
these alternatives would be more appropriate...

64 bit mod_jk for Solaris 10

Hello
Has anyone been able to successfully compile a 64 bit version of mod_jk compatible with apache 2.2 on Solaris 10 (SPARC)
I got hold of Sun Studio 12 update 1 and tried to build a 64 bit version of apache before compiling mod_jk as a prereq. But running into various issues.
Was hoping if some one has the steps document that can be used as a reference.
Thanks

I am pretty confident that you need the 64 bit JVM for your platform, then you need to use the generic installer, this is based on how it has been done in prior releases.
So you can find the available JVM's for your platform here:
http://www.oracle.com/technology/software/products/ias/files/oracle%20fusion%20middleware%2011gr1%20(11%201%201%201%200)%20certification%20matrix.xls
In this case that would be Sun JVM 1.6.0_11+
OR
JRockit 6 Update 5 R27.6.2+
Then you should be able to run the generic installer here with that downloaded supported JDK:
http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html
I was not able to find anything specific on the documentation pages that described this process in detail, but you can always open a support case to get some assistance. I will check with the documentation team to see if that is going to be documented or already is.
If you look at the 10gR3 releases, it shows how the generic installer is used, for example:
http://e-docs.bea.com/platform/suppconfigs/configs/solaris/solaris10_103.html#104355

[SOLVED] Installing mod_jk through Aurbuild - Cannot find...

OLD TOPIC TITLE: Tomcat + mod_jk + Apache2 - need help!
Hi everyone,
I've been trying to install mod_jk but cannot get it compiled (compiling finishes fine but then there is no mod_jk.so file.. got me stumbled..). Annyway, I found a wiki for it on the ArchWiki (http://wiki.archlinux.org/index.php/Tomcat_and_Apache), but the download link is dead, and since the only thing I really need is the compiled "mod_jk.so", that's a pretty big problem. Could someone provide me with 'jk2-2.0.2.tar.bz2'? I can get the other file ('tomcat-4.1.27-1.tar.gz') from the net easily, but googling for the jk2 file doesn't show any results other than the ArchWiki page refering to it..
I really need this for my school project so any help would be greatly appreciated!
Thanks in advance,
Target

Hi mpie,
I greatly appreciate it that you take the time and effort to help me out here! I looked at the commands you where doing in the pkgbuild and tried some allready, I downloaded the source, extracted it and ran the commands as specified in the pkgbuild, the output:
(only errors)
appending configuration tag "F77" to libtool
checking for test... /bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/opt/gnome/bin:/opt/java/jre/bin:/opt/java/bin:/opt/qt/bin
checking for rm... /bin/rm
checking for grep... /bin/grep
checking for echo... /bin/echo
checking for sed... /bin/sed
checking for cp... /bin/cp
checking for mkdir... /bin/mkdir
checking for uint32_t... yes
checking size of uint32_t... 4
checking for u_int32_t... yes
checking size of u_int32_t... 4
checking for unsigned long... yes
checking size of unsigned long... 4
checking for unsigned int... yes
checking size of unsigned int... 4
checking for unsigned long long... yes
checking size of unsigned long long... 8
checking for unsigned longlong... no
checking size of unsigned longlong... 0
checking for snprintf... yes
checking for vsnprintf... yes
checking for flock... yes
checking for setsockopt in -lsocket... no
checking whether to use SO_RCVTIMEO with setsockopt()... yes
checking whether to use SO_SNDTIMEO with setsockopt()... yes
./configure: line 22428: /bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/opt/gnome/bin:/opt/java/jre/bin:/opt/java/bin:/opt/qt/bin: No such file or directory
checking for target platform... unix
no apache given
./configure: line 22749: /bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/opt/gnome/bin:/opt/java/jre/bin:/opt/java/bin:/opt/qt/bin: No such file or directory
./configure: line 22752: /bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/opt/gnome/bin:/opt/java/jre/bin:/opt/java/bin:/opt/qt/bin: No such file or directory
./configure: line 22759: /bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/opt/gnome/bin:/opt/java/jre/bin:/opt/java/bin:/opt/qt/bin: No such file or directory
./configure: line 22954: /bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/opt/gnome/bin:/opt/java/jre/bin:/opt/java/bin:/opt/qt/bin: No such file or directory
./configure: line 22966: /bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/opt/gnome/bin:/opt/java/jre/bin:/opt/java/bin:/opt/qt/bin: No such file or directory
./configure: line 22975: /bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/opt/gnome/bin:/opt/java/jre/bin:/opt/java/bin:/opt/qt/bin: No such file or directory
configure: creating ./config.status
config.status: creating Makefile
config.status: creating apache-1.3/Makefile
config.status: creating apache-1.3/Makefile.apxs
config.status: creating apache-2.0/Makefile
config.status: creating apache-2.0/Makefile.apxs
config.status: creating common/Makefile
config.status: creating common/list.mk
config.status: creating jni/Makefile
config.status: creating common/portable.h
config.status: executing depfiles commands
I dont think the pkgbuild can fix those errors, what do you think? I looked through the configure script at the lines that the error messages state, but I don't see anything obviously wrong there. I've also met all the requirements for installing mod_jk as far as I know. echo $? after running ./configure shows a '0' too, so I'm not too sure if those errors are that serious.. After running a 'make' though (it does work for pretty long..) it doesn't show any errors, but there is no mod_jk.so in apache-2.0 directory. Also, after running make the exit code is still 0, so I don't think it has an error anywhere.
Any hints on what might cause these errors would be greatly appreciated!
I've attached the full output of the configure command and the make command:
http://tempz0ne.homelinux.com/configure-output.txt
http://tempz0ne.homelinux.com/make-output.txt

Mod_jk

Similar Messages

Maybe you are looking for