Activity information

The getactivityinfo console command displays the following values about an activity:

Field Description
 pkey

The activity’s primary key. Uniquely identifies this activity within Rhino.

 activity

The activity object, in string form. Its exact content is resource adaptor dependent (and may or may not contain useful human-readable information).

 creating-gen

The database generation in which the activity was created.

 ending

Boolean flag indicating if the activity is ending.

 events-submitted

The number of events that have been submitted for processing on the activity.

 flags

Hexadecimal value of the flags the activity was created with (if any).

 handle

The activity handle assigned by the activity’s resource adaptor entity, in string form. The exact content is resource adaptor dependent (and may or may not contain useful human-readable information).

 head-event

The event at the head of the activity’s event queue (the next event to be processed on the activity).

 last-event-time

When the most recent event was submitted on the activity.

 namespace

The namespace that the activity resides in.

 node

The Rhino cluster node that currently owns the activity. If this value is different to the submission-node field, the activity must be a replicated activity that was reassigned to this node.

If this value is negative, then the activity is currently non-resident. This means that the state for the activity was replicated to an external key/value store, the node that the activity was previously assigned to has failed, and the activity has not yet been adopted by any remaining cluster node. The absolute value of the node ID represents the node that the activity was last assigned to.

 ra-entity

The resource adaptor entity that created this activity.

 replication-mode

The method of activity replication. This field will have one of the following values:

  • NONE — the activity is not replicated

  • SAVANNA — the activity is replicated using the traditional savanna framework

  • KEY_VALUE_STORE — the activity is replicated using an external key/value store.

 submission-time

When the activity was created.

 submission-node

The Rhino cluster node that created the activity.

 update-time

When the activity was last updated (when the most recent database generation record was created). Useful in some situations for evaluating whether an activity is still live.

 bxref:#event-queue-information[event-queue]

A list of events queued for processing on the activity.

 bxref:#generational-information[generations]

A list of generational information stored in the database for the activity. If getactivityinfo includes the -v option, all generations display (otherwise just the most recent displays).

Event-queue information

The getactivityinfo console command displays the following values for each event in an activity’s event queue:

Field Description
 position

The position of the event in the queue.

 event-type

The event-type component identifier of the event.

 event

The event object, in string form. Its exact content is resource adaptor dependent (and may or may not contain useful human-readable information).

 flags

Hexadecimal value of the flags the event was fired with (if any).

Generational information

The getactivityinfo console command displays values for the following fields, in an activity’s generational information:

Field Description
 generation

Not displayed as a field but included in square brackets before the rest of the generational information, for example: [76343].

 refcount

The number of references made to the activity by the Timer Facility and the Activity Context Naming Facility.

 removed

Boolean flag indicating if the activity no longer exists in the SLEE. Only true if the activity has ended but has not yet been garbage collected.

 bxref:#attached-sbb-information[attached-sbbs]

A list of SBBs attached to the activity.

 bxref:#activity-timer-information[timers]

A list of Timer Facility timers set on the activity.

Attached-SBB information

The getactivityinfo console command displays values for the following fields, for each SBB entity attached to an activity:

Field Description
 pkey

The primary key of the SBB entity.

 namespace

The namespace the attached SBB entity resides in. This will always be equal to the namespace in which the activity resides.

 sbb-component-id

The component identifier of the SBB for the SBB entity.

 service-component-id

The component identifier of the service the SBB belongs to.

Activity-timer information

The getactivityinfo console command displays values for the following fields, for each timer active on an activity:

Field Description
 pkey

The primary key of the timer.

 namespace

The namespace that the timer exists in. This will always be equal to the namespace in which the activity resides.

 activity-pkey

The primary key of the activity the timer is set on.

 submission-time

The time the timer was initially set.

 period

The timer period (for periodic timers).

 repetitions

The number of repetitions the timer will fire before it expires.

 preserve-missed

Boolean flag indicating if missed timers should still fire an event into the SLEE.

 replicated

Boolean flag indicating whether or not the timer is replicated. This flag will only be set to true if the activity the timer was set on has a replication mode of SAVANNA.

Previous page Next page
Rhino Version 3.0.0