312/461

## glassfish:ejb:cache:beanPassivatedEvent

bean passivated event

Synopsis

    glassfish:ejb:cache:beanPassivatedEvent (
    long beanId,
    String appName,
    String modName,
    String ejbName,
    boolean success)

    glassfish:ejb:cache__beanspecific_:beanPassivatedEvent (
    long beanId,
    String appName,
    String modName,
    String ejbName,
    boolean success)

Description

These two events are sent when an object is passivated by the EJB container.

Use the generic version of this event to track the number of bean passivations across the entire EJB container and to track the number of successful or failed passivations across the entire EJB container.

Use the bean-specific version of this event to track the number of bean passivations of a specific bean and to track the number of successful or failed passivations of 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:cache__sample_App_sampleModule_jar_sampleBean_:beanPassivatedEvent

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.

`success`

  Has the value `true` if the bean was passivated successfully.