Skip to main content

Jboss JMX client twiddle

Twiddle is a command line tool that interact with JMX server instance. For linux systems twiddle.sh is under $JBOSS_HOME\bin directory. Usage can be learned typing ./twiddle.sh -h from command line.

./twiddle.sh -h
A JMX client to 'twiddle' with a remote JBoss server.

usage: twiddle.sh [options] <command> [command_arguments]
options:
-h, --help                             Show this help message
     --help-commands           Show a list of commands
-H=<command>                 Show command specific help
-c=command.properties      Specify the command.properties file to use
-D<name>[=<value>]         Set a system property
--                                        Stop processing options
-s, --server=<url>               The JNDI URL of the remote server
-a, --adapter=<name>        The JNDI name of the RMI adapter to use
-u, --user=<name>             Specify the username for authentication
-p, --password=<name>    Specify the password for authentication
-q, --quiet                          Be somewhat more quiet

Some simple usage is here:
List of MBeans published:
./twiddle.sh -s localhost serverinfo -l

Active Sessions for a web application: 
./twiddle.sh -s localhost get "jboss.web:host=localhost,path=<application context name>,type=Manager" activeSessions

Comments

Popular posts from this blog

Sending Jboss Server Logs to Logstash Using Filebeat with Multiline Support

In addition to sending system logs to logstash, it is possible to add a prospector section to the filebeat.yml for jboss server logs. Sometimes jboss server.log has single events made up from several lines of messages. In such cases Filebeat should be configured for a multiline prospector. Filebeat takes lines do not start with a date pattern (look at pattern in the multiline section "^[[:digit:]]{4}-[[:digit:]]{2}-[[:digit:]]{2}" and negate section is set to true ) and combines them with the previous line that starts with a date pattern. server.log file excerpt where DatePattern: yyyy-MM-dd-HH and ConversionPattern: %d %-5p [%c] %m%n Logstash filter:

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three