EJB container exit event
glassfish:ejb:bean:containerLeavingEvent (
long beanId,
String appName,
String modName,
String ejbName)
glassfish:ejb:bean__beanspecific_:containerLeavingEvent (
long beanId,
String appName,
String modName,
String ejbName)
These two events are sent when the execution stack leaves EJB container code.
Use the generic version of this event to track time spent in the EJB container (including calls to other internal modules) across the entire EJB container.
Use the bean-specific version of this event to track time spent in the EJB container (including calls to other internal modules) arising from 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_:containerLeavingEvent
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.
beanIdThe unique identifier for the EJB container associated with this EJB.
appNameThe name of the application associated with the EJB.
modNameThe name of the module that contains the EJB.
ejbNameThe name of the EJB.