2:
Re: mod_jk broken after upgrade to 2.4
By: Ernie Ghiglione
|
In response to 1 | 12/17/12 02:43 PM | ||
Hi Glen,
I think the error is that LAMS is bound to IP 210.48.33.60 and mod_jk is trying to connect to IP 127.0.0.1 For your server.log:
So LAMS has started as "run.sh -b 210.48.33.60", right? And mod_jk is configured to talk to LAMS on port 127.0.0.1/localhost:
So you can either start LAMS as run.sh -b 127.0.0.1 and that will ensure that mod_jk can talk via ajp to LAMS and you can do your apache proxying. Thanks Ernie Posted by Ernie Ghiglione |
|
||||||||||
|
Reply to first post on this page
Back to LAMS for Tech-Heads - General Forum