Hmmm. Googling on the jk_module found an IBM MTU for 6.1 that specifically says:

"5.7.3 Tomcat

Tomcat servers will no longer be shipped as part of the 5761-DG1 product
in V6R1. Remove the following directive from customer configurations:

LoadModule jk_module /QSYS.LIB/QHTTPSVR.LIB/QZTCJK.SRVPGM

In addition, unless an open source version of Tomcat with the Tomcat
connector is used instead, remove the following directives from customer
configurations:

JkAsfTomcat
JkLogFile
JkLogLevel
JkMount
JkMountCopy
JkWorkersFile

If an open source version of the Tomcat connector is used, the
information above regarding third-party modules applies to the module
that is loaded into the HTTP server.


Now the interesting part is that this is talking about Tomcat but the directive and module are used in Apache, not Tomcat so the MTU is a little confusing.

So it looks like the AJP connector doesn't work on 6.1 but I'll keep digging.

Pete Helgren
Value Added Software, Inc
www.asaap.com
www.opensource4i.com


On 4/15/2011 6:25 AM, Jim Oberholtzer wrote:
A little bit of further looking, I could not find the object QZTCJK of
any type on any of our systems. Are you sure the module name is right?

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 4/15/2011 6:51 AM, Jim Oberholtzer wrote:
Pete:

The error is logged in the job log of the server:

From module . . . . . . . . : QZSRSNDM
From procedure . . . . . . : sendMessageToJobLog_CCSID
Statement . . . . . . . . . : 27
To module . . . . . . . . . : MOD_SO
To procedure . . . . . . . : load_module
Statement . . . . . . . . . : 58
Message . . . . : The specified HTTP Server module cannot be added with
LoadModule.
Cause . . . . . : The HTTP Server module
/QSYS.LIB/QHTTPSVR.LIB/QZTCJK.SRVPGM specified on the LoadModule
directive
cannot be added into the server. The module name may be misspelled or
another error may have occured while attempting to load the module.
For
more information, see the previous messages in the job log.
Recovery . . .
: This message may be a result of attempting to load a module that
is not
compatible with the version of the HTTP Server (powered by Apache)
currently
running on the system. The version of the HTTP Server (powered by
Apache)
is 20051115 . Contact the provider of the module for service. Technical
description . . . . . . . . : If you are the developer of the
module, look
at member AP_RELEASE in file QHTTPSVR/H on the system the module was
built
on. The AP_RELEASE member contains the version number used by the
module.
If the version number does not match the version of the HTTP Server
(powered
by Apache), rebuild the module with the appropriate version of the header
file. After performing the appropriate recovery, start the server again.

It won't start on V7 either.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 4/14/2011 7:25 PM, Pete Helgren wrote:
I want to frontend Tomcat with my Zend server Apache instance and I
can't seem to get it to work (works like a champ in Windows). I
configured the workers.properties file and the uriworkmap.properties
file and added the following directives to httpd.conf.

LoadModule mod_jk /QSYS.LIB/QHTTPSVR.LIB/QZTCJK.SRVPGM


JkWorkersFile conf/workers.properties
JkMountFile conf/uriworkermap.properties

The Zendsvr Apache instance fails to start and also very unhelpfully
doesn't log anything anywhere I can see, so I can't tell what Zendsvr
Apache instance is cranky about. Using the directive listing doesn't
show any "JK" directives at all. Is this not supported on IBM i 6.1?
If I only attempt to load the module, it also won't start.

Anybody using AJP connectors on i?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.