Bug 1100602
| Summary: | mod_jk 1.2.40 IPv6 support does not work on Windows | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Web Server 2 | Reporter: | Libor Fuka <lfuka> | ||||||
| Component: | mod_jk | Assignee: | Mladen Turk <mturk> | ||||||
| Status: | CLOSED EOL | QA Contact: | Libor Fuka <lfuka> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 2.1.0 | CC: | dmasirka, jclere, jdoyle, jstefl, myarboro, pslavice, rsvoboda, weli | ||||||
| Target Milestone: | ER03 | ||||||||
| Target Release: | 2.1.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Windows | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
Previously, mod_jk 1.2.40 IPv6 support did not work on Microsoft Windows as APR resolves addresses on Microsoft Windows differently.
This issue is fixed in JBoss Enterprise Server 2.1. The mod_jk 1.2.40 IPv6 support now works with Microsoft Windows.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2019-06-13 08:03:57 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 898577 [details]
httpd error log
It works if you add prefer_ipv6=1 to worker, eg. worker.nodeX.prefer_ipv6=1 Seems this has to do with how APR resolves addresses on Windows. Please create upstream bug report for mod_jk and link it here. I'll try to create some patch that would bypass those APR differences. It works well after setting properties worker.nodeX.prefer_ipv6=1 on Windows. Two possible solutions: 1. Fix upstream - mod_jk behaviour should be the same on all platforms (without set worker.nodeX.prefer_ipv6=1) 2. Document this mod_jk property in EWS 2.1.0 documentation Mladen will fix it upstream - confirmed in discussion. Created upstream bugzilla https://issues.apache.org/bugzilla/show_bug.cgi?id=56565 Fixed upstream. I'll apply a patch to our mod_jk. *** Bug 901010 has been marked as a duplicate of this bug. *** This is fixed with ER2. Please verify. Its still the same in ER2 on windows. I see the same errors in mod_jk.log: [Thu Jun 12 00:21:33 2014][5936:5408] [error] ajp_validate::jk_ajp_common.c (2748): worker worker1 can't resolve tomcat address ::1 [Thu Jun 12 00:21:36 2014][5936:5408] [error] ajp_validate::jk_ajp_common.c (2748): worker worker2 can't resolve tomcat address ::1 Yeah, sorry, my bad. Seems the patch was not applied to ER2 after all. Rebuild with correct patch http://download.devel.redhat.com/brewroot/packages/mod_jk/1.2.40/3.win6/win/ You can just replace mod_jk.so from those .zip files. It'll be part of ER3, but if you can check it would give some time to fix it. I retest i686 build from comm#10 on Win2008 32-bit and it works! Verified with EWS 2.1.0-ER3 on MS Windows 2008 (i686, x86_64), 2008R2, 2012 added doc text. |
Created attachment 898575 [details] mod_jk.log Description of problem: mod_jk 1.2.40 IPv6 support does not work on Windows. mod_jk IPv6 support on RHEL and Solaris work well. see attched mod_jk.log and httpd error.log Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: