Bug 232352 - Undocumented NamingContext properties
Undocumented NamingContext properties
Product: JBoss Enterprise Application Platform 4
Classification: JBoss
Component: doc-Server_Configuration_Guide (Show other bugs)
All All
medium Severity low
: ---
: ---
Assigned To: Russell Dickenson
: Documentation
Depends On:
  Show dependency treegraph
Reported: 2007-03-14 17:34 EDT by Brian Stansberry
Modified: 2014-05-02 00:22 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-05-02 00:22:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian Stansberry 2007-03-14 17:34:23 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
socket to

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.
Comment 1 Brian Stansberry 2007-03-14 17:41:03 EDT
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232354 is the related
clustering docs issue.
Comment 2 Michael Hideo 2007-06-06 00:49:52 EDT
Adding 'cc ecs-dev-list@redhat.com for team coverage
Comment 4 Joshua Wulf 2007-06-22 04:16:26 EDT
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.

Comment 5 Michael Hideo 2007-10-22 22:48:44 EDT
Removing automation notification
Comment 6 Michael Hideo 2008-01-17 00:49:21 EST
Mass Re-Assignment to Vinu for vetting. Investigate and migrate to JIRA if

Note You need to log in before you can comment on or make changes to this bug.