Red Hat Bugzilla – Bug 232352
Undocumented NamingContext properties
Last modified: 2014-05-02 00:22:31 EDT
The following properties accepted by org.jnp.interfaces.NamingContext are not
covered in the documentation:
jnp.socketFactory -- The javax.net.SocketFactory impl to use for the bootstrap
jnp.localAddress -- The local (client-side) address to bind the connected
bootstrap socket to
jnp.localPort -- The local (client-side) port to bind the connected bootstrap
jnp.useRelativeName -- A flag indicating the style of names passed to
javax.naming.spi.NamingManager methods. True for api expected relative names, false
for absolute names as used historically by the jboss naming implementation.
jnp.maxRetries -- An integer that controls the number of connection retry
attempts that will be made on the initial connection to the naming server. This
only applies to ConnectException failures. A value <= 1 means that only one
attempt will be made. Default is one.
jnp.discoveryTTL -- The time-to-live for multicast discovery packets
The first five belong in the general discussion of
org.jnp.interfaces.NamingContext (e.g. Section 2.3.2 of The JBoss 4 Application
Server J2EE Reference), while the last belongs in the subsequent clustering
discussion (Section 2.3.3 of the J2EE Reference as well as Section 1.2.2 of The
JBoss 4 Application Server Clustering Guide).
I'll create a separate issue for getting jnp.discoveryTTL in the clustering docs.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232354 is the related
clustering docs issue.
Adding 'cc firstname.lastname@example.org for team coverage
I've updated the clustering documentation and the associated bug. The JBoss 4
Server J2EE Reference doesn't ship with JBEAP 4.2, so this bug may need to be
refiled against a different component / project.
Removing automation notification
Mass Re-Assignment to Vinu for vetting. Investigate and migrate to JIRA if