Bug 57049 - Engine jvmRoute documentation should mention the system property that can affect its value
Summary: Engine jvmRoute documentation should mention the system property that can aff...
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 8
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 8.0.x-trunk
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ----
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-02 14:07 UTC by Christopher Schultz
Modified: 2014-10-02 14:41 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Schultz 2014-10-02 14:07:51 UTC 
To facilitate dynamic deployments where a jvmRoute is set e.g. using a system property, an empty jvmRoute attribute should behave the same as having no jvmRoute attribute set.
Comment 1 Christopher Schultz 2014-10-02 14:25:07 UTC 
Hmm... while looking at the code to propose a patch, I found that the StandardEngine constructor actually looks for a "jvmRoute" system property.

This enhancement might not need to exist.

I checked, and the jvmRoute system property is properly-documented in the "System Properties" page of the configuration reference.

It might help to mention this in the <Engine> documentation for jvmRoute. Changing to a documentation bug.
Comment 2 Christopher Schultz 2014-10-02 14:36:48 UTC 
Fixed in r1628984. Will be in Tomcat 8.0.15's documentation.
Comment 3 Christopher Schultz 2014-10-02 14:41:22 UTC 
Fixed in 7.0.x branch in r1628985. Will be in Tomcat 7.0.57's documentation.