[jboss-cvs] JBossAS SVN: r88987 - projects/docs/community/5/Clustering_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun May 17 16:23:55 EDT 2009
Author: galder.zamarreno at jboss.com
Date: 2009-05-17 16:23:54 -0400 (Sun, 17 May 2009)
New Revision: 88987
Modified:
projects/docs/community/5/Clustering_Guide/en-US/Clustering_Guide_JNDI.xml
Log:
[JBNAME-27] Added documentation for global jndi discovery disable system property.
Modified: projects/docs/community/5/Clustering_Guide/en-US/Clustering_Guide_JNDI.xml
===================================================================
--- projects/docs/community/5/Clustering_Guide/en-US/Clustering_Guide_JNDI.xml 2009-05-17 14:17:57 UTC (rev 88986)
+++ projects/docs/community/5/Clustering_Guide/en-US/Clustering_Guide_JNDI.xml 2009-05-17 20:23:54 UTC (rev 88987)
@@ -456,6 +456,21 @@
</listitem>
</itemizedlist>
+
+ <para>Since AS 5.1.0.GA, there's a new system property called <literal>jboss.global.jnp.disableDiscovery</literal>
+ that controls autodiscovery behaivour at the client VM level and it can take <literal>true</literal> or
+ <literal>false</literal> (default value) boolean values. The system property works in such way that if
+ missing or it's set to <literal>false</literal>, default auto discovery behaivour will be used.
+ If set to <literal>true</literal>, the following can happen:</para>
+ <itemizedlist>
+ <listitem>If jnp.DisableDiscovery not present when context is created, auto discovery will
+ not be attempted.</listitem>
+ <listitem>If jnp.DisableDiscovery is present when context is created and this is set to true,
+ auto discovery will not be attempted.</listitem>
+ <listitem>If jnp.DisableDiscovery is present when context is created and is set to false,
+ the global auto discovery system property is ignored and auto discovery will be attempted.
+ This enables global discovery client VM setting to be overriden.</listitem>
+ </itemizedlist>
</section>
More information about the jboss-cvs-commits
mailing list