I am so sorry. You are correct.
Lance
Sent from my iPhone
> On Jun 20, 2016, at 12:13 PM, Rainer Jung wrote:
>
>> Am 20.06.2016 um 18:32 schrieb Campbell, Lance:
>> Neither of these options will work for me:
>> 1) no-jk is only supported for: "Starting with mod_jk
On 20.06.2016 18:32, Campbell, Lance wrote:
Neither of these options will work for me:
I don't see why not.
1) no-jk is only supported for: "Starting with mod_jk 1.2.6 for Apache 2.x and
1.2.19 for Apache 1.3"
So, you have Apache httpd 2.2.15 (which matches 2.x) and mod_jk 1.2.41, which
Am 20.06.2016 um 18:32 schrieb Campbell, Lance:
Neither of these options will work for me:
1) no-jk is only supported for: "Starting with mod_jk 1.2.6 for Apache 2.x and
1.2.19 for Apache 1.3"
So? You wrote your versions are
Apache 2.2.15
mod_jk 1.2.41
and isn't 1.2.41 >= 1.2.6? So the
Neither of these options will work for me:
1) no-jk is only supported for: "Starting with mod_jk 1.2.6 for Apache 2.x and
1.2.19 for Apache 1.3"
2) The urls that get sent to Tomcat are unkown. This is a dynamic content
driven site.
Any other options.
Thanks,
Lance
-Original
On Mon, Jun 20, 2016 at 9:14 AM, Campbell, Lance wrote:
> These are the versions of software I have to use. I cannot install other
> software:
>
>
>
> Apache 2.2.15
>
> mod_jk 1.2.41
>
> Tomcat 8.0.36
>
>
>
> Issue:
>
> We are looking at having a domain where all content