tracker issue : CF-3494405

select a category, or use search below
(searches all categories and all time range)

Separate JVM config for "coldfusion status|stop"

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Jan Ruusuvuori / Jan Ruusuvuori (jruusu)

Created: 02/01/2013

Components: Web Container (Tomcat)

Versions: 10.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: Final / 288696

Priority/Frequency: Trivial / Unknown

Locale/System: English / Linux All

Vote Count: 3

The server management script bin/coldfusion should apply a separate, lightweight JVM configuration when running the operations "status" and "stop".

Applying the actual server process JVM parameters from jvm.config to those operations is unnecessary and in many cases wasteful. It makes no sense to allocate several gigabytes of heap just to check the status of a CF server. In a low memory situation it may even prevent the operations from running at all.

Specifying two separate JVM argument strings in eg. jvm.config would be good; one for "server" and one for "management".

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3494405


External Customer Info:
External Company:  
External Customer Name: jruusu
External Customer Email:  
External Test Config: My Hardware and Environment details:



Stock Tomcat handles this with CATALINA_OPTS.
Vote by External U.
16412 | May 30, 2013 08:26:08 AM GMT
Using the same set of JVM args also causes an issue if you use arguments to enable SNMP or JMX.
Comment by External U.
16410 | May 30, 2013 08:27:45 AM GMT
There's no need to use a bazooka to take out a mosquito here. As pointed out, other configurations keep equivalent tasks lightweight.
Vote by External U.
16413 | May 30, 2013 08:45:02 AM GMT
i agree with Nathan and serdman
Vote by External U.
16414 | May 30, 2013 02:32:04 PM GMT
Makes sense and we should do it.
Comment by Rupesh K.
16411 | June 09, 2013 11:55:27 PM GMT