| Comment ID |
Section, Page Number/URL |
Comment |
Status – (RESOLVED/UNRESOLVED) |
| 1 |
28 |
Orig : lb-enabled false (optional) If true, all load-balancers consider this application available to them. |
|
| |
|
Modification: lb-enabled false (optional) If true, all load-balancers referring to this application consider its available to them. |
RESOLVED |
| 2 |
28 |
Attributes devide-host, device-port, ssl-proxy-host, ssl-proxy-port are used to identify the Physical load balancer (the ssl and non-ssl host and port info). |
RESOLVED |
| |
|
These attributes are used by the apply-http-lb-changes and also to automatically transfer the loadbalancer changes when auto-apply-enabled flag is turned on. |
RESOLVED |
| |
|
Might atleast want to mention about the physical loadbalancer. |
RESOLVED |
| 3 |
128 |
Orig : lb-enabled false (optional) If true, all load-balancers consider this server instance available to them. |
|
| |
|
Modification: lb-enabled false (optional) If true, all load-balancers referring to this server instance consider its available to them. |
RESOLVED |
| Prashanth |
|
More feedback |
RESOLVED |
| 4 |
Default Paths and names,12 |
instance-dir is not referred anywhere, it should be removed as it is confusing JP: instance-dir is defined in every doc preface. |
RESOLVED |
| 5 |
Table 1-159 page 126 |
mapped-principal-class this is not present by default in domain.xml. We need to capture this information JP: Default values section discusses this issue. |
RESOLVED |
| 6 |
Page 30 |
name of the class should be com.sun.enterprise.security.auth.realm.file.FileRealm instead of com.iplanet.ias.security.auth.realm.file.FileRealm |
RESOLVED |
| 7 |
Page 79 |
default values are incorrect |
RESOLVED |
| 8 |
page 29 |
default values are incorrect |
RESOLVED |
| 9 |
page 31 |
In GlassFish v2, the assign-groups property in CertificateRealm has been extended to FileRealm, LDAPRealm, SolarisRealm, and JDBCRealm. |
RESOLVED |
| 10 |
Page 31 |
JDBCRealm properties are not documented. Please see this blog post |
RESOLVED |
| 11 |
Page 106 |
default for auth-layer="SOAP" |
RESOLVED |
| 12 |
Page 118 |
default for security.config is incorrect |
RESOLVED |
| 13 |
Page 130 |
ssl-enabled of http-protocol is not implemented , so it should not be referred to here. See page 71 -"ssl-enabled - (optional) Not implemented. Use ssl subelements of Âœhttp-listener on page 67 elements." |
RESOLVED |
| 14 |
Page 131 |
default for cert-nickname should be s1as, |
RESOLVED |
| 15 |
Page 130 |
I dont think this statement is true - "In the developer profile, SSL is globally disabled by default." |
RESOLVED |
| 16 |
Page 131 |
allowed values for ssl3-tls-ciphers should be updated or may have to say it depends on JCE Provider JP: Values are correct. |
RESOLVED |
| hzhang |
lifecycle-module, Table 1-104 |
The classpath attribute of lifecycle module, the default should the application-root attribute of "domain" element, not "server" element. |
RESOLVED |
| hzhang |
j2ee-application, Table 1-80 |
The directory-deployed attribute of j2ee-applications, it should say whether the application has been deployed "as a directory" instead of "to a directory". This same change should apply to all directory-deployed attributes (web-module, ejb-module, appclient-module, connector module, extension-module). |
RESOLVED |
| Jagadish Ramu |
jdbc-connection-pool, Table 1-86 |
Attribute: "datasource-classname". In Description: java.sql.DataSource, java.sql.XADataSource has to be javax.sql.DataSource, javax.sql.XADataSource |
RESOLVED |
| Jagadish Ramu |
jdbc-connection-pool, Table 1-86 |
Attribute validate-atmostperiod-in-seconds has to be validate-atmost-once-period-in-seconds |
RESOLVED |
| Jagadish Ramu |
connector-connection-pool, Table 1-32 |
Attribute validate-atmostperiod-in-seconds has to be validate-atmost-once-period-in-seconds |
RESOLVED |
| Ramesh Parthasarathy |
jms-service, Properties Pg 91 |
We added the following properties under jms-service for fixing http://bt2ws.central.sun.com/CrPrint-2146030 user-name : specifies the user name for creating the jms connection default value is guest, password : specifies the password for creating the jms connection default is guest. These are optional properties, and the user has to configure these properties only if the default username/password of "guest/guest" is not available in the broker. |
RESOLVED |
| sparrow-001 |
Page 9 "as-install" |
Is there a schedule of adding installation for "Mac OS X" ? |
RESOLVED We do support the Mac OS, and as-install is the same as for Solaris and Linux. |
| sparrow-002 |
Page 13 "About the domain.xml File" |
"The encoding is UTF-8 to maintain compatibility with regular UNIX text editors." Is it correct ? I open the file "domain.xml" to make sure the text encoding. The file is encoded by "iso-8859-1 as Latin 1". |
RESOLVED Sentence deleted as instructed by the main domain.xml engineer. |
| sparrow-003 |
Page 15 "Element Hierarchy" |
Can "description" tag be omitted ? |
RESOLVED Description elements have become attributes. |
| shalm-001 |
Page 50 idle-timeout-in-seconds |
Add this to the description : "This timeout value must be kept shorter than the server side(Database) timeout value to prevent the accumulation of unusable connections in the application." |
RESOLVED |
| shalm-002 |
Page 52 connection-creation-retry-attempts |
Modify the description as "Specifies the number of attempts to create a new connection in case of a failure" |
RESOLVED |
| shalm-003 |
Page 52 associate-with-thread |
Append this to the description : "Specifies whether a connection is associated with the thread to enable the thread to reuse the connection. If associate-with-thread is set to false, the thread must obtain a connection from the pool each time the thread requires a connection." |
RESOLVED |
| shalm-004 |
Page 52 match-connections |
Add to the description : "Specifies whether a connection that is selected from the pool should be matched with the connections with certain credentials". |
RESOLVED |
| shalm-005 |
Page 52 max-connection-usage-count |
Add to the description : "By limiting the maximum number of times a connection can be reused, you can avoid statement leaks if the application does not close statements". |
RESOLVED |
| mvatkina-001 |
Page 87-88 transaction-service |
Add a note that while the elements are available, the ones that correspond to the transaction recovery do not have any effect as the transaction recovery is not supported in Prelude |
RESOLVED Added a note: Transaction recovery is not implemented for GlassFish v3 Prelude, even if the JTS and OMG add-on components are installed. Therefore, all transaction service attributes and properties pertaining to transaction recovery or transaction logs are not implemented. |
| maheshk-01 |
Page 32 |
Add a note for the following elements as we do not support Stateful session beans in prelude: cache-resice-quantity, max-cache-size, cache-idle-timeout-in-seconds, removal-timeout-in-seconds, victim-selection-policy |
RESOLVED |
| maheshk-02 |
Page 33 |
commit-option: Add a note saying that CMP beans are not yet supported in prelude |
RESOLVED |
| maheshk-03 |
Page 33 |
session-store: Add a note saying that Stateful session beans are not yet available in prelude |
RESOLVED |
| shalm-006 |
Page 52 associate-with-thread |
Add to the description : "This is an option to associate a connection with the thread such that when the same thread is in need of a connection, it can reuse the connection already associated with that thread. In this case, the overhead of getting a connection from the pool is avoided. However when this value is set to true, one should verify that the value of max-pool-size attribute is comparable to the max-thread-pool-size attribute of the thread-pool element. If the max-thread-pool-size value is way high than the max-pool-size, lot of time is spent in associating a connection to the new thread, after dissociating it from an older one. This attribute is basically used in cases where the user needs the thread pool to reuse connections thereby avoiding an overhead." |
RESOLVED |
| shalm-007 |
Page 51 connection-leak-timeout-in-seconds |
Add to the description : "This attribute is used along with connection-leak-reclaim to avoid potential connection leaks from the application. More details are at http://blogs.oracle.com/ks*tiz/entry/connection_leak_tracing ." |
RESOLVED |
| shalm-008 |
Page 51 connection-validation-method |
Add to the description, after auto-commit and meta-data bullet points : "Because many JDBC drivers cache the results of these calls, they do not always provide reliable validations. Check with the driver vendor to determine whether these calls are cached or not." Add to the description after table bullet point : "The table must exist and be accessible, but it doesn't require any rows. Do not use an existing table that has a large number of rows or a table that is already frequently accessed. More details can be found at http://blogs.oracle.com/JagadishPrasath/entry/connection_validation_in_glassfish_jdbc ." |
RESOLVED |
| shalm-009 |
Page 52 match-connections |
Add to the description : "If the connection pool is used by applications that have multiple user credentials, it is necessary that match-connections is turned ON. Connection pool will match the request's credential with the connections in the pool and return a matched connection for use. In case of new requests with different credentials, unmatched free connections will be automatically purged to provide new connections to satisfy the new requests. This attribute need not be set to true if it is known that there is only one credential used by the applications and hence the pool will have homogeneous connections." |
RESOLVED |
| shalm-010 |
Page 52 statement-timeout-in-seconds |
Add to the description : "This is the time in seconds after which abnormally running queries are terminated. A long running jdbc query executed by an application may leave it in a hanging state, unless a timeout is explicitly set on the statement. This provides the user to know that all queries would automatically timeout if not completed within the specified period. When statements are created, the queryTimeout will be set according to the value specified in this property. This will work only when the underlying JDBC driver supports queryTimeout for Statement, PreparedStatement, CallableStatement and ResultSet." |
RESOLVED |
| shalm-011 |
Page 52 wrap-jdbc-objects |
Change description to : "When this is set to true, wrapped jdbc objects are got for Statement, PreparedStatement, CallableStatement, ResultSet and DatabaseMetaData. This option makes sure that Statement.getConnection() will be the same as DataSource.getConnection(). Hence this option should be set to true when both Statement.getConnection() and DataSource.getConnection() are done. Default is set to false in the Enterprise server so as to not break the existing applications." |
RESOLVED |
| tjquinn-001 |
p. 51, table 1-45 |
The web-module-config element makes sense only if the parent engine's 'sniffer' value is "web" and should not appear otherwise. If we think that the description in the table "Configures the parent web module." conveys this, then fine. It might be good to elaborate there just a bit. |
RESOLVED Added "Applicable only if this engine element has a sniffer value of web" to the table. Added "Applicable only if the parent engine element has a sniffer value of web" to the web-module-config element description. |
| tjquinn-002 |
p. 25, table 1-8 and p. 95, table 1-104, property row |
(There might be a better place than the admin refc doc to describe the following...) As June has mentioned in e-mail, different deployers will pay attention to different property settings at the application and/or module level. The deploy command supports --property and --properties options (they are equivalent) to set property names and values at the application level. I'm not sure if there is a way other than the asadmin set command and dotted notation to set properties at the module level. There is an application-level property java-web-start-enabled which influences whether app clients in that application are enabled for Java Web Start access. Do we want to gather all such properties here in the admin refc? |
RESOLVED Added all the properties I know about to the application element properties table, including java-web-start-enabled (moved from under module), the four lifecycle module properties, and the seven jruby properties. Also added an intro to the properties that describes how to set them during deployment and how the engine sniffer attribute determines which are valid. |
| chaase-001 |
p. 130, Table 1â€Â"165, thread-pool Attributes |
The default values shown here are not the same as the defaults used by the asadmin create-threadpool command and the Admin Console. The admin tools create a pool with a max-thread-pool-size of 5, not 200; with a min-thread-pool-size of 2, not 0; with an idle-thread-timeout-in-seconds of 900, not 120; and with a max-queue-size of -1, not 4096. Are the tools doing the wrong thing, or is the document incorrect? |
RESOLVED I corrected the defaults to Tim's config analyzer output. Also added recommended values for various thread pool uses. |
