Red Hat Bugzilla – Bug 869014
Bug in Administration and Configuration Guide
Last modified: 2014-05-15 00:41:03 EDT
Description of problem: Typos - Use of AS or Application Server when EAP or Enterprise Application Platform should be used.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
In the Admin and Config guide at the following locations:
a. The image has AS in the title.
b. “The following diagram illustrates an overview of the JBoss Enterprise Application Server and its components.”
c. The first block of code has “-jboss-as - the path to your JBoss Enterprise Application Server.”
a. End of 3rd paragraph “In JBoss AS, the default local JNDI name”
b. In the 1st bullet “JNDI in JBoss AS means that the JNDI”
a. End of 2nd paragraph “how to setup alternative databases for JBoss AS.”
a. In 1st paragraph
i. “file, JBoss AS will provide a reasonable”
ii. “in JBoss AS 4.2. Notice the options”
a. In 1st and only paragraph “standalone services in JBoss AS or as part of”
a. End of 2nd paragraph “files shipped with the JBoss AS are already listed”
a. In 2nd paragraph “Notice that in JBoss AS, unlike in”
b. In 3rd paragraph “The JAR file location defaults to lib in JBoss AS -- but it”
a. In NOTE labeled Persistence Units in EAR Deployment, at the end of the 2nd paragraph “under the respective JBoss AS server profile”
a. In 1st bullet “By default, JBoss Application Server will not do load-time”
a. This one is a maybe depending on the meaning the author was trying to convey. It is in the 2nd paragraph “legacy version of JBoss Application Server.”
a. In 1st bullet “exposed via tools like the AS's JMX console”
b. In the NOTE “JBoss Application Server 3.x and 4.x”
c. In the NOTE “in JBoss Application Server 5 and later”
a. Under 220.127.116.11, below code example, in 2nd bullet
i. “The standard protocol stack configurations in JBoss AS use the value”
ii. “Using the -u command line switch when starting JBoss Application Server sets that value.”
a. Under 18.104.22.168 FD, in the 3rd bullet “This is default behavior for JBoss Application Server”
b. Under 22.214.171.124. FD versus FD_SOCK, in the last paragraph “JGroups configurations included with JBoss Application Server”
a. In the 2nd paragraph “If JBoss Application Server is started with”
a. In the 1st paragraph “Within JBoss Application Server, there are a number”
a. The title of the following sub section “126.96.36.199. Isolating sets of Application Server instances from each other”
a. The title of the following sub section “188.8.131.52. Isolating Channels for Different Services on the Same Set of AS Instances”
b. Under 184.108.40.206, in the 2nd paragraph “The configurations that ship with JBoss Application Server ensure that this”
c. Under 220.127.116.11, in the 3rd paragraph
i. “In releases prior to JBoss Application Server 5, different”
ii. “transport introduced in JBoss AS 5”
a. In the 1st line “JGroups channels opened by all standard AS services”
b. In the 2nd line “protocol stack configurations in JBoss AS:”
a. In the 1st paragraph “By default, a JBoss AS instance running”
b. In the 3rd paragraph
i. “configurations that the standard JBoss AS distribution doesn't”
ii. “So, if you reconfigure some AS service to use one”
1. The whole chapter has been rewritten, while the mentioned points have been fixed during the rewrite.
2. Already fixed out of the scope of this BZ.
3. Already fixed out of the scope of this BZ.
4. TODO: get SME info on removed 5.2.3
5. Already fixed out of the scope of this BZ.
6. Already fixed out of the scope of this BZ.
7. Already fixed out of the scope of this BZ.
10. Kept the original version as this general statement should also cover migration from community AS.
a) Edited to "like the JMX Console". Within the context of this guide, it's redundant to say that it belongs to the AS.
b), c) Fixed.
19. Already fixed out of the scope of this BZ.
Changes committed to SVN and staged at .
4. Fixed with up to date information and included in the book. Changes have been committed to SVN and staged.
Verified in peer review.