Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats

[Vamegh Hedayati]

Hi,

I was also just testing it, all combinations I tried didn't work with
the built package you provided.  Miguel do you want access into my
server, just so you can verify ? I should also note my server is a xen
domu, but that should make absolutely no difference.

I will also try compiling it / building my own package and will let
you know if that works for me also.

All the best,


Vamegh

On 4 February 2011 22:49, Nelson Lago <nelson.lago at gmail.com> wrote:
> On Fri, Feb 4, 2011 at 7:39 PM, Miguel Landaeta <miguel at miguel.cc> wrote:
>> I prepared a new package for 1.2.31.
>> Would you please test it?
>
> Your binary package itself did not work, BUT I took your sources and
> created a debian package myself, and it works!
>
> I downloaded the files:
>
> libapache-mod-jk_1.2.31-0miguel1.dsc
> libapache-mod-jk_1.2.31-0miguel1.debian.tar.gz
> libapache-mod-jk_1.2.31.orig.tar.gz
>
> Then
>
> dpkg-source -x libapache-mod-jk_1.2.31-0miguel1.dsc
>
> then debian/rules binary
>
> I really do not understand why this happens, though. If the only
> important difference here was the OpenVZ kernel, how would this
> influence the compilation?
>
> If you also do not know what is going on, maybe this should be brought
> to the attention of the mainstream authors.
>