Red Hat Bugzilla – Bug 852699
DOC: 22.214.171.124. Basic Configuration and EAP6 subsystems
Last modified: 2012-11-08 17:10:51 EST
126.96.36.199. Basic Configuration
EAP6 subsystem configuration in the scope of EWS?
We talk Tomcat6/7 here...
Adding Jean-Frederic for a pointer to information about this.
Keep that part. EWS can be used as a frond-end for EAP6 therefore it must be documented and tested.
In light of Jean-Frederic's clarification in c#2, closing this as NOTABUG. Michal, please open it back up and comment if you have any further issues related to this particular bug.
Using this bug to track addition of 3.3 - Configuring Apache Tomcat to work with mod_jk hence reopened.
3.3 Configuring Apache Tomcat to work
Tomcat is already prepared to use mod_jk. In conf/server.xml you have:
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />
Added the following text:
3.3. Configuring Apache Tomcat to Work with mod_jk
Tomcat is configured to use mod_jk by default. Specifically, refer to the conf/server.xml file, which contains the following code for this purpose:
<connector port="8009" protocol="AJP/1.3" redirectPort="8443" />
This default Tomcat configuration is ready for immediate use with mod_jk.
Available for QE here:
Just one thing, I am missing info about jvmRoute.
Make sure that jvmRoute attribute is set at your Engine <Engine name="Catalina" jvmRoute="node01" > and that the jvmRoute attribute value matches your worker name in workers.properties
Information is added.
This addition can be verified here:
I noticed, that we use naming of first worker as "node1", please change:
node01 -> node1
Fixed. This bug will be set to ON_QA once this change appears on the stage.
This bug is set to CLOSED CURRENT RELEASE to indicate that this fix is now released and available at access.redhat.com.