[CONF] Apache Qpid: Qman Tool (page edited)

2008-10-29 Thread confluence 










Page Edited :
qpid :
Qman Tool



 
Qman Tool
has been edited by Arnaud
(Oct 29, 2008).
 

 
 (View changes)
 

Content:
Introduction

QMan is a Management bridge that exposes one (or several) Qpid broker domain model as MBeans that are accessible through the Java Management Extensions (JMX).

How to run QMan


Prerequisites

QMan is a standalone application that is packaged as qpid-management-client-incubating-M3.jar. To run QMan you need to add the following jars in your CLASSPATH:

	log4j-1.2.12.jar
	slf4j-api-1.4.0.jar
	slf4j-log4j12-1.4.0.jar
	commons-pool-1.4.jar
	commons-codec-1.3.jar
	commons-lang-2.2.jar
	commons-collections-3.2.jar
	commons-configuration-1.2.jar
	qpid-client-incubating-Mx.jar (were x is the current qpid version)
	qpid-common-incubating-Mx.jar (were x is the current qpid version)



alternatively you can run the following script (that add all the qpid jars to the CLASSPATH):
> CLASSPATH=`find  -name '*.jar' | tr '\n' ":"`
Where  is the directory containing the qpid jars (when qpid is built from source  is equal to qpid/java/build/lib)

QMan can be connected at run time against any broker. However if you wish to automatically connect to one or several brokers you can do so by providing a configuration file as follows:


  
	
	  localhost
	  5672
	  test
	  guest
	  guest
	  4
	  0
	  -1
	

	  myhost
	  5672
	  test
	  guest
	  guest
	  4
	  0
	  -1
	
  


The configuration above specifies that QMan should connect to two brokers, one on localhos and one on myhost, both listening on port 5672.

The configuration file to use is specified through the JVM parameter "qman-config" that must point onto a valid configuration file.

Running QMan

To run QMan in a console run the following command:

java org.apache.qpid.management.domain.services.QMan

Messages similar to those should be displayed:

... [org.apache.qpid.management.domain.services.QMan]  : Starting Q-Man...
...
Type "q" to quit.

if you wish to use a configuration file /myconfiguration.xml so QMan establishes a connection with one or several brokers, run the following command:

java -Dqman-config="/myconfiguration.xml" org.apache.qpid.management.domain.services.QMan


Stopping QMan

Type "q" In the console from which QMan has been started.

Browsing Manageable Beams

The jconsole tool (JMX-compliant graphical tool for monitoring a Java virtual machine) can be used for monitoring and QMan Mbeans. for more information see http://java.sun.com/javase/6/docs/technotes/guides/management/jconsole.html

The jconsole executable can be found in JDK_HOME/bin, where JDK_HOME is the directory in which the JDK software is installed. If this directory is in your system path, you can start JConsole by simply typing jconsole in a console. Otherwise, you have to type the full path to the executable file.

As jconsole needs to perform operations invocation you will need to add the QMan jar in jconsole classpath. In a console type:

jconsole -J-Djava.class.path=$CLASSPATH:$JAVA_HOME/lib/jconsole.jar:$JAVA_HOME/lib/tools.jar

Where CLASSPATH contains the QMan jars and JAVA_HOME point on your JDK home.

As demonstrated on the following screenshot, once jconsole is running select the MBeans tab and select the Q-MAN set of MBeans.

 

The screenshot above depicts the value of a queue attributes.

Invoking Operations

jconsole can be used for invoking operations. For example, the following screshot shows the queue message_queue attributes.



We can see that 22 messages have been enqueued when only 11 messages have been dequeued. This means that message_queue contains 11 messages. Let's delete 5 of them! For doing that we must select the operation purge of the queue message_queue. The following screeshot shows that the operation purge has one parameter that specify the number of messages to be discarded.



We invoke the purge operation with 5 messages. The following popup window tells us that the operation has been successfully invoked.



We can now check that 5 messages have been dequeued form message_queue. The following screenshot shows the updated attributes  of message_queue.



As shown above there are now 16 messages that have been dequeued.

Deploying the QMan servlet

QMan comes with a servlet that can be deployed in any application server. In the following we show how to deploy the qman servlet within JBoss application server.

Prerequisites

You mus install JBoss:

	Download the latest stable version from: http://www.jboss.org/jbossas/downloads/
	Unzip the download archive in 



Deploying the QMan servlet within JBoss 

First you need to copy the provided qman.war in /server/default/deploy/ (note that you can use another server configuration like for example minimal)

