. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 11.2. SSH Shell Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 11.2.2. Lifecycle commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 11.2.3. Runtime commands. . . . . . . . . . . . While setting up form tracking, it can be very useful to use the Apache Unomi Karaf SSH shell commands : event-tail and event-view to check if you are properly receiving the form submission events and

__/ /_/ |_|\__,_/_/ \__,_/_/ Apache Karaf (4.2.15) Hit '' for a list of available commands and '[cmd] --help' for help on a specific command. Hit 'system:shutdown' to shutdown Karaf. Hit protect the system if you have changed it. You can find the list of Apache Unomi shell commands in the "Shell commands" section of the documentation. 4.14. ELASTICSEARCH AUTHENTICATION AND SECURITY With its data migration, located in tools/shell-commands/src/main/resources/META- INF/cxs/migration (https://github.com/apache/unomi/tree/master/tools/shell-commands/src/main/resources/META-INF/cxs/migration)

nothing had happened. The way this works is as follows: As Apache ActiveMQ Artemis clients send commands to their servers they store each sent command in an in-memory buffer. In the case that connection successfully received from that client. If the client has sent more commands than were received before failover it can replay any sent commands from its buffer so that the client and server can reconcile their parameter on the connection URL. When the server has received confirmationWindowSize bytes of commands and processed them it will send back a command confirmation to the client, and the client can then

nothing had happened. The way this works is as follows: As Apache ActiveMQ Artemis clients send commands to their servers they store each sent command in an in-memory buffer. In the case that connection successfully received from that client. If the client has sent more commands than were received before failover it can replay any sent commands from its buffer so that the client and server can reconcile their parameter on the connection URL. When the server has received confirmationWindowSize bytes of commands and processed them it will send back a command confirmation to the client, and the client can then

nothing had happened. The way this works is as follows: As Apache ActiveMQ Artemis clients send commands to their servers they store each sent command in an in-memory buffer. In the case that connection successfully received from that client. If the client has sent more commands than were received before failover it can replay any sent commands from its buffer so that the client and server can reconcile their parameter on the connection URL. When the server has received confirmationWindowSize bytes of commands and processed them it will send back a command confirmation to the client, and the client can then

nothing had happened. The way this works is as follows: As Apache ActiveMQ Artemis clients send commands to their servers they store each sent command in an in-memory buffer. In the case that connection successfully received from that client. If the client has sent more commands than were received before failover it can replay any sent commands from its buffer so that the client and server can reconcile their parameter on the connection URL. When the server has received confirmationWindowSize bytes of commands and processed them it will send back a command confirmation to the client, and the client can then

nothing had happened. The way this works is as follows: As Apache ActiveMQ Artemis clients send commands to their servers they store each sent command in an in-memory buffer. In the case that connection successfully received from that client. If the client has sent more commands than were received before failover it can replay any sent commands from its buffer so that the client and server can reconcile their parameter on the connection URL. When the server has received confirmationWindowSize bytes of commands and processed them it will send back a command confirmation to the client, and the client can then

nothing had happened. The way this works is as follows: As Apache ActiveMQ Artemis clients send commands to their servers they store each sent command in an in-memory buffer. In the case that connection successfully received from that client. If the client has sent more commands than were received before failover it can replay any sent commands from its buffer so that the client and server can reconcile their parameter on the connection URL. When the server has received confirmationWindowSize bytes of commands and processed them it will send back a command confirmation to the client, and the client can then

nothing had happened. The way this works is as follows: As Apache ActiveMQ Artemis clients send commands to their servers they store each sent command in an in-memory buffer. In the case that connection successfully received from that client. If the client has sent more commands than were received before failover it can replay any sent commands from its buffer so that the client and server can reconcile their parameter on the connection URL. When the server has received confirmationWindowSize bytes of commands and processed them it will send back a command confirmation to the client, and the client can then

Connecting to the remote shell Remote shell credentials Extending the remote shell Remote shell commands Remote shell plugins 36. Metrics Recording your own metrics Metric repositories Coda Hale Metrics (v1.0.3.BUILD-SNAPSHOT) on myhost Type help for a list of commands. Spring boot provides metrics, beans, autoconfig and endpoint commands. Remote shell credentials You can use the shell.auth.simple ways. Remote shell commands You can write additional shell commands using Groovy or Java (see the CRaSH documentation for details). By default Spring Boot will search for commands in the following locations: