[JBoss JIRA] Created: (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
2:26 p.m.
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: http://www.atlassian.com/software/jira
9:54 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
[
https://issues.jboss.org/browse/AS7-1751?page=com.atlassian.jira.plugin.s...
]
Paul Ferraro commented on AS7-1751:
-----------------------------------
The recommended way to isolate clusters (i.e. oam vs traffic) in AS7 is to use either a
different multicast address, or different multicast port. By default these are
manipulated via the "jgroups-udp" socket binding.
This is conceptually different from multiple jgroups channels on the same server, since
these channel will use the same shared transport layer - and can be thought of as a single
"cluster".
But your point is still valid - you should have the option to manipulate the cluster name
independently from the cache-container name. Something like:
<cache-container name="web" ...>
<transport cluster="${CLUSTER}-web"/>
</cache-container>
Alternatively (since it might be annoying to have to do this within every cache container)
or perhaps additionally, we add this logic to the jgroups subsystem itself. Something
like:
<subsystem xmlns="urn:jboss:domain:jgroups:1.0" default-stack="udp"
cluster-prefix="${CLUSTER}-">
...
</subsystem>
Thoughts?
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: http://www.atlassian.com/software/jira
7:32 p.m.
New subject: [JBoss JIRA] Commented: (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
[
https://issues.jboss.org/browse/AS7-1751?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-1751:
---------------------------------------
Make sure this is implemented using jboss-dmr ModelNodes of ModelType.EXPRESSION and not
via system-property substitution logic in the parser.
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: http://www.atlassian.com/software/jira
3:13 p.m.
New subject: [JBoss JIRA] Commented: (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
[
https://issues.jboss.org/browse/AS7-1751?page=com.atlassian.jira.plugin.s...
]
Paul Ferraro commented on AS7-1751:
-----------------------------------
Brian,
I wasn't suggesting the default value of these attributes would contain expressions,
but that we would merely expose mechanisms for letting users customize their cluster
names. Users are free to populate them with system property expressions if they insist.
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: http://www.atlassian.com/software/jira
7:25 p.m.
New subject: [JBoss JIRA] Commented: (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
[
https://issues.jboss.org/browse/AS7-1751?page=com.atlassian.jira.plugin.s...
]
Dan Sirbu commented on AS7-1751:
--------------------------------
The idea would be the following to have the standalone.xml having ${VAR} for every
variable that makes sense to be defined at run-time.
standalone.conf - is the configuration file not only for standalone.sh BUT can also for
the standalone.xml via environment variables. Then one would have to take care to
configure one place and it get's pushed to the xml file.
AS7 already overwrites the standalone.xml file every time it starts at min. It also
provides a history. So it can be a 'nice' fit - in my opinion.
Think a bash shell managing an xml file ......
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: http://www.atlassian.com/software/jira
10:09 p.m.
New subject: [JBoss JIRA] Commented: (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
[
https://issues.jboss.org/browse/AS7-1751?page=com.atlassian.jira.plugin.s...
]
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: http://www.atlassian.com/software/jira
10:22 p.m.
New subject: [JBoss JIRA] Updated: (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
[
https://issues.jboss.org/browse/AS7-1751?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-1751:
------------------------------
Fix Version/s: 7.1.0.Beta1
(was: 7.0.2.Final)
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.1.0.Beta1
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: http://www.atlassian.com/software/jira
2:50 p.m.
New subject: [JBoss JIRA] (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
[
https://issues.jboss.org/browse/AS7-1751?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-1751:
------------------------------
Fix Version/s: 7.1.0.CR1
(was: 7.1.0.Beta1)
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.1.0.CR1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:07 p.m.
New subject: [JBoss JIRA] (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
[
https://issues.jboss.org/browse/AS7-1751?page=com.atlassian.jira.plugin.s...
]
Paul Ferraro reassigned AS7-1751:
---------------------------------
Assignee: Richard Achmatowicz (was: Paul Ferraro)
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: Richard Achmatowicz
Fix For: 7.1.0.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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:07 p.m.
New subject: [JBoss JIRA] (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
[
https://issues.jboss.org/browse/AS7-1751?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz updated AS7-1751:
-------------------------------------
Fix Version/s: 7.1.1.Final
(was: 7.1.0.Final)
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: Richard Achmatowicz
Fix For: 7.1.1.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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:13 p.m.
New subject: [JBoss JIRA] (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
[
https://issues.jboss.org/browse/AS7-1751?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-1751:
----------------------------------
Priority: Blocker (was: Major)
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: Richard Achmatowicz
Priority: Blocker
Fix For: 7.1.1.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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:30 p.m.
New subject: [JBoss JIRA] (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
[
https://issues.jboss.org/browse/AS7-1751?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-1751:
---------------------------------------
A "name" attribute that really just reflects an element in the resource address
should not support expressions. The names of resources cannot be set via expressions.
In general, if there's a legit question whether an expression should be allowed for a
given configuration item, don't support it. There's no requirement to support
expressions everywhere. It's easier to add support later if there is a legitimate use
case, as adding support is not an incompatible change. Once an expression is supported,
removing it *is* an incompatible change.
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: Richard Achmatowicz
Priority: Blocker
Fix For: 7.1.1.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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:31 a.m.
New subject: [JBoss JIRA] (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
[
https://issues.jboss.org/browse/AS7-1751?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-1751:
------------------------------------------
Discussed this issue with Paul and we decided to do the following:
(i) define a new attribute of the cache-container transport element called cluster which
allows specifying a name for the underlying JGroups channel used to support the cache
container:
{noformat}
<cache-container name="web" ...>
<transport cluster="some-cluster-name" .../>
</cache-container/>
{noformat}
(ii) allow the following attributes to allow expressions:
JGroups subsystem: default-stack, site, rack, machine
Infinispan subsystem: default-cache-container, default-cache, cluster
In this instance, we chose the minimal set of attributes which would be cluster / machine
dependent.
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: Richard Achmatowicz
Priority: Blocker
Fix For: 7.1.1.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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4643
days inactive
4815
days old
12 comments
6 participants
participants (6)
-
Brian Stansberry (JIRA) -
Dan Sirbu (JIRA)
-
Jason Greene (JIRA)
-
Jason Greene (Updated) (JIRA)
-
Paul Ferraro (JIRA)
-
Richard Achmatowicz (JIRA)