The Remote The Remote Communication Protocol (RCP) is the protocol used for the internal communication. RCP latency monitoring can be performed on all of the available Pico Instances:
- Platform
- Execution Context
- Execution Context Stand-Alone
- Desktop
- Command Line
Each time a new instance is started, for example, when starting an mzsh shell from the Command Line, it will be added to the list of monitored Pico Instances.
The latency is the time it takes for a ping request to be sent to another party, for example, from the Platform to an Execution Context, and for the corresponding ping response to be received.
| Note | ||
|---|---|---|
| ||
When starting the Platform, the latency values might become high. To get more realistic values, do a reset using resetAllValues, as described in the section below, Operations. |
To monitor the latency between the Platform and the Pico Instance communicating with it, do the following:
- Select the codeserver process when starting the JMX client, see 7.1 Starting the Jconsole Client for further information.
The Java Monitoring & Management Console will open and display the Overview tab. - Click on the MBeans tab to display the different beans.
- Expand the tree in the left section by clicking on the plus sign for com.digitalroute.rcp, then on the plus sign for Ping and then on the plus sign for the connection you want to monitor.
Attributes
Click on Attributes in the tree to display the different attribute values for a certain Pico Instance in the right section of the JConsole window.
JConsole displaying the attributes for RCP
| Attribute | Description |
|---|---|
Counter | This attribute value shows the total number of ping requests sent from a Pico Instance. This value shows "0" when the Platform has been started, or after resetting the RCP latency values using resetAllValues, as described in the section below, Operations. |
Latency | This attribute value shows the current latency. |
MinLatency | This attribute value shows the lowest latency since the Platform was started, or after resetting the RCP latency values using resetAllValues, as described in the section below, Operations. |
MaxLatency | This attribute value shows the highest latency since the Platform was started, or after resetting the RCP latency values using resetAllValues, as described in the section below, Operations. |
| Anchor | ||||
|---|---|---|---|---|
|
Operations
Click on Operations in the tree to display the operation alternatives for a certain Pico Instance in the right section of the JConsole window.
| Operation | Description |
|---|---|
resetAllValues | Click on the resetAllValues operation in the tree to the left and then click this button to reset all RCP latency values. |
| Scroll ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||