System property expansion with Multiplexer

[brian.stansberry]

One multiplexer integration problem I've noticed is using the JBoss system property expansion technique doesn't work with multiplexer-stacks.xml. E.g.

<UDP
 mcast_port="45588"
 mcast_addr="${jboss.partition.udpGroup:228.1.2.3}"...

v will fail on setting up the protocol stack.

Haven't thought about it; perhaps the solution is trivial.


On a tangential topic, if we can solve the above problem, one good thing the multiplexer provides is the ability to set the multicast port via a system property and/or startup switch. That will make life easier for admins needing to segregate clusters. Wasn't practical before due to the numerous Channels deployed in a server.

[belaban]

I thought variable expansion/substitution is a feature of JBoss, the subsystem parsing the config XML files ?

[brian.stansberry]

(We discussed offline; following is for other interested people).

Issue is the multiplexer-stacks.xml file is read and parsed by JGroups directly, bypassing the AS deployer code that does the substitution.

Plus, there's nothing AS specific about system property substitution; seems like a useful feature for JGroups outside the AS.

Created a JIRA: http://jira.jboss.com/jira/browse/JGRP-272

[belaban]

This will probably go into JGroups 2.4

[brian.stansberry]

JIRA for the idea of having a startup switch to set the multicast port is at http://jira.jboss.com/jira/browse/JBAS-3537 .

[starksm64]

JBossXB and hence the MC configuration via the bean deployer also does property substitution.