M wrote: > > Remy Maucherat wrote: > > > > I don't see any major issues with 4.1.16, so I plan to tag 4.1.17 (which > > hopefully would be the next stable build) tomorrow after a few more > > minor tweaks. > > > > There was a report made against JK 2 immediately after 4.1.16 Beta was > > announced. Can someone confirm there's no major issue with JK ? > > I made the report and I can confirm that it still isn't working. > I'm using exacly the same configuration as for 4.1.12 and 4.1.14 both of > which work.
The workaround in Bug 15258 fixes our problem. We were indeed using the external ip address of the machine to connect and not the loopback address. (Multiple load balanced servers) Sorry I should have spotted the bind problem when I did a netstat... Many thanks. -- Regards, M Martin Sillence PR Newswire DL +44 (0)1865 78 5065 F +44 (0)1865 78 5100 W www.prnewswire.eu.com --------------------------------------- Any views or opinions are solely those of the author and do not necessarily represent those of PR Newswire Europe. The e-mail contents are intended only for addressee and may contain confidential and/or privileged material. If you are not the intended recipient, please do not read, copy, use or disclose this communication and notify the sender. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
