]
Brian Stansberry commented on AS7-1751:
---------------------------------------
My comment above wasn't meant to discourage doing this or to argue for or against
doing it by default. Paul, I'm just pointing out the proper way to implement this. The
core management layer has a standard way of dealing with expressions (i.e. system property
substitution) in configuration values, and that should be used. But it's not used a
lot, so people may not know about it and instead roll their own solution.
infinispan setup to support environment variables within the
standalone.xml file
--------------------------------------------------------------------------------
Key: AS7-1751
URL:
https://issues.jboss.org/browse/AS7-1751
Project: Application Server 7
Issue Type: Enhancement
Components: Clustering
Affects Versions: 7.0.1.Final
Reporter: Dan Sirbu
Assignee: Paul Ferraro
Fix For: 7.0.2.Final
When I kickstart the inifispan subsystem by using the start=EAGER option, saw that there
are multiple "clusters" that get kickstarted as:
GMS: address=traffic_instance_PL-3-31315, cluster=hibernate
........................................, cluster=web
and others.
Now, if I do have mutliple blades e.g. SC-1, SC-2, PL-3, PL-4 and then I would like to
define two clusters e.g. "oam" , "traffic" where "oam"
should be assigned for SC-x and "traffic" for PL-x, then I will certainly need
to go in the standalone-ha.xml file and change all the "cache-container name"
entries in order to have "oam" cluster distinguished from "traffic"
cluster, right ?
If so, it would be better if for example I could pass an jvm option via e.g.
-DCLUSTER="oam" and then in the standalone-ha.xml file have this set as:
"cache-container name=${CLUSTER}-"
In this way, I can obtain a dynamic config at runtime.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: