This section lists the following known issues with Monitoring Scripting Client:
Keep-alive probes for network listeners are not fired as expected (6886579)
Invalid script causes run-script to throw an exception (6906040)
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.
None.
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.
None.
The following Jersey probes are not fired:
glassfish:jersey:server:requestStart
glassfish:jersey:server:requestEnd
glassfish:jersey:server:ruleAccept
None.
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.
Examine the stack trace for information that might help identify errors in the script.