glassfish
  1. glassfish
  2. GLASSFISH-18651

the function in the command of the monitor isn't match to the manual(glassfish V4)

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0_b83
    • Component/s: docs
    • Labels:
      None
    • Environment:

      all

      Description

      1.Do the command as follows:
      asadmin enable-monitoring --adasdd
      2.from the command we got the messages as follows:
      Invalid option: --adasdd
      Usage: asadmin [asadmin-utility-options] enable-monitoring
      [--target ] [--pid
      ] [--options ]
      [--modules ] [--mbean[=]]
      [--dtrace[=
      ]] [?|-help[=]]
      3.Then I try to acquire the manual and do the command as follows:
      asadmin enable-monitoring --help
      4.I can't find any information related to the parameter of "--target",the information as follows:
      asadmin Utility Subcommands enable-monitoring(1)

      NAME
      enable-monitoring - enables monitoring for the server or for
      specific monitorable modules

      SYNOPSIS
      enable-monitoring [--help]
      [--mbean=

      {false|true}

      ]
      [--dtrace={true|false]
      [--modules modules[=level][:module[=level]]*
      [--pid pid]
      [--options options={true|false]]

      DESCRIPTION
      The enable-monitoring subcommand is used to turn on monitor-
      ing for GlassFish Server or for particular modules during
      runtime. Changes are dynamic, that is, server restart is not
      required.

      By default, the monitoring service is enabled, that is, the
      monitoring-enabled attribute of the monitoring-service ele-
      ment is true. However, the default monitoring level for
      individual modules is OFF. This subcommand used with the –
      modules option can enable monitoring for a given module by
      setting the monitoring level to HIGH or LOW. If level is not
      specified when running the subcommand, the level defaults to
      HIGH.

      The specific meanings of HIGH or LOW are determined by the
      individual containers. For a list of monitorable modules,
      see the --modules option in this help page.

      An alternative method for enabling monitoring is to use the
      set subcommand. In this case, the server must be restarted
      for changes to take effect.

      This subcommand is supported in remote mode only.

      OPTIONS
      --help
      -?

      Displays the help text for the subcommand.

      --mbean
      Enables Mbean monitoring. Default value is false.

      Java EE 6 Last change: 01 Nov 2010 1

      asadmin Utility Subcommands enable-monitoring(1)

      --dtrace

      Only usable if the DTracTMMonitoring module is present.
      Enables Oracle Solaris DTrace monitoring. Default
      value is false.

      --modules
      Enables specified module or modules by indicating moni-
      toring level. Valid levels are OFF, HIGH, LOW. If level
      is not specified, the default setting is HIGH. Multiple
      modules are separated by : (colon). Monitorable modules
      include connector-connection-pool, connector-service,
      ejb-container, http-service, jdbc-connection-pool, jer-
      sey, jpa, jms-service, jvm, security, thread-pool,
      transaction-service, web-container, and web-services-
      container. Additional modules can be listed by using the
      get subcommand.

      --pid

      Specifies the GlassFish Server JVM process identifier
      (PID). When monitoring is enabled, the btrace-agent is
      attached, based on the specified PID. Need to specify
      only in exceptional cases when the system cannot deter-
      mine the PID. In this situation, the subcommand prompts
      for the PID of the corresponding GlassFish Serverpro-
      cess.

      --options
      Sets the following btrace-agent options:

      debug

      Enables debugging for BTrace. Default value is
      false.

      EXAMPLES
      Example 1 Enabling the Monitoring Service for GlassFish
      Server

      This example enables monitoring for GlassFish Server in gen-
      eral by setting the enable-monitoring flag to true (default
      is true).

      asadmin> enable-monitoring
      Command enable-monitoring executed successfully

      Java EE 6 Last change: 01 Nov 2010 2

      asadmin Utility Subcommands enable-monitoring(1)

      Example 2 Enabling Monitoring for the Web and EJB Containers

      This example enables monitoring for specific containers by
      setting their monitoring levels.

      asadmin> enable-monitoring --modules web-container=LOW:ejb-container=HIGH

      Command enable-monitoring executed successfully

      Example 3 Turning on Debugging for Monitoring

      This example turns on debugging.

      asadmin> enable-monitoring --options debug=true
      Command enable-monitoring executed successfully

      EXIT STATUS
      0 subcommand executed successfully

      1 error in executing the subcom-
      mand

      SEE ALSO
      disable-monitoring(1), monitor(1), list(1), get(1), set(1)

      monitoring(5ASC)

      asadmin(1M)

      Chapter 8, Administering the Monitoring Service, in Oracle
      GlassFish Server 3.1 Administration Guide

      Java EE 6 Last change: 01 Nov 2010 3

      all in all,I wonder to know whether the parameter of "--target" can be used in glassfish V3?

        Activity

        Hide
        Jeremy_Lv added a comment -

        Does the parameter of "--target" can be used in glassfish?
        if it doesn't release in glassfish V4 ,I wonder you will delete the definition in source,if the monitor has release this function, there's more issue occured by the parameter of "--target"

        Show
        Jeremy_Lv added a comment - Does the parameter of "--target" can be used in glassfish? if it doesn't release in glassfish V4 ,I wonder you will delete the definition in source,if the monitor has release this function, there's more issue occured by the parameter of "--target"
        Hide
        Mike Fitch added a comment -

        Changed Fix Version to 4.0 so issue will show up on 4.0* queries. Actual commitment and build # TBD.

        Show
        Mike Fitch added a comment - Changed Fix Version to 4.0 so issue will show up on 4.0* queries. Actual commitment and build # TBD.
        Hide
        Mike Fitch added a comment -

        Added the --target option to the manpage:

        --target
        Specifies the target on which to enabling monitoring. Valid values are as follows:

        server
        Enables monitoring for the default server instance server and is the default value.

        <configuration_name>
        Enables monitoring for the named configuration.

        <cluster_name>
        Enables monitoring for every server instance in the cluster.

        <instance_name>
        Enables monitoring for a particular server instance.

        This addition will become accessible in GlassFish when the next main-docs build is promoted and picked up by GlassFish builds.

        Show
        Mike Fitch added a comment - Added the --target option to the manpage: --target Specifies the target on which to enabling monitoring. Valid values are as follows: server Enables monitoring for the default server instance server and is the default value. <configuration_name> Enables monitoring for the named configuration. <cluster_name> Enables monitoring for every server instance in the cluster. <instance_name> Enables monitoring for a particular server instance. This addition will become accessible in GlassFish when the next main-docs build is promoted and picked up by GlassFish builds.
        Hide
        Mike Fitch added a comment -

        Addition included in main-docs 4.0_b26, which began getting picked up by GlassFish builds as of revision 61028.

        Show
        Mike Fitch added a comment - Addition included in main-docs 4.0_b26, which began getting picked up by GlassFish builds as of revision 61028.

          People

          • Assignee:
            Mike Fitch
            Reporter:
            Jeremy_Lv
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: