311/461

## glassfish:ejb:bean:methodStartEvent

start of the method execution event

Synopsis

    glassfish:ejb:bean:methodStartEvent (
    long beanId,
    String appName,
    String modName,
    String ejbName,
    Method method)

    glassfish:ejb:bean__beanspecific_:methodStartEvent (
    long beanId,
    String appName,
    String modName,
    String ejbName,
    Method method)

Description

These two events are sent when the EJB container code starts executing a bean method.

Use the generic version of this event to track EJB methods executed across the entire EJB container.

Use the bean-specific version of this event to track EJB methods executed for a specific bean. In the bean-specific version, beanspecific has the form:

    appName_modName_ejbName

In this form, appName, modName, and ejbName are the names of the application, the module, and the bean, respectively, with dashes (-) and periods (.) converted to underscores (_). For example, the bean-specific event name for the `sampleBean` bean in the `sampleModule.jar` module of the `sample-App` application is:

    glassfish:ejb:bean__sample_App_sampleModule_jar_sampleBean_:methodStartEvent

When monitoring the activity of a specific bean, using the bean-specific version of this event provides much better end-to-end monitoring performance than does using the generic version and inspecting its parameters to associate the event with the bean.

Parameters

`beanId`

  The unique identifier for the EJB container associated with this EJB.

`appName`

  The name of the application associated with the EJB.

`modName`

  The name of the module that contains the EJB.

`ejbName`

  The name of the EJB.

`method`

  The Method object.