Monitoring Active JMS Connections
Active JMS connections are listed below sub-context sys$jms/usage as entities with their remote hostname and port.
Example:
router1> cc sys$jms/usage router1/sys$jms/usage> lc Entity List: Usage List Description: List of all active JMS Connections Entities in this List: ---------------------- pamela.iit.de:1034 router1/sys$jms/usage>_
|
Each connection entity contains read-only properties, that are describing the connection, and 2 sub-contexts, containing the active JMS sessions and active temporary queues of that connection.
Example:
router1/sys$jms/usage> cc pamela.iit.de:1034 router1/sys$jms/usage/pamela.iit.de:1034> lc Entity: JMS Connection Description: Active JMS Connection Properties for this Entity: Name Current Value -------------------------------------------------------------- clientid (R/O) router1:1 logintime (R/O) Mon May 22 06:43:38 GMT+02:00 2000 started (R/O) true username (R/O) admin Sub-Entities of this Entity: ---------------------------- sessions tempqueues router1/sys$jms/usage/pamela.iit.de:1034>_
|
Monitoring Active JMS Sessions
Active JMS sessions of a connection are listed below sub-context sys$jms/usage/<jmsconn>/sessions as entities with their session numbers.
Example:
router1/sys$jms/usage/pamela.iit.de:1034> cc sessions router1/sys$jms/usage/pamela.iit.de:1034/sessions> lc Entity List: JMS Session List Description: List of all active JMS Sessions Entities in this List: ---------------------- 1 2 router1/sys$jms/usage/pamela.iit.de:1034/sessions>_
|
Each session entity contains read-only properties, that are describing the session, and 6 sub-contexts, containing the active queue browser/sender/reciver and topic publisher/subscriber/durable subscriber of that session.
Example:
router1/sys$jms/usage/pamela.iit.de:1034/sessions> cc 1 router1/sys$jms/usage/pamela.iit.de:1034/sessions/1> lc Entity: JMS Session Description: Active JMS Session Properties for this Entity: Name Current Value -------------------------------------------------------------- acknowledgemode (R/O) AUTO_ACKNOWLEDGE transacted (R/O) false Sub-Entities of this Entity: ---------------------------- browser durable publisher receiver sender subscriber router1/sys$jms/usage/pamela.iit.de:1034/sessions/1>
|
Monitoring Active Queue Browser
Active queue browser of a session are listed below sub-context sys$jms/usage/<jmsconn>/sessions/<sessionid>/browser as entities with their queue names, extended by a browser id.
Example:
router1/sys$jms/usage/pamela.iit.de:1034/sessions/2> cc browser router1/sys$jms/usage/pamela.iit.de:1034/sessions/2/browser> lc Entity List: Queue Browser List Description: List of all active Queue Browser Entities in this List: ---------------------- airplanequeue0-0 router1/sys$jms/usage/pamela.iit.de:1034/sessions/2/browser>_
|
Each browser entity contains read-only properties, that are describing the browser.
Example:
router1/sys$jms/usage/pamela.iit.de:1034/sessions/2/browser> lc airplanequeue0-0 Entity: Queue Browser Description: Active Queue Browser Properties for this Entity: Name Current Value -------------------------------------------------------------- queue (R/O) airplanequeue0 selector (R/O) plaintype like 'Airbus A3__' Entity contains no Sub-Entities. router1/sys$jms/usage/pamela.iit.de:1034/sessions/2/browser>_
|
Monitoring Active Queue Sender
Active queue sender of a session are listed below sub-context sys$jms/usage/<jmsconn>/sessions/<sessionid>/sender as entities with their queue names, extended by a sender id.
Example:
router1/sys$jms/usage/pamela.iit.de:1034/sessions/2> cc sender router1/sys$jms/usage/pamela.iit.de:1034/sessions/2/sender> lc Entity List: Queue Sender List Description: List of all active Queue Sender Entities in this List: ---------------------- swiftmqmgmt-0 swiftmqmgmt@router1-1 swiftmqmgmt@router2-2 router1/sys$jms/usage/pamela.iit.de:1034/sessions/2/sender>_
|
Each sender entity contains read-only properties, that are describing the sender.
Example:
router1/sys$jms/usage/pamela.iit.de:1034/sessions/2/sender> cc swiftmqmgmt-0 router1/sys$jms/usage/pamela.iit.de:1034/sessions/2/sender/swiftmqmgmt-0> lc Entity: Queue Sender Description: Active Queue Sender Properties for this Entity: Name Current Value -------------------------------------------------------------- queue (R/O) swiftmqmgmt Entity contains no Sub-Entities. router1/sys$jms/usage/pamela.iit.de:1034/sessions/2/sender/swiftmqmgmt-0>_
|
Monitoring Active Queue Receiver
Active queue receiver of a session are listed below sub-context sys$jms/usage/<jmsconn>/sessions/<sessionid>/receiver as entities with their queue names, extended by a receiver id.
Example:
router1/sys$jms/usage/pamela.iit.de:1034/sessions/1> cc receiver router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/receiver> lc Entity List: Queue Receiver List Description: List of all active Queue Receiver Entities in this List: ---------------------- tmp$2@router1-0 router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/receiver>_
|
Each receiver entity contains read-only properties, that are describing the receiver.
Example:
router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/receiver> lc tmp$2@router1-0 Entity: Queue Receiver Description: Active Queue Receiver Properties for this Entity: Name Current Value -------------------------------------------------------------- queue (R/O) tmp$2@router1 selector (R/O) <not set> Entity contains no Sub-Entities. router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/receiver>_
|
Monitoring Active Topic Publisher
Active topic publisher of a session are listed below sub-context sys$jms/usage/<jmsconn>/sessions/<sessionid>/publisher as entities with their topic predicates, extended by a publisher id.
Example:
router1/sys$jms/usage/pamela.iit.de:1034/sessions/1> cc p router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/p> lc Entity List: Topic Publisher List Description: List of all active Topic Publisher Entities in this List: ---------------------- swiftmq.jndi-0 router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/p>_
|
Each publisher entity contains read-only properties, that are describing the publisher.
Example:
router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/p> cc s router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/p/s> lc Entity: Topic Publisher Description: Active Topic Publisher Properties for this Entity: Name Current Value -------------------------------------------------------------- topic (R/O) swiftmq.jndi Entity contains no Sub-Entities. router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/p/s>_
|
Monitoring Active Topic Subscriber
Active topic subscriber of a session are listed below sub-context sys$jms/usage/<jmsconn>/sessions/<sessionid>/subscriber as entities with their topic predicates, extended by a subscriber id.
Example:
router1/sys$jms/usage/pamela.iit.de:1034/sessions/1> cc sub router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/sub> lc Entity List: Topic Subscriber List Description: List of all active Topic Subscriber Entities in this List: ---------------------- iit.sales-0 router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/sub>_
|
Each subscriber entity contains read-only properties, that are describing the subscriber.
Example:
router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/sub> cc i router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/sub/i> lc Entity: Topic Subscriber Description: Active Topic Subscriber Properties for this Entity: Name Current Value -------------------------------------------------------------- boundto (R/O) tmp$5@router1 nolocal (R/O) true selector (R/O) <not set> temptopic false topic (R/O) iit.sales Entity contains no Sub-Entities. router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/sub/i>_
|
Monitoring Active Durable Subscriber
Active durable topic subscriber of a session are listed below sub-context sys$jms/usage/<jmsconn>/sessions/<sessionid>/durable as entities with their clientid/durable name combination.
Example:
router1/sys$jms/usage/pamela.iit.de:1034/sessions/1> cc d router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/d> lc Entity List: Durable Topic Subscriber List Description: List of all active Durable Topic Subscriber Entities in this List: ---------------------- Muelli$dur01 router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/d>_
|
Each durable subscriber entity contains read-only properties, that are describing the durable subscriber.
Example:
router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/d> cc M router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/d/M> lc Entity: Durable Topic Subscriber Description: Active Durable Topic Subscriber Properties for this Entity: Name Current Value -------------------------------------------------------------- boundto (R/O) Muelli$dur01 clientid (R/O) Muelli durablename (R/O) dur01 nolocal (R/O) false selector (R/O) JMSDeliveryMode = PERSISTENT topic (R/O) iit.sales Entity contains no Sub-Entities. router1/sys$jms/usage/pamela.iit.de:1034/sessions/1/d/M>_
|
Monitoring Active Temp. Queues
Temporary queues created by a connection are listed below the sub-context sys$jms/usage/<jmsconn>/tempqueues. The lifetime of a temporary queue is that of the connection. If the queue is not destroyed by the connection itself, it is automatically done when the connection is closed.
Example:
dev194.iit.de/sys$jms/usage/n> lc Entity: JMS Connection Description: Active JMS Connection Properties for this Entity: Name Current Value -------------------------------------------------------------- clientid (R/O) dev194.iit.de:1 logintime (R/O) Mon May 22 19:17:34 GMT+02:00 2000 started (R/O) true username (R/O) <not set> Sub-Entities of this Entity: ---------------------------- sessions tempqueues dev194.iit.de/sys$jms/usage/n> cc t dev194.iit.de/sys$jms/usage/n/t> lc Entity List: Temp Queue List Description: Active Temporary Queues Entities in this List: ---------------------- tmp$2@dev194.iit.de tmp$3@dev194.iit.de dev194.iit.de/sys$jms/usage/n/t>_
|
Deleting active JMS Connections
Deleting an active JMS connection is an administration task that leads to a graceful shutdown of the connection. The client detects a 'connection lost'. On the server side, all open transactions will be rolled back and all unacknowledged messages will be redelivered.
To delete a JMS connection, switch to context /sys$jms/usage and perform a delete command.
Example:
dev194.iit.de> cc sys$jms/usage dev194.iit.de/sys$jms/usage> lc Entity List: Usage List Description: List of all active JMS Connections Entities in this List: ---------------------- localhost:1207 dev194.iit.de:1150 dev194.iit.de/sys$jms/usage> delete localhost:1207 dev194.iit.de/sys$jms/usage> lc Entity List: Usage List Description: List of all active JMS Connections Entities in this List: ---------------------- dev194.iit.de:1150 dev194.iit.de/sys$jms/usage>_
|