You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Thomas Bouron (JIRA)" <ji...@apache.org> on 2015/06/26 13:43:04 UTC

[jira] [Commented] (BROOKLYN-152) Enable Java options parameters to be configured in YAML

    [ https://issues.apache.org/jira/browse/BROOKLYN-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602735#comment-14602735 ] 

Thomas Bouron commented on BROOKLYN-152:
----------------------------------------

I checked the latest SNAPSHOT version and here is the list of entities that implement the {{brooklyn.entity.java.UsesJava}} interface:
* ActiveMQBroker
* BrooklynNode
* CassandraNode
* ControlledDynamicWebAppCluster
* DynamicWebAppCluster
* ElasticJavaWebAppService
* JavaWebAppService
* JavaWebAppSoftwareProcess
* JBoss6Server
* JBoss7Server
* Jetty6Server
* KafkaBroker
* KarafContainer
* LocalBrooklynNode
* QpidBroker
* Storm
* *TomcatServer* <= *Isn't what you are looking for?*
* UsesJmx
* VanillaJavaApp



> Enable Java options parameters to be configured in YAML
> -------------------------------------------------------
>
>                 Key: BROOKLYN-152
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-152
>             Project: Brooklyn
>          Issue Type: Improvement
>    Affects Versions: 0.7.0-SNAPSHOT
>            Reporter: Mike Zaccardo
>            Priority: Minor
>              Labels: configuration
>
> It would be good if options like "-Xms" were easier to control via config. If someone wanted a different Xmx then they'd currently probably have to write code to override the Java blueprint code.
> For example, maybe we should look at using UsesJava.JAVA_OPTS in Tomcat, and in a whole bunch of other entities.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)