Bill,
Proviso: my knowledge of this area is limited. AFAIK, <domain>
could contain a system property HTTP_LISTENER_PORT and so could
<config>, and so could <server> and each could have a different
value. But see failure below where I tried...a bug?
Below is an XML snippet of a <config> from V2 domain.xml (irrelevant
portions elided
<config dynamic-reconfiguration-enabled="true" name="default-config">
<http-service>
<http-listener acceptor-threads="1" address="0.0.0.0"
blocking-enabled="false" default-virtual-server="server"
enabled="true" family="inet" id="http-listener-1" port="$
{HTTP_LISTENER_PORT}" security-enabled="false" server-name=""
xpowered-by="true">
</http-listener>
<http-listener acceptor-threads="1" address="0.0.0.0"
blocking-enabled="false" default-virtual-server="server"
enabled="true" family="inet" id="http-listener-2" port="$
{HTTP_SSL_LISTENER_PORT}" security-enabled="true" server-name=""
xpowered-by="true">
</http-listener>
</virtual-server>
</http-service>
<iiop-service client-authentication-required="false">
<iiop-listener address="0.0.0.0" enabled="true" id="orb-
listener-1" port="${IIOP_LISTENER_PORT}" security-enabled="false"/>
<iiop-listener address="0.0.0.0" enabled="true" id="SSL"
port="${IIOP_SSL_LISTENER_PORT}" security-enabled="true"> </iiop-
listener>
<iiop-listener address="0.0.0.0" enabled="true"
id="SSL_MUTUALAUTH" port="${IIOP_SSL_MUTUALAUTH_PORT}" security-
enabled="true">
</iiop-service>
...
<system-property name="HTTP_LISTENER_PORT" value="38080"/>
<system-property name="HTTP_SSL_LISTENER_PORT" value="38181"/>
<system-property name="JMS_PROVIDER_PORT" value="37676"/>
<system-property name="IIOP_LISTENER_PORT" value="33700"/>
<system-property name="IIOP_SSL_LISTENER_PORT" value="33820"/>
<system-property name="IIOP_SSL_MUTUALAUTH_PORT" value="33920"/>
<system-property name="JMX_SYSTEM_CONNECTOR_PORT" value="38686"/>
</config>
!!!!!!!!!!!!
So I tried this out. According to the DTD, <system-property> is
allowed in a <server>. But any attempt to use one results in an
error (works OK in a <config> though). This looks like a bug--the
DTD claims that <system-property> elements are OK, but startup
rejects them! Shown below I tried "XHTTP_LISTENER_PORT" to rule out
some confict with using "HTTP_LISTENER_PORT" in the <config>. No dice.
<server config-ref="server-config" lb-weight="100" name="server">
<system-property name="XHTTP_LISTENER_PORT" value="14080"/>
...
</server>
Starting Domain domain1, please wait.
Error refreshing ConfigContext:/gf/run/domains/domain1/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make
sure it is correct.
The content of element type "server" must match "(application-
ref*,resource-ref*,system-property*,property*)".
CLI156 Could not start the domain domain1.
Lloyd
On Feb 1, 2008, at 5:29 PM, Bill Shannon wrote:
>> System properties can exist in the following elements:
>> - <config>
>> - <server>
>> - <cluster>
>> - <domain>
>> So to resolve a system property, one cannot simply look in one
>> global place; MBeans contained (directly or indirectly) under one
>> <config> will resolve differently than those contained under
>> another config.
>
> Can you give me an example of where an attribute value will resolve
> differently depending on whether it's part of (e.g.) a <server>
> element vs. a <domain> element?
---
Lloyd L Chambers
lloyd.chambers_at_sun.com
Sun Microsystems, Inc