Then run JBoss:

	Add the following option-Djboss.platform.mbeanserver to JAVA_OPTS (for example: export JAVA_OP

[CONF] Apache Qpid: Qman Tool (page edited)

2008-10-29 Thread confluence 










Page Edited :
qpid :
Qman Tool



 
Qman Tool
has been edited by Arnaud
(Oct 29, 2008).
 

 
 (View changes)
 

Content:
Introduction

QMan is a Management bridge that exposes one (or several) Qpid broker domain model as MBeans that are accessible through the Java Management Extensions (JMX).

How to run QMan


Prerequisites

QMan is a standalone application that is packaged as qpid-management-client-incubating-M3.jar. To run QMan you need to add the following jars in your CLASSPATH:

	log4j-1.2.12.jar
	slf4j-api-1.4.0.jar
	slf4j-log4j12-1.4.0.jar
	commons-pool-1.4.jar
	commons-codec-1.3.jar
	commons-lang-2.2.jar
	commons-collections-3.2.jar
	commons-configuration-1.2.jar
	qpid-client-incubating-Mx.jar (were x is the current qpid version)
	qpid-common-incubating-Mx.jar (were x is the current qpid version)



alternatively you can run the following script (that add all the qpid jars to the CLASSPATH):
> CLASSPATH=`find  -name '*.jar' | tr '\n' ":"`
Where  is the directory containing the qpid jars (when qpid is built from source  is equal to qpid/java/build/lib)

QMan can be connected at run time against any broker. However if you wish to automatically connect to one or several brokers you can do so by providing a configuration file as follows:


  
	
	  localhost
	  5672
	  test
	  guest
	  guest
	  4
	  0
	  -1
	

	  myhost
	  5672
	  test
	  guest
	  guest
	  4
	  0
	  -1
	
  


The configuration above specifies that QMan should connect to two brokers, one on localhos and one on myhost, both listening on port 5672.

The configuration file to use is specified through the JVM parameter "qman-config" that must point onto a valid configuration file.

Running QMan

To run QMan in a console run the following command:

java org.apache.qpid.management.domain.services.QMan

Messages similar to those should be displayed:

... [org.apache.qpid.management.domain.services.QMan]  : Starting Q-Man...
...
Type "q" to quit.

if you wish to use a configuration file /myconfiguration.xml so QMan establishes a connection with one or several brokers, run the following command:

java -Dqman-config="/myconfiguration.xml" org.apache.qpid.management.domain.services.QMan


Stopping QMan

Type "q" In the console from which QMan has been started.

Browsing Manageable Beams

The jconsole tool (JMX-compliant graphical tool for monitoring a Java virtual machine) can be used for monitoring and QMan Mbeans. for more information see http://java.sun.com/javase/6/docs/technotes/guides/management/jconsole.html

The jconsole executable can be found in JDK_HOME/bin, where JDK_HOME is the directory in which the JDK software is installed. If this directory is in your system path, you can start JConsole by simply typing jconsole in a console. Otherwise, you have to type the full path to the executable file.

As jconsole needs to perform operations invocation you will need to add the QMan jar in jconsole classpath. In a console type:

jconsole -J-Djava.class.path=$CLASSPATH:$JAVA_HOME/lib/jconsole.jar:$JAVA_HOME/lib/tools.jar

Where CLASSPATH contains the QMan jars and JAVA_HOME point on your JDK home.

As demonstrated on the following screenshot, once jconsole is running select the MBeans tab and select the Q-MAN set of MBeans.

 

The screenshot above depicts the value of a queue attributes.

Invoking Operations

jconsole can be used for invoking operations. For example, the following screshot shows the queue message_queue attributes.



We can see that 22 messages have been enqueued when only 11 messages have been dequeued. This means that message_queue contains 11 messages. Let's delete 5 of them! For doing that we must select the operation purge of the queue message_queue. The following screeshot shows that the operation purge has one parameter that specify the number of messages to be discarded.



We invoke the purge operation with 5 messages. The following popup window tells us that the operation has been successfully invoked.



We can now check that 5 messages have been dequeued form message_queue. The following screenshot shows the updated attributes  of message_queue.



As shown above there are now 16 messages that have been dequeued.

Deploying the QMan servlet

QMan comes with a servlet that can be deployed in any application server. In the following we show how to deploy the qman servlet within JBoss application server.

Prerequisites

You mus install JBoss:

	Download the latest stable version from: http://www.jboss.org/jbossas/downloads/
	Unzip the download archive in 



Deploying the QMan servlet

First you need to copy the provided qman.war in /server/default/deploy/ (note that you can use another server configuration like for example minimal)

Then run JBoss:

	Add the following option-Djboss.platform.mbeanserver to JAVA_OPTS (for example: export JAVA_OPTS=-Djboss.pla

[CONF] Apache Qpid: Qman Tool (page edited)

2008-10-29 Thread confluence 










Page Edited :
qpid :
Qman Tool



 
Qman Tool
has been edited by Arnaud
(Oct 29, 2008).
 

 
 (View changes)
 

Content:
Introduction

QMan is a Management bridge that exposes one (or several) Qpid broker domain model as MBeans that are accessible through the Java Management Extensions (JMX).

How to run QMan


Prerequisites

QMan is a standalone application that is packaged as qpid-management-client-incubating-M3.jar. To run QMan you need to add the following jars in your CLASSPATH:

	log4j-1.2.12.jar
	slf4j-api-1.4.0.jar
	slf4j-log4j12-1.4.0.jar
	commons-pool-1.4.jar
	commons-codec-1.3.jar
	commons-lang-2.2.jar
	commons-collections-3.2.jar
	commons-configuration-1.2.jar
	qpid-client-incubating-Mx.jar (were x is the current qpid version)
	qpid-common-incubating-Mx.jar (were x is the current qpid version)



alternatively you can run the following script (that add all the qpid jars to the CLASSPATH):
> CLASSPATH=`find  -name '*.jar' | tr '\n' ":"`
Where  is the directory containing the qpid jars (when qpid is built from source  is equal to qpid/java/build/lib)

QMan can be connected at run time against any broker. However if you wish to automatically connect to one or several brokers you can do so by providing a configuration file as follows: 


	
  
	
	  localhost
	  5672
	  test
	  guest
	  guest
	  4
	  0
	  -1
	

	  myhost
	  5672
	  test
	  guest
	  guest
	  4
	  0
	  -1
	
  



The configuration above specifies that QMan should connect to two brokers, one on localhos and one on myhost, both listening on port 5672. 

The configuration file to use is specified through the JVM parameter "qman-config" that must point onto a valid configuration file. 

Running QMan

To run QMan in a console run the following command:

java org.apache.qpid.management.domain.services.QMan

Messages similar to those should be displayed:

... [org.apache.qpid.management.domain.services.QMan]  : Starting Q-Man...
...
Type "q" to quit.


if you wish to use a configuration file /myconfiguration.xml so QMan establishes a connection with one or several brokers, run the following command: 

java -Dqman-config="/myconfiguration.xml" org.apache.qpid.management.domain.services.QMan


Stopping QMan

Type "q" In the console from which QMan has been started.

Browsing Manageable Beams

The jconsole tool (JMX-compliant graphical tool for monitoring a Java virtual machine) can be used for monitoring and QMan Mbeans. for more information see http://java.sun.com/javase/6/docs/technotes/guides/management/jconsole.html 

The jconsole executable can be found in JDK_HOME/bin, where JDK_HOME is the directory in which the JDK software is installed. If this directory is in your system path, you can start JConsole by simply typing jconsole in a console. Otherwise, you have to type the full path to the executable file.

As jconsole needs to perform operations invocation you will need to add the QMan jar in jconsole classpath. In a console type: 


jconsole -J-Djava.class.path=$CLASSPATH:$JAVA_HOME/lib/jconsole.jar:$JAVA_HOME/lib/tools.jar
 

Where CLASSPATH contains the QMan jars and JAVA_HOME point on your JDK home. 

As demonstrated on the following screenshot, once jconsole is running select the MBeans tab and select the Q-MAN set of MBeans. 

 

The screenshot above depicts the value of a queue attributes. 

Invoking Operations

jconsole can be used for invoking operations. For example, the following screshot shows the queue message_queue attributes.  



We can see that 22 messages have been enqueued when only 11 messages have been dequeued. This means that message_queue contains 11 messages. Let's delete 5 of them! For doing that we must select the operation purge of the queue message_queue. The following screeshot shows that the operation purge has one parameter that specify the number of messages to be discarded. 



We invoke the purge operation with 5 messages. The following popup window tells us that the operation has been successfully invoked. 



We can now check that 5 messages have been dequeued form message_queue. The following screenshot shows the updated attributes  of message_queue. 



As shown above there are now 16 messages that have been dequeued. 

Deploying the QMan servlet

QMan comes with a servlet that can be deployed in any application server. In the following we show how to deploy the qman servlet within JBoss application server. 

Prerequisites 

You mus first install JBoss: 

	Download the latest stable version from: http://www.jboss.org/jbossas/downloads/
	Unzip the download archive



Run JBoss with the Mbean server: 

	Add the following option-Djboss.platform.mbeanserver to JAVA_OPTS (for example: export JAVA_OPTS=-Djboss.platform.mbeanserver)
	Execute /binrun.sh (or run.bat on a windows platform)














Powered by
Atlassian C

[CONF] Apache Qpid: Qman Tool (page edited)

2008-10-29 Thread confluence 










Page Edited :
qpid :
Qman Tool



 
Qman Tool
has been edited by Arnaud
(Oct 29, 2008).
 

 
 (View changes)
 

Content:
Introduction

QMan is a Management bridge that exposes one (or several) Qpid broker domain model as MBeans that are accessible through the Java Management Extensions (JMX).

How to run QMan


Prerequisites

QMan is a standalone application that is packaged as qpid-management-client-incubating-M3.jar. To run QMan you need to add the following jars in your CLASSPATH:

	log4j-1.2.12.jar
	slf4j-api-1.4.0.jar
	slf4j-log4j12-1.4.0.jar
	commons-pool-1.4.jar
	commons-codec-1.3.jar
	commons-lang-2.2.jar
	commons-collections-3.2.jar
	commons-configuration-1.2.jar
	qpid-client-incubating-Mx.jar (were x is the current qpid version)
	qpid-common-incubating-Mx.jar (were x is the current qpid version)



alternatively you can run the following script (that add all the qpid jars to the CLASSPATH):
> CLASSPATH=`find  -name '*.jar' | tr '\n' ":"`
Where  is the directory containing the qpid jars (when qpid is built from source  is equal to qpid/java/build/lib)

QMan can be connected at run time against any broker. However if you wish to automatically connect to one or several brokers you can do so by providing a configuration file as follows: 


	
  
	
	  localhost
	  5672
	  test
	  guest
	  guest
	  4
	  0
	  -1
	

	  myhost
	  5672
	  test
	  guest
	  guest
	  4
	  0
	  -1
	
  



The configuration above specifies that QMan should connect to two brokers, one on localhos and one on myhost, both listening on port 5672. 

The configuration file to use is specified through the JVM parameter "qman-config" that must point onto a valid configuration file. 

Running QMan

To run QMan in a console run the following command:

java org.apache.qpid.management.domain.services.QMan

Messages similar to those should be displayed:

... [org.apache.qpid.management.domain.services.QMan]  : Starting Q-Man...
...
Type "q" to quit.


if you wish to use a configuration file /myconfiguration.xml so QMan establishes a connection with one or several brokers, run the following command: 

java -Dqman-config="/myconfiguration.xml" org.apache.qpid.management.domain.services.QMan


Stopping QMan

Type "q" In the console from which QMan has been started.

Browsing Manageable Beams

The jconsole tool (JMX-compliant graphical tool for monitoring a Java virtual machine) can be used for monitoring and QMan Mbeans. for more information see http://java.sun.com/javase/6/docs/technotes/guides/management/jconsole.html 

The jconsole executable can be found in JDK_HOME/bin, where JDK_HOME is the directory in which the JDK software is installed. If this directory is in your system path, you can start JConsole by simply typing jconsole in a console. Otherwise, you have to type the full path to the executable file.

As jconsole needs to perform operations invocation you will need to add the QMan jar in jconsole classpath. In a console type: 


jconsole -J-Djava.class.path=$CLASSPATH:$JAVA_HOME/lib/jconsole.jar:$JAVA_HOME/lib/tools.jar
 

Where CLASSPATH contains the QMan jars and JAVA_HOME point on your JDK home. 

As demonstrated on the following screenshot, once jconsole is running select the MBeans tab and select the Q-MAN set of MBeans. 

 

The screenshot above depicts the value of a queue attributes. 

Invoking Operations

jconsole can be used for invoking operations. For example, the following screshot shows the queue message_queue attributes.  



We can see that 22 messages have been enqueued when only 11 messages have been dequeued. This means that message_queue contains 11 messages. Let's delete 5 of them! For doing that we must select the operation purge of the queue message_queue. The following screeshot shows that the operation purge has one parameter that specify the number of messages to be discarded. 



We invoke the purge operation with 5 messages. The following popup window tells us that the operation has been successfully invoked. 



We can now check that 5 messages have been dequeued form message_queue. The following screenshot shows the updated attributes  of message_queue. 



As shown above there are now 16 messages that have been dequeued. 











Powered by
Atlassian Confluence
(Version: 2.2.9 Build:#527 Sep 07, 2006)
-
Bug/feature request

Unsubscribe or edit your notifications preferences

[CONF] Apache Qpid: Qman Tool (page edited)

2008-10-29 Thread confluence 










Page Edited :
qpid :
Qman Tool



 
Qman Tool
has been edited by Arnaud
(Oct 29, 2008).
 

 
 (View changes)
 

Content:
Introduction

QMan is a Management bridge that exposes one (or several) Qpid broker domain model as MBeans that are accessible through the Java Management Extensions (JMX).

How to run QMan


Prerequisites

QMan is a standalone application that is packaged as qpid-management-client-incubating-M3.jar. To run QMan you need to add the following jars in your CLASSPATH:

	log4j-1.2.12.jar
	slf4j-api-1.4.0.jar
	slf4j-log4j12-1.4.0.jar
	commons-pool-1.4.jar
	commons-codec-1.3.jar
	commons-lang-2.2.jar
	commons-collections-3.2.jar
	commons-configuration-1.2.jar
	qpid-client-incubating-Mx.jar (were x is the current qpid version)
	qpid-common-incubating-Mx.jar (were x is the current qpid version)



alternatively you can run the following script (that add all the qpid jars to the CLASSPATH):
> CLASSPATH=`find  -name '*.jar' | tr '\n' ":"`
Where  is the directory containing the qpid jars (when qpid is built from source  is equal to qpid/java/build/lib)

QMan can be connected at run time against any broker. However if you wish to automatically connect to one or several brokers you can do so by providing a configuration file as follows: 


	
  
	
	  localhost
	  5672
	  test
	  guest
	  guest
	  4
	  0
	  -1
	

	  myhost
	  5672
	  test
	  guest
	  guest
	  4
	  0
	  -1
	
  



The configuration above specifies that QMan should connect to two brokers, one on localhos and one on myhost, both listening on port 5672. 

The configuration file to use is specified through the JVM parameter "qman-config" that must point onto a valid configuration file. 

Running QMan

To run QMan in a console run the following command:

java org.apache.qpid.management.domain.services.QMan

Messages similar to those should be displayed:

... [org.apache.qpid.management.domain.services.QMan]  : Starting Q-Man...
...
Type "q" to quit.


if you wish to use a configuration file /myconfiguration.xml so QMan establishes a connection with one or several brokers, run the following command: 

java -Dqman-config="/myconfiguration.xml" org.apache.qpid.management.domain.services.QMan


Stopping QMan

Type "q" In the console from which QMan has been started.

Browsing Manageable Beams

The jconsole tool (JMX-compliant graphical tool for monitoring a Java virtual machine) can be used for monitoring and QMan Mbeans. for more information see http://java.sun.com/javase/6/docs/technotes/guides/management/jconsole.html 

The jconsole executable can be found in JDK_HOME/bin, where JDK_HOME is the directory in which the JDK software is installed. If this directory is in your system path, you can start JConsole by simply typing jconsole in a console. Otherwise, you have to type the full path to the executable file.

As jconsole needs to perform operations invocation you will need to add the QMan jar in jconsole classpath. In a console type: 


jconsole -J-Djava.class.path=$CLASSPATH:$JAVA_HOME/lib/jconsole.jar:$JAVA_HOME/lib/tools.jar
 

Where CLASSPATH contains the QMan jars and JAVA_HOME point on your JDK home. 

As demonstrated on the following screen shot, once jconsole is running select the MBeans tab and select the Q-MAN set of MBeans. 

 











Powered by
Atlassian Confluence
(Version: 2.2.9 Build:#527 Sep 07, 2006)
-
Bug/feature request

Unsubscribe or edit your notifications preferences

[CONF] Apache Qpid: Qman Tool (page edited)

2008-10-29 Thread confluence 










Page Edited :
qpid :
Qman Tool



 
Qman Tool
has been edited by Arnaud
(Oct 29, 2008).
 

 
 (View changes)
 

Content:
Introduction

QMan is a Management bridge that exposes one (or several) Qpid broker domain model as MBeans that are accessible through the Java Management Extensions (JMX).

How to run QMan


Prerequisites

QMan is a standalone application that is packaged as qpid-management-client-incubating-M3.jar. To run QMan you need to add the following jars in your CLASSPATH:

	log4j-1.2.12.jar
	slf4j-api-1.4.0.jar
	slf4j-log4j12-1.4.0.jar
	commons-pool-1.4.jar
	commons-codec-1.3.jar
	commons-lang-2.2.jar
	commons-collections-3.2.jar
	commons-configuration-1.2.jar
	qpid-client-incubating-Mx.jar (were x is the current qpid version)
	qpid-common-incubating-Mx.jar (were x is the current qpid version)



alternatively you can run the following script (that add all the qpid jars to the CLASSPATH):
> CLASSPATH=`find  -name '*.jar' | tr '\n' ":"`
Where  is the directory containing the qpid jars (when qpid is built from source  is equal to qpid/java/build/lib)

QMan can be connected at run time against any broker however it must first connect to a running broker.  As default QMan will try to connect to a broker running on localhost port 5672.

The file config.xml that must be located in a directory referenced by the CLASSPATH can be used for configuring QMAN. The default content of this file is:


	
		
			1
			org.apache.qpid.management.domain.model.type.Uint8
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator

		
		
			2
			org.apache.qpid.management.domain.model.type.Uint16
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator

		
		
			3
			org.apache.qpid.management.domain.model.type.Uint32
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator

		
		
			4
			org.apache.qpid.management.domain.model.type.Uint64
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator<
/validator-class-name>
		
		
			6
			org.apache.qpid.management.domain.model.type.Str8
			org.apache.qpid.management.domain.model.QpidProperty$StringValidator

		
		
			7
			org.apache.qpid.management.domain.model.type.Str16
			org.apache.qpid.management.domain.model.QpidProperty$StringValidator

		
		
			8
			org.apache.qpid.management.domain.model.type.AbsTime

		
		
			9
			org.apache.qpid.management.domain.model.type.DeltaTime

		
		
			10
			org.apache.qpid.management.domain.model.type.ObjectReference
		
		
			11
			org.apache.qpid.management.domain.model.type.Boolean
		
		
			14
			org.apache.qpid.management.domain.model.type.Uuid
		
		
			15
			org.apache.qpid.management.domain.model.type.Map
		
	
	
		
			1
			RC
		
		
			2
			RW
		
		
			3
			RO
		
	
	
		
			localhost
			5672
			test
			guest
			guest
			4
			0
			-1
		
	


Several brokers can be added so that QMan will try to connect to those broker at starting time.

Running QMan

To run QMan in a console run the following command:

java org.apache.qpid.management.domain.services.QMan

Messages similar to those should be displayed:

... [org.apache.qpid.management.domain.services.QMan]  : Starting Q-Man...
...
Type "q" to quit.


Stopping QMan

Type "q" In the console from which QMan has been started.

Browsing Manageable Beams

The jconsole tool (JMX-compliant graphical tool for monitoring a Java virtual machine) can be used for monitoring and QMan Mbeans. for more information see http://java.sun.com/javase/6/docs/technotes/guides/management/jconsole.html 

The jconsole executable can be found in JDK_HOME/bin, where JDK_HOME is the directory in which the JDK software is installed. If this directory is in your system path, you can start JConsole by simply typing jconsole in a console. Otherwise, you have to type the full path to the executable file.

As demonstrated on the following screen shot, once jconsole is running select the MBeans tab and select the Q-MAN set of MBeans. 

 











Powered by
Atlassian Confluence
(Version: 2.2.9 Build:#527 Sep 07, 2006)
-
Bug/feature request

Unsubscribe or edit your notifications preferences

[CONF] Apache Qpid: Qman Tool (page edited)

2008-10-29 Thread confluence 










Page Edited :
qpid :
Qman Tool



 
Qman Tool
has been edited by Arnaud
(Oct 29, 2008).
 

 
 (View changes)
 

Content:
Introduction

QMan is a Management bridge that exposes one (or several) Qpid broker domain model as MBeans that are accessible through the Java Management Extensions (JMX).

How to run QMan


Prerequisites

QMan is a standalone application that is packaged as qpid-management-client-incubating-M3.jar. To run QMan you need to add the following jars in your CLASSPATH:

	log4j-1.2.12.jar
	slf4j-api-1.4.0.jar
	slf4j-log4j12-1.4.0.jar
	commons-pool-1.4.jar
	commons-codec-1.3.jar
	commons-lang-2.2.jar
	commons-collections-3.2.jar
	commons-configuration-1.2.jar
	qpid-client-incubating-Mx.jar (were x is the current qpid version)
	qpid-common-incubating-Mx.jar (were x is the current qpid version)



alternatively you can run the following script (that add all the qpid jars to the CLASSPATH):
> CLASSPATH=`find  -name '*.jar' | tr '\n' ":"`
Where  is the directory containing the qpid jars (when qpid is built from source  is equal to qpid/java/build/lib)

QMan can be connected at run time against any broker however it must first connect to a running broker.  As default QMan will try to connect to a broker running on localhost port 5672.

The file config.xml that must be located in a directory referenced by the CLASSPATH can be used for configuring QMAN. The default content of this file is:


	
		
			1
			org.apache.qpid.management.domain.model.type.Uint8
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			2
			org.apache.qpid.management.domain.model.type.Uint16
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			3
			org.apache.qpid.management.domain.model.type.Uint32
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			4
			org.apache.qpid.management.domain.model.type.Uint64
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			6
			org.apache.qpid.management.domain.model.type.Str8
			org.apache.qpid.management.domain.model.QpidProperty$StringValidator
		
		
			7
			org.apache.qpid.management.domain.model.type.Str16
			org.apache.qpid.management.domain.model.QpidProperty$StringValidator
		
		
			8
			org.apache.qpid.management.domain.model.type.AbsTime
		
		
			9
			org.apache.qpid.management.domain.model.type.DeltaTime
		
		
			10
			org.apache.qpid.management.domain.model.type.ObjectReference
		
		
			11
			org.apache.qpid.management.domain.model.type.Boolean
		
		
			14
			org.apache.qpid.management.domain.model.type.Uuid
		
		
			15
			org.apache.qpid.management.domain.model.type.Map
		
	
	
		
			1
			RC
		
		
			2
			RW
		
		
			3
			RO
		
	
	
		
			localhost
			5672
			test
			guest
			guest
			4
			0
			-1
		
	


Several brokers can be added so that QMan will try to connect to those broker at starting time.

Running QMan

To run QMan in a console run the following command:

java org.apache.qpid.management.domain.services.QMan

Messages similar to those should be displayed:

... [org.apache.qpid.management.domain.services.QMan]  : Starting Q-Man...
...
Type "q" to quit.


Stopping QMan

Type "q" In the console from which QMan has been started.

Browsing Manageable Beams

The jconsole tool (JMX-compliant graphical tool for monitoring a Java virtual machine) can be used for monitoring and QMan Mbeans. for more information see http://java.sun.com/javase/6/docs/technotes/guides/management/jconsole.html 

The jconsole executable can be found in JDK_HOME/bin, where JDK_HOME is the directory in which the JDK software is installed. If this directory is in your system path, you can start JConsole by simply typing jconsole in a console. Otherwise, you have to type the full path to the executable file.

As demonstrated on the following screen shot, once jconsole is running select the MBeans tab and select the Q-MAN set of MBeans. 

 











Powered by
Atlassian Confluence
(Version: 2.2.9 Build:#527 Sep 07, 2006)
-
Bug/feature request

Unsubscribe or edit your notifications preferences

[CONF] Apache Qpid: Qman Tool (page edited)

2008-10-29 Thread confluence 










Page Edited :
qpid :
Qman Tool



 
Qman Tool
has been edited by Arnaud
(Oct 29, 2008).
 

 
 (View changes)
 

Content:
Introduction

QMan is a Management bridge that exposes one (or several) Qpid broker domain model as MBeans that are accessible through the Java Management Extensions (JMX).

How to run QMan


Prerequisites

QMan is a standalone application that is packaged as qpid-management-client-incubating-M3.jar. To run QMan you need to add the following jars in your CLASSPATH:

	log4j-1.2.12.jar
	slf4j-api-1.4.0.jar
	slf4j-log4j12-1.4.0.jar
	commons-pool-1.4.jar
	commons-codec-1.3.jar
	commons-lang-2.2.jar
	commons-collections-3.2.jar
	commons-configuration-1.2.jar
	qpid-client-incubating-Mx.jar (were x is the current qpid version)
	qpid-common-incubating-Mx.jar (were x is the current qpid version)



alternatively you can run the following script (that add all the qpid jars to the CLASSPATH):
> CLASSPATH=`find  -name '*.jar' | tr '\n' ":"`
Where  is the directory containing the qpid jars (when qpid is built from source  is equal to qpid/java/build/lib)

QMan can be connected at run time against any broker however it must first connect to a running broker.  As default QMan will try to connect to a broker running on localhost port 5672.

The file config.xml that must be located in a directory referenced by the CLASSPATH can be used for configuring QMAN. The default content of this file is:


	
		
			1
			org.apache.qpid.management.domain.model.type.Uint8
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			2
			org.apache.qpid.management.domain.model.type.Uint16
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			3
			org.apache.qpid.management.domain.model.type.Uint32
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			4
			org.apache.qpid.management.domain.model.type.Uint64
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			6
			org.apache.qpid.management.domain.model.type.Str8
			org.apache.qpid.management.domain.model.QpidProperty$StringValidator
		
		
			7
			org.apache.qpid.management.domain.model.type.Str16
			org.apache.qpid.management.domain.model.QpidProperty$StringValidator
		
		
			8
			org.apache.qpid.management.domain.model.type.AbsTime
		
		
			9
			org.apache.qpid.management.domain.model.type.DeltaTime
		
		
			10
			org.apache.qpid.management.domain.model.type.ObjectReference
		
		
			11
			org.apache.qpid.management.domain.model.type.Boolean
		
		
			14
			org.apache.qpid.management.domain.model.type.Uuid
		
		
			15
			org.apache.qpid.management.domain.model.type.Map
		
	
	
		
			1
			RC
		
		
			2
			RW
		
		
			3
			RO
		
	
	
		
			localhost
			5672
			test
			guest
			guest
			4
			0
			-1
		
	


Several brokers can be added so that QMan will try to connect to those broker at starting time.

Running QMan

To run QMan in a console run the following command:

java org.apache.qpid.management.domain.services.QMan

Messages similar to those should be displayed:

2008-10-29 14:45:17,686 INFO  [org.apache.qpid.management.domain.services.QMan]  : Starting Q-Man...
2008-10-29 14:45:17,687 INFO  [org.apache.qpid.management.domain.services.QMan]  : Reading Q-Man configuration...
2008-10-29 14:45:17,747 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 1 associated to org.apache.qpid.management.domain.model.type.Uint8 (wraps java.lang.Short) (validator class is org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2008-10-29 14:45:17,748 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 2 associated to org.apache.qpid.management.domain.model.type.Uint16 (wraps java.lang.Integer) (validator class is org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2008-10-29 14:45:17,750 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 3 associated to org.apache.qpid.management.domain.model.type.Uint32 (wraps java.lang.Long) (validator class is org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2008-10-29 14:45:17,752 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 4 associated to org.apache.qpid.management.domain.model.type.Uint64 (wraps java.lang.Long) (validator class is org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2008-10-29 14:45:17,753 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 6 associated to org.apache.qpid.management.domain.model.type.Str8 (wraps java.lang.String) (validator class is org.apache.qpid.management.domain.model.QpidProperty$StringValidator)
2008-10-29 14:45:17,754 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : cod

[CONF] Apache Qpid: Qman Tool (page edited)

2008-10-29 Thread confluence 










Page Edited :
qpid :
Qman Tool



 
Qman Tool
has been edited by Arnaud
(Oct 29, 2008).
 

 
 (View changes)
 

Content:
Introduction

QMan is a Management bridge that exposes one (or several) Qpid broker domain model as MBeans that are accessible through the Java Management Extensions (JMX).

How to run QMan


Prerequisites

QMan is a standalone application that is packaged as qpid-management-client-incubating-M3.jar. To run QMan you need to add the following jars in your CLASSPATH:

	log4j-1.2.12.jar
	slf4j-api-1.4.0.jar
	slf4j-log4j12-1.4.0.jar
	commons-pool-1.4.jar
	commons-codec-1.3.jar
	commons-lang-2.2.jar
	commons-collections-3.2.jar
	commons-configuration-1.2.jar
	qpid-client-incubating-Mx.jar (were x is the current qpid version)
	qpid-common-incubating-Mx.jar (were x is the current qpid version)



alternatively you can run the following script (that add all the qpid jars to the CLASSPATH):
> CLASSPATH=`find  -name '*.jar' | tr '\n' ":"`
Where  is the directory containing the qpid jars (when qpid is built from source  is equal to qpid/java/build/lib)

QMan can be connected at run time against any broker however it must first connect to a running broker.  As default QMan will try to connect to a broker running on localhost port 5672.

The file config.xml that must be located in a directory referenced by the CLASSPATH can be used for configuring QMAN. The default content of this file is:



	
		
			1
			org.apache.qpid.management.domain.model.type.Uint8
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			2
			org.apache.qpid.management.domain.model.type.Uint16
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			3
			org.apache.qpid.management.domain.model.type.Uint32
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			4
			org.apache.qpid.management.domain.model.type.Uint64
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			6
			org.apache.qpid.management.domain.model.type.Str8
			org.apache.qpid.management.domain.model.QpidProperty$StringValidator
		
		
			7
			org.apache.qpid.management.domain.model.type.Str16
			org.apache.qpid.management.domain.model.QpidProperty$StringValidator
		
		
			8
			org.apache.qpid.management.domain.model.type.AbsTime
		
		
			9
			org.apache.qpid.management.domain.model.type.DeltaTime
		
		
			10
			org.apache.qpid.management.domain.model.type.ObjectReference
		
		
			11
			org.apache.qpid.management.domain.model.type.Boolean
		
		
			14
			org.apache.qpid.management.domain.model.type.Uuid
		
		
			15
			org.apache.qpid.management.domain.model.type.Map
		
	
	
		
			1
			RC
		
		
			2
			RW
		
		
			3
			RO
		
	
	
		
			localhost
			5672
			test
			guest
			guest
			4
			0
			-1

	



Several brokers can be added so that QMan will try to connect to those broker at starting time. 

Running QMan 

To run QMan in a console run the following command: 


java org.apache.qpid.management.domain.services.QMan


Messages similar to those should be displayed: 


2008-10-29 14:45:17,686 INFO  [org.apache.qpid.management.domain.services.QMan]  : Starting Q-Man...
2008-10-29 14:45:17,687 INFO  [org.apache.qpid.management.domain.services.QMan]  : Reading Q-Man configuration...
2008-10-29 14:45:17,747 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 1 associated to org.apache.qpid.management.domain.model.type.Uint8 (wraps java.lang.Short) (validator class is org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2008-10-29 14:45:17,748 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 2 associated to org.apache.qpid.management.domain.model.type.Uint16 (wraps java.lang.Integer) (validator class is org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2008-10-29 14:45:17,750 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 3 associated to org.apache.qpid.management.domain.model.type.Uint32 (wraps java.lang.Long) (validator class is org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2008-10-29 14:45:17,752 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 4 associated to org.apache.qpid.management.domain.model.type.Uint64 (wraps java.lang.Long) (validator class is org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2008-10-29 14:45:17,753 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 6 associated to org.apache.qpid.management.domain.model.type.Str8 (wraps java.lang.String) (validator class is org.apache.qpid.management.domain.model.QpidProperty$StringValidator)
2008-10-29 14:45:17,754 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type ma

[CONF] Apache Qpid: Qman Tool (page edited)

2008-10-29 Thread confluence 










Page Edited :
qpid :
Qman Tool



 
Qman Tool
has been edited by Arnaud
(Oct 29, 2008).
 

 
 (View changes)
 

Content:
Introduction

QMan is a Management bridge that exposes one (or several) Qpid broker domain model as MBeans that are accessible through the Java Management Extensions (JMX).

How to run QMan


Prerequisites

QMan is a standalone application that is packaged as qpid-management-client-incubating-M3.jar. To run QMan you need to add the following jars in your CLASSPATH:

	log4j-1.2.12.jar
	slf4j-api-1.4.0.jar
	slf4j-log4j12-1.4.0.jar
	commons-pool-1.4.jar
	commons-codec-1.3.jar
	commons-lang-2.2.jar
	commons-collections-3.2.jar
	commons-configuration-1.2.jar
	qpid-client-incubating-Mx.jar (were x is the current qpid version)
	qpid-common-incubating-Mx.jar (were x is the current qpid version)



alternatively you can run the following script (that add all the qpid jars to the CLASSPATH):
> CLASSPATH=`find  -name '*.jar' | tr '\n' ":"`
Where  is the directory containing the qpid jars (when qpid is built from source  is equal to qpid/java/build/lib)

QMan can be connected at run time against any broker however it must first connect to a running broker.  As default QMan will try to connect to a broker running on localhost port 5672.

The file config.xml that must be located in a directory referenced by the CLASSPATH can be used for configuring QMAN. The default content of this file is:



	
		
			1
			org.apache.qpid.management.domain.model.type.Uint8
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			2
			org.apache.qpid.management.domain.model.type.Uint16
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			3
			org.apache.qpid.management.domain.model.type.Uint32
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			4
			org.apache.qpid.management.domain.model.type.Uint64
			org.apache.qpid.management.domain.model.QpidProperty$NumberValidator
		
		
			6
			org.apache.qpid.management.domain.model.type.Str8
			org.apache.qpid.management.domain.model.QpidProperty$StringValidator
		
		
			7
			org.apache.qpid.management.domain.model.type.Str16
			org.apache.qpid.management.domain.model.QpidProperty$StringValidator
		
		
			8
			org.apache.qpid.management.domain.model.type.AbsTime
		
		
			9
			org.apache.qpid.management.domain.model.type.DeltaTime
		
		
			10
			org.apache.qpid.management.domain.model.type.ObjectReference
		
		
			11
			org.apache.qpid.management.domain.model.type.Boolean
		
		
			14
			org.apache.qpid.management.domain.model.type.Uuid
		
		
			15
			org.apache.qpid.management.domain.model.type.Map
		
	
	
		
			1
			RC
		
		
			2
			RW
		
		
			3
			RO
		
	
	
		
			localhost
			5672
			test
			guest
			guest
			4
			0
			-1

	



Several brokers can be added so that QMan will try to connect to those broker at starting time. 

Running QMan 

To run QMan in a console run the following command: 


java org.apache.qpid.management.domain.services.QMan


Messages similar to those should be displayed: 


2008-10-29 14:45:17,686 INFO  [org.apache.qpid.management.domain.services.QMan]  : Starting Q-Man...
2008-10-29 14:45:17,687 INFO  [org.apache.qpid.management.domain.services.QMan]  : Reading Q-Man configuration...
2008-10-29 14:45:17,747 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 1 associated to org.apache.qpid.management.domain.model.type.Uint8 (wraps java.lang.Short) (validator class is org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2008-10-29 14:45:17,748 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 2 associated to org.apache.qpid.management.domain.model.type.Uint16 (wraps java.lang.Integer) (validator class is org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2008-10-29 14:45:17,750 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 3 associated to org.apache.qpid.management.domain.model.type.Uint32 (wraps java.lang.Long) (validator class is org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2008-10-29 14:45:17,752 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 4 associated to org.apache.qpid.management.domain.model.type.Uint64 (wraps java.lang.Long) (validator class is org.apache.qpid.management.domain.model.QpidProperty$NumberValidator)
2008-10-29 14:45:17,753 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type mapping : code = 6 associated to org.apache.qpid.management.domain.model.type.Str8 (wraps java.lang.String) (validator class is org.apache.qpid.management.domain.model.QpidProperty$StringValidator)
2008-10-29 14:45:17,754 INFO  [org.apache.qpid.management.configuration.Configuration]  : Type ma

[CONF] Apache Qpid: Qman Tool (page edited)

2008-10-29 Thread confluence 










Page Edited :
qpid :
Qman Tool



 
Qman Tool
has been edited by Arnaud
(Oct 29, 2008).
 

 
 (View changes)
 

Content:
Introduction

QMan is a Management bridge that exposes one (or several) Qpid broker domain model as MBeans that are accessible through the Java Management Extensions (JMX).

How to run QMan

QMan is a standalone application that is packaged as qpid-management-client-incubating-M3.jar. To run QMan you need to add the following jars in your CLASSPATH:

	log4j-1.2.12.jar
	slf4j-api-1.4.0.jar
	slf4j-log4j12-1.4.0.jar
	commons-pool-1.4.jar
	commons-codec-1.3.jar
	commons-lang-2.2.jar
	commons-collections-3.2.jar
	commons-configuration-1.2.jar
	qpid-client-incubating-Mx.jar (were x is the current qpid version)
	qpid-common-incubating-Mx.jar (were x is the current qpid version)













Powered by
Atlassian Confluence
(Version: 2.2.9 Build:#527 Sep 07, 2006)
-
Bug/feature request

Unsubscribe or edit your notifications preferences