To find activity context name bindings in the SLEE, use the following rhino-console command or related MBean operations.

Console command: findactivitybindings

Command

findactivitybindings [-maxpernode maxrows] [-node nodeid] [-created-after
date|time|offset] [-created-before date|time|offset]
  Description
    Find activity context naming facility bindings.

Options

Option Abbreviation Description
 -maxpernode <maxrows>

Retrieve at most this many activity context name bindings from each event-router node (default is 100). Can be used to limit Rhino’s load when processing the request.

 -node <node-id>

Only display activity context name bindings owned by the given node.

 -created-after <time>
 -ca

Only display activity context name bindings created after the given time.

 -created-before <time>
 -cb

Only display activity context name bindings created before the given time.

Times for the above options may be entered in either absolute or relative format:

Type Format Description Examples

Absolute

 [[yyyy/]MM/dd] [HH:mm[:ss]]

yyyy = the year
MM = the month (1-12)
dd = the date of the month (1-31)
HH = the hour (0-23)
mm = the minute (0-59)
ss = the second (0-59)

 2008/04/15
04/15
10:57
10:57:35
2008/04/15 10:57:35

Relative

 (<nn><d|h|m|s>)*

nn = a number
d = days
h = hours
m = minutes
s = seconds

 1d
1h
1m
30s
1m
7m30s
1d12h5m30s
Note Rhino assumes relative time format is in the past. For example, 1h30m means 1 hour and 30 minutes ago.

Examples

To display all activity context name bindings in the SLEE:
$ ./rhino-console findactivitybindings
name                                pkey                      namespace   replicated   submission-time
----------------------------------  ------------------------  ----------  -----------  ------------------
connection[1542896514/0]/non-repl    2.101:227012595280421.0                    false   20181122 14:22:05
connection[1542896514/0]/repl        3.101:227012595280422.0                     true   20181122 14:22:05
connection[1542896514/1]/non-repl    2.102:227012872179724.0                    false   20181122 14:22:05
connection[1542896514/1]/repl        3.102:227012872179725.0                     true   20181122 14:22:05
connection[1542896514/2]/non-repl    2.103:227012872965639.0                    false   20181122 14:22:05
connection[1542896514/2]/repl        3.103:227012872965640.0                     true   20181122 14:22:05
connection[1542896514/3]/non-repl    2.101:227012595280424.0                    false   20181122 14:23:15
connection[1542896514/3]/repl        3.101:227012595280425.0                     true   20181122 14:23:15
connection[1542896514/4]/non-repl    2.102:227012872179727.0                    false   20181122 14:23:16
connection[1542896514/4]/repl        3.102:227012872179728.0                     true   20181122 14:23:16
10 rows
Narrowing a name bindings 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 arguments -node 101 and -cb 1h:

$ ./rhino-console findactivitybindings -node 101 -cb 1h
name                                pkey                      namespace   replicated   submission-time
----------------------------------  ------------------------  ----------  -----------  ------------------
connection[1542896514/0]/non-repl    2.101:227012595280421.0                    false   20181122 14:22:05
connection[1542896514/0]/repl        3.101:227012595280422.0                     true   20181122 14:22:05
2 rows

(This example returned two name bindings.)

MBean operation: getBoundActivities

MBean

Rhino operations

Get summary information for all activity context name bindings
public TabularData getBoundActivities(int maxPerNode)
    throws ManagementException;

This operation returns tabular data summarising all activity context name bindings.


Get summary information for activity context name bindings using time-based criteria
public TabularData getBoundActivities(int maxPerNode, long createdAfter, long createdBefore)
    throws ManagementException;

This operation returns tabular data summarising the activity context name bindings using the time-based criteria specified (in milliseconds, as used by java.util.Date, or the value 0 to ignore a particular parameter).


Tip

Results depend on the Housekeeping MBean that invokes the operation:

  • Cluster Housekeeping MBean — returns results from all event-router nodes in the primary component

  • Node Housekeeping MBean — returns results from that node only.


Note For a description of the format of the tabular data that these operations return, see the javadoc.
Previous page Next page
Rhino Version 3.2