Chapter 1 Oracle GlassFish^TM Server Monitoring Scripting Client 3.0.1 Release Notes

Oracle GlassFish Server 3.0.1 Monitoring Scripting Client Release Notes provide late-breaking information about the software and documentation for the Monitoring Scripting Client. The document includes requirements for obtaining and using Monitoring Scripting Client. Descriptions and workarounds for known issues and limitations are also provided.

Read this document before installing, setting up, and using Oracle GlassFish Server Monitoring Scripting Client 3.0.1.

The following topics are addressed here:

• Revision History

• About Monitoring Scripting Client

• Requirements for Obtaining and Using Monitoring Scripting Client

• Monitoring Scripting Client Documentation

• Known Issues

• How to Report Problems and Provide Feedback

• Additional Resources

• Third-Party Web Site References

• Accessibility Features

Revision History

This section provides a record of changes in these Release Notes.

About Monitoring Scripting Client

Monitoring Scripting Client provides support for clients that are written in the JavaScript^TM programming language to provide monitoring data about Oracle GlassFish Server.

Requirements for Obtaining and Using Monitoring Scripting Client

Monitoring Scripting Client is integrated with Oracle GlassFish Server and is installed when Oracle GlassFish Server is installed.

If you are using GlassFish Server Open Source Edition, you can obtain this feature separately by purchasing a right-to-use. Monitoring Scripting Client is available to customers who have purchased a right to use either as a patch from the SunSolve^SM program site or as an add-on component from Update Tool.

For information about how to download Monitoring Scripting Client, see Downloading and Installing Monitoring Scripting Client in Oracle GlassFish Server 3.0.1 Monitoring Scripting Client Installation and Quick Start Guide. Before downloading Monitoring Scripting Client, ensure that you have your account username and password.

Monitoring Scripting Client 3.0.1 requires Oracle GlassFish Server 3.0.1.

The remaining hardware and software requirements for Monitoring Scripting Client are identical to the requirements for using Oracle GlassFish Server 3.0.1. For more information, see Hardware and Software Requirements in Oracle GlassFish Server 3.0.1 Release Notes.

Monitoring Scripting Client Documentation

For information about installation and basic use of Monitoring Scripting Client, see Oracle GlassFish Server 3.0.1 Monitoring Scripting Client Installation and Quick Start Guide.

For information about GlassFish Server, see the Oracle GlassFish Server 3.0.1 documentation.

Known Issues

This section lists the following known issues with Monitoring Scripting Client:

• Omission of DynamicImport-Package entry in manifest causes probes for the JavaMail^TM service not to fire (Issue 11069)

• Keep-alive probes for network listeners are not fired as expected (6886579)

• Jersey probes are not fired (6908856)

• Invalid script causes run-script to throw an exception (6906040)

Omission of DynamicImport-Package entry in manifest causes probes for the JavaMail^TM service not to fire (Issue 11069)

Description

The DynamicImport-Package: org.glassfish.flashlight.provider entry is omitted from the manifest for the mail.jar file. As a result, the probes for the JavaMail service are not fired.

For details, see GlassFish project Issue 11069.

Workaround

None.

Keep-alive probes for network listeners are not fired as expected (6886579)

Description

When an HTTP request with the connection header Connection: keep-alive is sent to a network listener for whose HTTP protocol Comet support is enabled, keep-alive probes are not fired.

Workaround

None.

Jersey probes are not fired (6908856)

Description

The following Jersey probes are not fired:

• glassfish:jersey:server:requestStart

• glassfish:jersey:server:requestEnd

• glassfish:jersey:server:ruleAccept

Workaround

None.

Invalid script causes run-script to throw an exception (6906040)

Description

When run-script is run with an invalid script, an exception is thrown.

Ideally, run-script should display a suitable error message and not throw an exception stack trace.

Workaround

Examine the stack trace for information that might help identify errors in the script.

How to Report Problems and Provide Feedback

If you have problems with Oracle GlassFish Server Monitoring Scripting Client 3.0.1, provide feedback through one of the following mechanisms:

• Feedback Submittal form — A form for submitting feedback on the GlassFish Server product

• Java Technology Forums — An interactive message board for sharing knowledge and questions about Java technologies and programming techniques; use the Java EE SDK forum for discussions related to the Oracle GlassFish Server 3.0.1 product

• Oracle Support services — Links to the Knowledge Base, Online Support Center, and Product Tracker, as well as to maintenance programs and support contact numbers

  So that we can best assist you in resolving problems, please have the following information available when you contact support:

  • The telephone dispatch number associated with your maintenance contract

  • A description of the problem, including the situation where the problem occurs and its impact on your operation

  • Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem

  • Detailed steps on the methods you have used to reproduce the problem

  • Any error logs or core dumps

Additional Resources

Useful information can be found at the following locations:

• GlassFish Community

• Oracle Developer Information

• Oracle GlassFish Server product page

• Sun Developer Support Services

• Oracle product documentation

Third-Party Web Site References

Third-party URLs are referenced in this document and provide additional, related information.

Oracle is not responsible for the availability of third-party Web sites mentioned in this document. Oracle does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Oracle will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

Accessibility Features

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/index.html.