The messagebrowser JAR
The messagebrowser JAR
Destination type is queue
Sending message: This is message 1
3. Go to the messagebrowser/dist directory.
4. Run the MessageBrowser program:
appclient -client messagebrowser.jar
The output of the program looks like this:
Message:
Text: This is message 1
Class: com.sun.messaging.jmq.jmsclient.TextMessageImpl
getJMSMessageID(): ID:12-129.148.71.199(8c:34:4a:1a:1b:b8)-40883-1129062957611
getJMSTimestamp(): 1129062957611
getJMSCorrelationID(): null
JMSReplyTo: null
JMSDestination: PhysicalQueue
getJMSDeliveryMode(): PERSISTENT
getJMSRedelivered(): false
getJMSType(): null
getJMSExpiration(): 0
getJMSPriority(): 4
Properties: null
Message:
Class: com.sun.messaging.jmq.jmsclient.MessageImpl
getJMSMessageID(): ID:13-129.148.71.199(8c:34:4a:1a:1b:b8)-40883-1129062957616
getJMSTimestamp(): 1129062957616
getJMSCorrelationID(): null
JMSReplyTo: null
JMSDestination: PhysicalQueue
getJMSDeliveryMode(): PERSISTENT
getJMSRedelivered(): false
getJMSType(): null
getJMSExpiration(): 0
getJMSPriority(): 4
Properties: null
The first message is the TextMessage, and the second is the non-text control message.
5. Go to the synchconsumer/dist directory.
6. Run the SynchConsumer program to consume the messages:
appclient -client synchconsumer.jar queue
The output of the program looks like this:
Destination type is queue
Reading message: This is message 1
Writing Simple JMS Client Applications
The Java EE 5 Tutorial · September 2007
930
