GlassFish - World's first Java EE 7 Application Server


This page provides links to review drafts of new and changed documentation for the IIOP Load Balancing and Failover project as listed in the IIOP Load Balancing and Failover Documentation Plan.

Mandatory reviewers for each item are listed in each section.

Changes to existing documentation since the last release are marked with change bars. No changes are marked in new documentation.

Please provide your feedback by adding a comment to this page. To simplify the processing of your comments, please add your comments in the format in the sample comment. Review existing comments to see known issues and avoid duplicates.

Changes to Books

High Availability Administration Guide Changes

Section Documentation Impact Reviewers
Chapter 11. RMI-IIOP Load Balancing and Failover Moderate Ken Cavanaugh
Cheng Fang

Application Development Guide Changes

Section Documentation Impact Reviewers
To Access an EJB Component From an Application Client Minor Ken Cavanaugh

Application Deployment Guide Changes

Section Documentation Impact Reviewers
The sun-ejb-jar.xml File Minor Cheng Fang
per-request-load-balancing New Cheng Fang

Changes to Online Help

Changes to Man Pages

Mandatory reviewers in addition to the reviewers that are listed in the table are as follows:

  • Gopal Jorapur
  • Tom Mueller
Man Page Name and Section Documentation Impact Reviewers
create-iiop-listener(1) Minor Ken Cavanaugh
delete-iiop-listener(1) Minor Ken Cavanaugh
list-iiop-listeners(1) Minor Ken Cavanaugh

Attachments:
create-iiop-listener.1.pdf (application/pdf)
delete-iiop-listener.1.pdf (application/pdf)
list-iiop-listeners.1.pdf (application/pdf)
HAAG-rmi_iiop_chapter.pdf (application/octet-stream)
EEADG-ejb_jar_xml.pdf (application/octet-stream)
EEADG-prlb_element.pdf (application/octet-stream)
EEDG-access_ejb_next.pdf (application/octet-stream)
EEDG-access_ejb_next.pdf (application/octet-stream)
HAAG-rmi_iiop_chapter.pdf (application/octet-stream)

Comments:
Comment ID Location Comment
RJP-001 create-iiop-listener(1) man page Sample comment. Should provide a proposed fix and correct content if applicable.
RJP-002 delete-iiop-listener(1) man page Another sample comment.
Posted by rebeccaparks at Nov 08, 2010 13:12

No comments - LGTM.
Posted by trmueller at Nov 17, 2010 11:47

Comments on RMI-IIOP FOLB docs:

  • I don't think InitialContext (Hardware) is appropriate.  There is no special hardware (like a load balancer?) required here
    • The ORB does have undocumented support for hardware loadbalancing, which is quite different from InitialContext load balancing.
  • p. 30: InitiaContext summary:
    • Says "When a client performs a JNDI lookup for an object, the Naming Service create a InitialContext (IC) object associated with a particular server instance".
      • The client FIRST creates the InitialContext (calling new InitialContext()), then does a JNDI lookup on the InitialContext
      • need to state somewhere that failover can take place, and all objects derived from the same InitialContext will failover to the same instance
  • p. 31: InitialContext Algorithm, 3rd paragraph:
    • Note that the rotation is actually randomized, so this is not rotation to the next endpoint in the list, but instead to a random endpoint in the list.
  • IIOP FOLB vs. PRLB:
    • Note that PRLB is configured on a per-EJB basis, while IIOP FOLB is configured automatically across the entire cluster, so long as the application client has at least two endpoints specified (e.g. in com.sun.appserv.iiop.endpoints).
    • The user can certainly have some EJBs using PRLB, and some that use IIOP FOLB.
    • Failover is the same in either (PRLB vs. IIOP FOLB) case.
    • I can't see how a warning not to mix the two makes sense here.
Posted by kcavanaugh at Jan 31, 2011 09:47
Comment ID Location Comment
TJQ-001 p. 132 Steps 1 through 5 are needed only if the user is setting up a system different from the one where the DAS is installed. (In a production system this will be common, but it is rarer in a development environment.) For example, a developer who wants to experiment with a cluster and load balancing might create two instances on the same system where the DAS is running. In such a case steps 1-5 are unnecessary. Let's mention the difference.
TJQ-002 p. 133, step 7 In addition, the user can specify -targetserver host1:port1,host2:port2 on the appclient command to specify endpoints.
TJQ-003 p. 133, step 9 I suggest changing "/my_dir" to "my_dir" (removing the slash). Rarely will a user really want to store the downloaded artifacts at a top-level directory.
TJQ-004 p. 133, step 10 I suggest changing the command to appclient -client my_dir/myappClient.jar. The -name option and value are optional and are needed only if the user deployed an EAR which contained multiple app clients; the name is one way to instruct the ACC which of multiple clients in the EAR to launch. If you want to keep the -name option please change the example value to clientName and rearrange the options like this:

appclient -name clientName -client my_dir/myappClient.jar

The file name my_dir/myappClient.jar is consistent with the earlier asadmin deploy example command (if modified as suggested in TJQ-003).
Posted by timq at Jan 31, 2011 14:02
Comment ID Location Comment
CF-001 The sun-ejb-jar.xml file
Looks good.
CF-002 per-request-load-balancing
Looks good.
CF-003
Chapter 11 RMI-IIOP Load Balancing and Failover p133 #9, I suggest changing the deploy command to:

asadmin  --user admin --passwordfile pw.txt deploy --target cluster1 --retrieve my_dir myapp.ear

so we're using a --target for deploying to cluster; changing file name to have .ear extension; moving common asadmin options in front of deploy subcommand.
CF-004
   GO for 3.1 FCS
Posted by cheng.fang at Feb 07, 2011 08:46

Looks good to me. GO for 3.1 FCS.
Posted by kcavanaugh at Feb 21, 2011 11:06