To find activities in the SLEE, use the following rhino-console command or related MBean operations.
Console command: findactivities
Command |
findactivities [-all] [-maxpernode maxrows] [-node nodeid] [-ra <ra-entity>] [-created-after date|time|offset] [-created-before date|time|offset] [-updated-after date|time|offset] [-updated-before date|time|offset] Find activities. Use -all to display activities removed but not garbage collected. |
|||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Options |
Times for the above options may be entered in either absolute or relative format:
|
|||||||||||||||||||||||||||||||||||||||||
Examples |
To display all activities in the SLEE:
$ ./rhino-console findactivities pkey attach-count handle node ra-entity ref-count replicated submission-time update-time -- -- -- -- -- -- -- -- ------------------ 0.101:108896044881:1.1 0 ServiceActivity[ServiceID[name=Simp 101 Rhino Inte 0 true 20080417 16:48:19 20080417 16:48:19 A.101:108896044898:100.1 1 SAH[switchID=1208407667,connectionI 101 simple 1 true 20080417 17:32:19 20080417 17:32:19 A.101:108896044898:104.1 1 SAH[switchID=1208407667,connectionI 101 simple 1 true 20080417 17:32:20 20080417 17:32:20 A.101:108896044898:106.1 1 SAH[switchID=1208407667,connectionI 101 simple 1 true 20080417 17:32:21 20080417 17:32:21 A.101:108896044898:108.1 1 SAH[switchID=1208407667,connectionI 101 simple 1 true 20080417 17:32:21 20080417 17:32:21 A.101:108896044898:110.1 1 SAH[switchID=1208407667,connectionI 101 simple 1 true 20080417 17:32:23 20080417 17:32:23 A.101:108896044898:112.1 1 SAH[switchID=1208407667,connectionI 101 simple 1 true 20080417 17:32:24 20080417 17:32:24 A.101:108896044898:116.1 1 SAH[switchID=1208407667,connectionI 101 simple 1 true 20080417 17:32:25 20080417 17:32:25 ... 100 rows Finding stale activities
A common search would be for stale activities. Rhino performs a periodic activity-liveness scan, checking all active activities and ending those detected as stale. Sometimes, however, a failure in the network or inside a resource adaptor might prevent the liveness scan from detecting and ending some activities. In this case, the Administrator would have to locate and end the stale activities manually. To narrow the search:
To search for activities belonging to node 101 (replicated or non-replicated activities owned by 101) that are more than one hour old, you would use the parameters $ ./rhino-console findactivities -node 101 -cb 1h pkey attach-count handle node ra-entity ref-count replicated submission-time update-time -- -- -- -- -- -- -- -- ------------------ A.101:108896044898:104.1 1 SAH[switchID=1208407667,connectionI 101 simple 1 true 20080417 17:32:20 20080417 17:32:20 A.101:108896044898:106.1 1 SAH[switchID=1208407667,connectionI 101 simple 1 true 20080417 17:32:21 20080417 17:32:21 2 rows (This example returned two activities.) |
MBean operation: getActivities
MBean |
|||||
---|---|---|---|---|---|
Rhino operations |
Get summary information for all activities
public TabularData getActivities(int maxPerNode, boolean includeRemoved) throws ManagementException; This operation returns tabular data summarising all activities. Get summary information for activities belonging to a resource adaptor entity
public TabularData getActivities(int maxPerNode, String entityName, boolean includeRemoved) throws ManagementException, UnrecognizedResourceAdaptorEntityException; This operation returns tabular data summarising the activities owned by the given resource adaptor entity. Get summary information for activities using time-based criteria
public TabularData getActivities(int maxPerNode, String entityName, long createdAfter, long createdBefore, long updatedAfter, long updatedBefore, boolean includeRemoved) throws ManagementException, UnrecognizedResourceAdaptorEntityException; This operation returns tabular data summarising the activities owned by the given resource adaptor entity using the time-based criteria specified (in milliseconds, as used by
|