CHAPTER 6 Messaging on JBoss - JMS Configuration and Architecture

A P2P JMS client example

package org.jboss.chap6.ex1;

import javax.jms.JMSException;

import javax.jms.Message;

import javax.jms.MessageListener;

import javax.jms.Queue;

import javax.jms.QueueConnection;

import javax.jms.QueueConnectionFactory;

import javax.jms.QueueReceiver;

import javax.jms.QueueSender;

import javax.jms.QueueSession;

import javax.jms.TextMessage;

import javax.naming.InitialContext;

import javax.naming.NamingException;

import EDU.oswego.cs.dl.util.concurrent.CountDown;

/** A complete JMS client example program that sends a

TextMessage to a Queue and asynchronously receives the

message from the same Queue.

@author Scott.Stark@jboss.org

@version $Revision:$

*/

public class SendRecvClient

{

static CountDown done = new CountDown(1);

QueueConnection conn;

QueueSession session;

Queue que;

public static class ExListener implements MessageListener

{

public void onMessage(Message msg)

{

done.release();

TextMessage tm = (TextMessage) msg;

try

{

System.out.println("onMessage, recv text="

+ tm.getText());

}

catch(Throwable t)

{

t.printStackTrace();

}

}

}

public void setupPTP()

throws JMSException, NamingException

{

InitialContext iniCtx = new InitialContext();

Object tmp = iniCtx.lookup("ConnectionFactory");

QueueConnectionFactory qcf = (QueueConnectionFactory) tmp;

conn = qcf.createQueueConnection();

que = (Queue) iniCtx.lookup("queue/testQueue");

session = conn.createQueueSession(false,

QueueSession.AUTO_ACKNOWLEDGE);

conn.start();

}

public void sendRecvAsync(String text)

throws JMSException, NamingException

{

System.out.println("Begin sendRecvAsync");

// Setup the PTP connection, session

setupPTP();

// Set the async listener

QueueReceiver recv = session.createReceiver(que);

recv.setMessageListener(new ExListener());

// Send a text msg

QueueSender send = session.createSender(que);

TextMessage tm = session.createTextMessage(text);

send.send(tm);

System.out.println("sendRecvAsync, sent text="

+ tm.getText());

send.close();

System.out.println("End sendRecvAsync");

}

public void stop() throws JMSException

conn.stop(); {

session.close();

conn.close();

}

public static void main(String args[]) throws Exception

{

SendRecvClient client = new SendRecvClient();

client.sendRecvAsync("A text msg");

client.done.acquire();

client.stop();

System.exit(0);

}

}

The client may be run using the following command line:

[nr@toki examples]$ ant -Dchap=chap6 -Dex=1p2p run-example

Buildfile: build.xml

...

run-example1p2p:

[java] [INFO,SendRecvClient] Begin SendRecvClient, now=1083649316059

[java] [INFO,SendRecvClient] Begin sendRecvAsync

[java] [INFO,SendRecvClient] onMessage, recv text=A text msg

[java] [INFO,SendRecvClient] sendRecvAsync, sent text=A text msg

[java] [INFO,SendRecvClient] End sendRecvAsync

[java] [INFO,SendRecvClient] End SendRecvClient

 

BUILD SUCCESSFUL

Total time: 9 seconds

A Pub-Sub JMS client example

package org.jboss.chap6.ex1;

import javax.jms.JMSException;

import javax.jms.Message;

import javax.jms.MessageListener;

import javax.jms.Topic;

import javax.jms.TopicConnection;

import javax.jms.TopicConnectionFactory;

import javax.jms.TopicPublisher;

import javax.jms.TopicSubscriber;

import javax.jms.TopicSession;

import javax.jms.TextMessage;

import javax.naming.InitialContext;

import javax.naming.NamingException;

import EDU.oswego.cs.dl.util.concurrent.CountDown;

/** A complete JMS client example program that sends a

TextMessage to a Topic and asynchronously receives the

message from the same Topic.

@author Scott.Stark@jboss.org

@version $Revision:$

*/

public class TopicSendRecvClient

{

static CountDown done = new CountDown(1);

TopicConnection conn = null;

TopicSession session = null;

Topic topic = null;

public static class ExListener implements MessageListener

{

public void onMessage(Message msg)

{

done.release();

TextMessage tm = (TextMessage) msg;

try

{

System.out.println("onMessage, recv text="

+ tm.getText());

}

catch(Throwable t)

{

t.printStackTrace();

}

}

}

public void setupPubSub()

throws JMSException, NamingException

{

InitialContext iniCtx = new InitialContext();

Object tmp = iniCtx.lookup("ConnectionFactory");

TopicConnectionFactory tcf = (TopicConnectionFactory) tmp;

conn = tcf.createTopicConnection();

topic = (Topic) iniCtx.lookup("topic/testTopic");

session = conn.createTopicSession(false,

TopicSession.AUTO_ACKNOWLEDGE);

conn.start();

}

public void sendRecvAsync(String text)

throws JMSException, NamingException

{

System.out.println("Begin sendRecvAsync");

// Setup the PubSub connection, session

setupPubSub();

// Set the async listener

TopicSubscriber recv = session.createSubscriber(topic);

recv.setMessageListener(new ExListener());

// Send a text msg

TopicPublisher send = session.createPublisher(topic);

TextMessage tm = session.createTextMessage(text);

send.publish(tm);

System.out.println("sendRecvAsync, sent text="

+ tm.getText());

send.close();

System.out.println("End sendRecvAsync");

}

public void stop() throws JMSException

{

conn.stop();

session.close();

conn.close();

}

public static void main(String args[]) throws Exception

{

System.out.println("Begin TopicSendRecvClient, now="+System.currentTimeMillis());

TopicSendRecvClient client = new TopicSendRecvClient();

client.sendRecvAsync("A text msg, now="+System.currentTimeMillis());

client.done.acquire();

client.stop();

System.out.println("End TopicSendRecvClient");

System.exit(0);

}

}

The client may be run using the following command line:

[nr@toki examples]$ ant -Dchap=chap6 -Dex=1ps run-example

Buildfile: build.xml

...

run-example1ps:

[java] Begin TopicSendRecvClient, now=1083649449640

[java] Begin sendRecvAsync

[java] onMessage, recv text=A text msg, now=1083649449642

[java] sendRecvAsync, sent text=A text msg, now=1083649449642

[java] End sendRecvAsync

[java] End TopicSendRecvClient

 

BUILD SUCCESSFUL

Total time: 3 seconds

Now let's break the publisher and subscribers into separate programs to demonstrate that subscribers only receive messages while they are listening to a topic. See A JMS publisher client. shows a variation of the previous Pub-Sub client that only publishes messages to the "topic/testTopic" topic. The subscriber only client is shown in See A JMS subscriber client..

A JMS publisher client

package org.jboss.chap6.ex1;

import javax.jms.JMSException;

import javax.jms.Message;

import javax.jms.MessageListener;

import javax.jms.Topic;

import javax.jms.TopicConnection;

import javax.jms.TopicConnectionFactory;

import javax.jms.TopicPublisher;

import javax.jms.TopicSubscriber;

import javax.jms.TopicSession;

import javax.jms.TextMessage;

import javax.naming.InitialContext;

import javax.naming.NamingException;

/** A JMS client example program that sends a TextMessage to a Topic

@author Scott.Stark@jboss.org

@version $Revision:$

*/

public class TopicSendClient

{

TopicConnection conn = null;

TopicSession session = null;

Topic topic = null;

public void setupPubSub()

throws JMSException, NamingException

{

InitialContext iniCtx = new InitialContext();

Object tmp = iniCtx.lookup("ConnectionFactory");

TopicConnectionFactory tcf = (TopicConnectionFactory) tmp;

conn = tcf.createTopicConnection();

topic = (Topic) iniCtx.lookup("topic/testTopic");

session = conn.createTopicSession(false,

TopicSession.AUTO_ACKNOWLEDGE);

conn.start();

}

public void sendAsync(String text)

throws JMSException, NamingException

{

System.out.println("Begin sendAsync");

// Setup the pub/sub connection, session

setupPubSub();

// Send a text msg

TopicPublisher send = session.createPublisher(topic);

TextMessage tm = session.createTextMessage(text);

send.publish(tm);

System.out.println("sendAsync, sent text="

+ tm.getText());

send.close();

System.out.println("End sendAsync");

}

public void stop() throws JMSException

{

conn.stop();

session.close();

conn.close();

}

public static void main(String args[]) throws Exception

{

System.out.println("Begin TopicSendClient, now="+System.currentTimeMillis());

TopicSendClient client = new TopicSendClient();

client.sendAsync("A text msg, now="+System.currentTimeMillis());

client.stop();

System.out.println("End TopicSendClient");

System.exit(0);

}

}

A JMS subscriber client

package org.jboss.chap6.ex1;

import javax.jms.JMSException;

import javax.jms.Message;

import javax.jms.MessageListener;

import javax.jms.Topic;

import javax.jms.TopicConnection;

import javax.jms.TopicConnectionFactory;

import javax.jms.TopicPublisher;

import javax.jms.TopicSubscriber;

import javax.jms.TopicSession;

import javax.jms.TextMessage;

import javax.naming.InitialContext;

import javax.naming.NamingException;

/** A JMS client example program that synchronously receives a message a Topic

@author Scott.Stark@jboss.org

@version $Revision:$

*/

public class TopicRecvClient

{

TopicConnection conn = null;

TopicSession session = null;

Topic topic = null;

public void setupPubSub()

throws JMSException, NamingException

{

InitialContext iniCtx = new InitialContext();

Object tmp = iniCtx.lookup("ConnectionFactory");

TopicConnectionFactory tcf = (TopicConnectionFactory) tmp;

conn = tcf.createTopicConnection();

topic = (Topic) iniCtx.lookup("topic/testTopic");

session = conn.createTopicSession(false,

TopicSession.AUTO_ACKNOWLEDGE);

conn.start();

}

public void recvSync()

throws JMSException, NamingException

{

System.out.println("Begin recvSync");

// Setup the pub/sub connection, session

setupPubSub();

// Wait upto 5 seconds for the message

TopicSubscriber recv = session.createSubscriber(topic);

Message msg = recv.receive(5000);

if( msg == null )

System.out.println("Timed out waiting for msg");

else

System.out.println("TopicSubscriber.recv, msgt="+msg);

}

public void stop() throws JMSException

{

conn.stop();

session.close();

conn.close();

}

public static void main(String args[]) throws Exception

{

System.out.println("Begin TopicRecvClient, now="+System.currentTimeMillis());

TopicRecvClient client = new TopicRecvClient();

client.recvSync();

client.stop();

System.out.println("End TopicRecvClient");

System.exit(0);

}

}

Run the TopicSendClient followed by the TopicRecvClient as follows:

[nr@toki examples]$ ant -Dchap=chap6 -Dex=1ps2 run-example

Buildfile: build.xml

...

run-example1ps2:

[java] Begin TopicSendClient, now=1083649621287

[java] Begin sendAsync

[java] sendAsync, sent text=A text msg, now=1083649621289

[java] End sendAsync

[java] End TopicSendClient

[java] Begin TopicRecvClient, now=1083649625592

[java] Begin recvSync

[java] Timed out waiting for msg

[java] End TopicRecvClient

 

BUILD SUCCESSFUL

 

Total time: 10 seconds

The output shows that the topic subscriber client (TopicRecvClient) fails to receive the message sent by the publisher due to a timeout.

A durable topic JMS client example

package org.jboss.chap6.ex1;

import javax.jms.JMSException;

import javax.jms.Message;

import javax.jms.MessageListener;

import javax.jms.Topic;

import javax.jms.TopicConnection;

import javax.jms.TopicConnectionFactory;

import javax.jms.TopicPublisher;

import javax.jms.TopicSubscriber;

import javax.jms.TopicSession;

import javax.jms.TextMessage;

import javax.naming.InitialContext;

import javax.naming.NamingException;

/** A JMS client example program that synchronously receives a message a Topic

@author Scott.Stark@jboss.org

@version $Revision:$

*/

public class DurableTopicRecvClient

{

TopicConnection conn = null;

TopicSession session = null;

Topic topic = null;

public void setupPubSub()

throws JMSException, NamingException

{

InitialContext iniCtx = new InitialContext();

Object tmp = iniCtx.lookup("ConnectionFactory");

TopicConnectionFactory tcf = (TopicConnectionFactory) tmp;

conn = tcf.createTopicConnection("john", "needle");

topic = (Topic) iniCtx.lookup("topic/testTopic");

session = conn.createTopicSession(false,

TopicSession.AUTO_ACKNOWLEDGE);

conn.start();

}

public void recvSync()

throws JMSException, NamingException

{

System.out.println("Begin recvSync");

// Setup the pub/sub connection, session

setupPubSub();

// Wait upto 5 seconds for the message

TopicSubscriber recv = session.createDurableSubscriber(topic, "chap6-ex1dtps");

Message msg = recv.receive(5000);

if( msg == null )

System.out.println("Timed out waiting for msg");

else

System.out.println("DurableTopicRecvClient.recv, msgt="+msg);

}

public void stop() throws JMSException

{

conn.stop();

session.close();

conn.close();

}

public static void main(String args[]) throws Exception

{

System.out.println("Begin DurableTopicRecvClient, now="+System.currentTimeMillis());

DurableTopicRecvClient client = new DurableTopicRecvClient();

client.recvSync();

client.stop();

System.out.println("End DurableTopicRecvClient");

System.exit(0);

}

}

Now run the previous topic publisher with the durable topic subscriber as follows:

[nr@toki examples]$ ant -Dchap=chap6 -Dex=1psdt run-example

Buildfile: build.xml

...

run-example1psdt:

[java] Begin DurableTopicSetup

[java] End DurableTopicSetup

[java] Begin TopicSendClient, now=1083649712652

[java] Begin sendAsync

[java] sendAsync, sent text=A text msg, now=1083649712655

[java] End sendAsync

[java] End TopicSendClient

[java] Begin DurableTopicRecvClient, now=1083649716858

[java] Begin recvSync

[java] DurableTopicRecvClient.recv, msgt=org.jboss.mq.SpyTextMessage {

[java] Header {

[java] jmsDestination : TOPIC.testTopic.DurableSubscriberExample.chap6-ex1dtps

[java] jmsDeliveryMode : 2

[java] jmsExpiration : 0

[java] jmsPriority : 4

[java] jmsMessageID : ID:5-10836497160641

[java] jmsTimeStamp : 1083649716064

[java] jmsCorrelationID: null

[java] jmsReplyTo : null

[java] jmsType : null

[java] jmsRedelivered : false

[java] jmsProperties : {}

[java] jmsPropertiesReadWrite:false

[java] msgReadOnly : true

[java] producerClientId: ID:5

[java] }

[java] Body {

[java] text :A text msg, now=1083649712655

[java] }

[java] }

[java] End DurableTopicRecvClient

 

BUILD SUCCESSFUL

Total time: 6 seconds

Items of note for the durable topic example include:

• The TopicConnectionFactory creation in the durable topic client used a username and password, and the TopicSubscriber creation was done using the createDurableSubscriber(Topic, String) method. This is a requirement of durable topic subscribers. The messaging server needs to know what client is requesting the durable topic and what the name of the durable topic subscription is. We will discuss the details of durable topic setup in the configuration section.
• An org.jboss.chap6.DurableTopicSetup client was run prior to the TopicSendClient . The reason for this is a durable topic subscriber must have registered a subscription at some point in the past in order for the messaging server to save messages. JBoss supports dynamic durable topic subscribers and the DurableTopicSetup client simply creates a durable subscription receiver and then exits. This leaves an active durable topic subscriber on the "topic/testTopic" and the messaging server knows that any messages posted to this topic must be saved for latter delivery.
• The TopicSendClient does not change for the durable topic. The notion of a durable topic is a subscriber only notion.
• The DurableTopicRecvClient sees the message published to the "topic/testTopic" even though it was not listening to the topic at the time the message was published.

A TextMessage processing MDB

package org.jboss.chap6.ex2;

import javax.ejb.MessageDrivenBean;

import javax.ejb.MessageDrivenContext;

import javax.ejb.EJBException;

import javax.jms.JMSException;

import javax.jms.Message;

import javax.jms.MessageListener;

import javax.jms.Queue;

import javax.jms.QueueConnection;

import javax.jms.QueueConnectionFactory;

import javax.jms.QueueSender;

import javax.jms.QueueSession;

import javax.jms.TextMessage;

import javax.naming.InitialContext;

import javax.naming.NamingException;

/** An MDB that transforms the TextMessages it receives and send the transformed

messages to the Queue found in the incoming message JMSReplyTo header.

@author Scott.Stark@jboss.org

@version $Revision:$

*/

public class TextMDB implements MessageDrivenBean, MessageListener

{

private MessageDrivenContext ctx = null;

private QueueConnection conn;

private QueueSession session;

public TextMDB()

{

System.out.println("TextMDB.ctor, this="+hashCode());

}

public void setMessageDrivenContext(MessageDrivenContext ctx)

{

this.ctx = ctx;

System.out.println("TextMDB.setMessageDrivenContext, this="+hashCode());

}

public void ejbCreate()

{

System.out.println("TextMDB.ejbCreate, this="+hashCode());

try

{

setupPTP();

}

catch(Exception e)

{

throw new EJBException("Failed to init TextMDB", e);

}

}

public void ejbRemove()

{

System.out.println("TextMDB.ejbRemove, this="+hashCode());

ctx = null;

try

{

if( session != null )

session.close();

if( conn != null )

conn.close();

}

catch(JMSException e)

{

e.printStackTrace();

}

}

public void onMessage(Message msg)

{

System.out.println("TextMDB.onMessage, this="+hashCode());

try

{

TextMessage tm = (TextMessage) msg;

String text = tm.getText() + "processed by: "+hashCode();

Queue dest = (Queue) msg.getJMSReplyTo();

sendReply(text, dest);

}

catch(Throwable t)

{

t.printStackTrace();

}

}

private void setupPTP()

throws JMSException, NamingException

{

InitialContext iniCtx = new InitialContext();

Object tmp = iniCtx.lookup("java:comp/env/jms/QCF");

QueueConnectionFactory qcf = (QueueConnectionFactory) tmp;

conn = qcf.createQueueConnection();

session = conn.createQueueSession(false,

QueueSession.AUTO_ACKNOWLEDGE);

conn.start();

}

private void sendReply(String text, Queue dest)

throws JMSException

{

System.out.println("TextMDB.sendReply, this="+hashCode()

+", dest="+dest);

QueueSender sender = session.createSender(dest);

TextMessage tm = session.createTextMessage(text);

sender.send(tm);

sender.close();

}

}

The MDB ejb-jar.xml and jboss.xml deployment descriptors are shown in See The MDB ejb-jar.xml and jboss.xml descriptors..

The MDB ejb-jar.xml and jboss.xml descriptors

// The ejb-jar.xml descriptor

<?xml version="1.0"?>

<!DOCTYPE ejb-jar

PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"

"http://java.sun.com/dtd/ejb-jar_2_0.dtd"

>

<ejb-jar>

<enterprise-beans>

<message-driven>

<ejb-name>TextMDB</ejb-name>

<ejb-class>org.jboss.chap6.ex2.TextMDB</ejb-class>

<transaction-type>Container</transaction-type>

<acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode>

<message-driven-destination>

<destination-type>javax.jms.Queue</destination-type>

</message-driven-destination>

<res-ref-name>jms/QCF</res-ref-name> <resource-ref>

<res-type>javax.jms.QueueConnectionFactory</res-type>

<res-auth>Container</res-auth>

</resource-ref>

</message-driven>

</enterprise-beans>

</ejb-jar>

// The jboss.xml descriptor

<?xml version="1.0"?>

<jboss>

<enterprise-beans>

<message-driven>

<ejb-name>TextMDB</ejb-name>

<destination-jndi-name>queue/B</destination-jndi-name>

<resource-ref>

<res-ref-name>jms/QCF</res-ref-name>

<jndi-name>ConnectionFactory</jndi-name>

</resource-ref>

</message-driven>

</enterprise-beans>

</jboss>

See A JMS client that interacts with the TextMDB. shows a variation of the P2P client that sends several messages to the "queue/B" destination and asynchronously receives the messages as modified by TextMDB from Queue A.

A JMS client that interacts with the TextMDB

package org.jboss.chap6.ex2;

import javax.jms.JMSException;

import javax.jms.Message;

import javax.jms.MessageListener;

import javax.jms.Queue;

import javax.jms.QueueConnection;

import javax.jms.QueueConnectionFactory;

import javax.jms.QueueReceiver;

import javax.jms.QueueSender;

import javax.jms.QueueSession;

import javax.jms.TextMessage;

import javax.naming.InitialContext;

import javax.naming.NamingException;

import EDU.oswego.cs.dl.util.concurrent.CountDown;

/** A complete JMS client example program that sends N

TextMessages to a Queue B and asynchronously receives the

messages as modified by TextMDB from Queue A.

@author Scott.Stark@jboss.org

@version $Revision:$

*/

public class SendRecvClient

{

static final int N = 10;

static CountDown done = new CountDown(N);

QueueConnection conn;

QueueSession session;

Queue queA;

Queue queB;

public static class ExListener implements MessageListener

{

public void onMessage(Message msg)

{

done.release();

TextMessage tm = (TextMessage) msg;

try

{

System.out.println("onMessage, recv text="+tm.getText());

}

catch(Throwable t)

{

t.printStackTrace();

}

}

}

public void setupPTP()

throws JMSException, NamingException

{

InitialContext iniCtx = new InitialContext();

Object tmp = iniCtx.lookup("ConnectionFactory");

QueueConnectionFactory qcf = (QueueConnectionFactory) tmp;

conn = qcf.createQueueConnection();

queA = (Queue) iniCtx.lookup("queue/A");

queB = (Queue) iniCtx.lookup("queue/B");

session = conn.createQueueSession(false,

QueueSession.AUTO_ACKNOWLEDGE);

conn.start();

}

public void sendRecvAsync(String textBase)

throws JMSException, NamingException, InterruptedException

{

System.out.println("Begin sendRecvAsync");

// Setup the PTP connection, session

setupPTP();

// Set the async listener for queA

QueueReceiver recv = session.createReceiver(queA);

recv.setMessageListener(new ExListener());

// Send a few text msgs to queB

QueueSender send = session.createSender(queB);

for(int m = 0; m < 10; m ++)

{

TextMessage tm = session.createTextMessage(textBase+"#"+m);

tm.setJMSReplyTo(queA);

send.send(tm);

System.out.println("sendRecvAsync, sent text="+tm.getText());

}

System.out.println("End sendRecvAsync");

}

public void stop() throws JMSException

{

conn.stop();

session.close();

conn.close();

}

public static void main(String args[]) throws Exception

{

System.out.println("Begin SendRecvClient,now="+System.currentTimeMillis());

SendRecvClient client = new SendRecvClient();

client.sendRecvAsync("A text msg");

client.done.acquire();

client.stop();

System.exit(0);

System.out.println("End SendRecvClient");

}

}

Run the client as follows:

[nr@toki examples]$ ant -Dchap=chap6 -Dex=2 run-example

Buildfile: build.xml

...

run-example2:

[copy] Copying 1 file to G:\JBoss\jboss-3.2.1\server\default\deploy

[echo] Waiting 5 seconds for deploy...

[java] Begin SendRecvClient, now=1056767530834

[java] Begin sendRecvAsync

[java] sendRecvAsync, sent text=A text msg#0

[java] sendRecvAsync, sent text=A text msg#1

[java] sendRecvAsync, sent text=A text msg#2

[java] sendRecvAsync, sent text=A text msg#3

[java] sendRecvAsync, sent text=A text msg#4

[java] sendRecvAsync, sent text=A text msg#5

[java] sendRecvAsync, sent text=A text msg#6

[java] sendRecvAsync, sent text=A text msg#7

[java] sendRecvAsync, sent text=A text msg#8

[java] sendRecvAsync, sent text=A text msg#9

[java] End sendRecvAsync

[java] onMessage, recv text=A text msg#2processed by: 23715584

[java] onMessage, recv text=A text msg#6processed by: 322649

[java] onMessage, recv text=A text msg#1processed by: 27534070

[java] onMessage, recv text=A text msg#3processed by: 23966866

[java] onMessage, recv text=A text msg#0processed by: 28532430

[java] onMessage, recv text=A text msg#4processed by: 1734943

[java] onMessage, recv text=A text msg#9processed by: 24814248

[java] onMessage, recv text=A text msg#7processed by: 21845470

[java] onMessage, recv text=A text msg#8processed by: 17243666

[java] onMessage, recv text=A text msg#5processed by: 403211

 

BUILD SUCCESSFUL

Total time: 9 seconds

The corresponding JBoss server console output is:

19:32:07,209 INFO [MainDeployer] Starting deployment of package: file:/G:/JBoss/jboss-3.2.1/server/default/deploy/chap6

-ex2.jar

19:32:07,760 INFO [EjbModule] Creating

19:32:07,770 INFO [EjbModule] Deploying TextMDB

19:32:07,810 INFO [MessageDrivenContainer] Creating

19:32:07,810 INFO [MessageDrivenInstancePool] Creating

19:32:07,810 INFO [MessageDrivenInstancePool] Created

19:32:07,810 INFO [JMSContainerInvoker] Creating

19:32:07,820 INFO [JMSContainerInvoker] Created

19:32:07,820 INFO [MessageDrivenContainer] Created

19:32:07,820 INFO [EjbModule] Created

19:32:07,820 INFO [EjbModule] Starting

19:32:07,820 INFO [MessageDrivenContainer] Starting

19:32:07,830 INFO [JMSContainerInvoker] Starting

19:32:07,830 INFO [DLQHandler] Creating

19:32:07,890 INFO [DLQHandler] Created

19:32:08,191 WARN [SecurityManager] No SecurityMetadadata was available for B adding default security conf

19:32:08,201 INFO [DLQHandler] Starting

19:32:08,201 INFO [DLQHandler] Started

19:32:08,201 INFO [JMSContainerInvoker] Started

19:32:08,201 INFO [MessageDrivenInstancePool] Starting

19:32:08,211 INFO [MessageDrivenInstancePool] Started

19:32:08,211 INFO [MessageDrivenContainer] Started

19:32:08,211 INFO [EjbModule] Started

19:32:08,211 INFO [EJBDeployer] Deployed: file:/G:/JBoss/jboss-3.2.1/server/default/deploy/chap6-ex2.jar

19:32:08,241 INFO [MainDeployer] Deployed package: file:/G:/JBoss/jboss-3.2.1/server/default/deploy/chap6-ex2.jar

19:32:12,136 WARN [SecurityManager] No SecurityMetadadata was available for A adding default security conf

19:32:12,206 INFO [TextMDB] TextMDB.ctor, this=28532430

19:32:12,216 INFO [TextMDB] TextMDB.ctor, this=27534070

19:32:12,307 INFO [TextMDB] TextMDB.ctor, this=23966866

19:32:12,307 INFO [TextMDB] TextMDB.ctor, this=23715584

19:32:12,307 INFO [TextMDB] TextMDB.setMessageDrivenContext, this=27534070

19:32:12,307 INFO [TextMDB] TextMDB.setMessageDrivenContext, this=28532430

19:32:12,347 INFO [TextMDB] TextMDB.ejbCreate, this=27534070

19:32:12,347 INFO [TextMDB] TextMDB.ejbCreate, this=28532430

19:32:12,347 INFO [TextMDB] TextMDB.setMessageDrivenContext, this=23966866

19:32:12,357 INFO [TextMDB] TextMDB.ejbCreate, this=23966866

19:32:12,377 INFO [TextMDB] TextMDB.setMessageDrivenContext, this=23715584

19:32:12,377 INFO [TextMDB] TextMDB.ejbCreate, this=23715584

19:32:12,387 INFO [TextMDB] TextMDB.ctor, this=1734943

19:32:12,387 INFO [TextMDB] TextMDB.setMessageDrivenContext, this=1734943

19:32:12,387 INFO [TextMDB] TextMDB.ejbCreate, this=1734943

19:32:12,387 INFO [TextMDB] TextMDB.ctor, this=403211

19:32:12,387 INFO [TextMDB] TextMDB.setMessageDrivenContext, this=403211

19:32:12,397 INFO [TextMDB] TextMDB.ejbCreate, this=403211

19:32:12,397 INFO [TextMDB] TextMDB.ctor, this=322649

19:32:12,397 INFO [TextMDB] TextMDB.setMessageDrivenContext, this=322649

19:32:12,397 INFO [TextMDB] TextMDB.ejbCreate, this=322649

19:32:12,437 INFO [TextMDB] TextMDB.ctor, this=21845470

19:32:12,437 INFO [TextMDB] TextMDB.ctor, this=17243666

19:32:12,467 INFO [TextMDB] TextMDB.ctor, this=24814248

19:32:12,467 INFO [TextMDB] TextMDB.setMessageDrivenContext, this=21845470

19:32:12,467 INFO [TextMDB] TextMDB.setMessageDrivenContext, this=24814248

19:32:12,467 INFO [TextMDB] TextMDB.ejbCreate, this=24814248

19:32:12,477 INFO [TextMDB] TextMDB.ejbCreate, this=21845470

19:32:12,487 INFO [TextMDB] TextMDB.setMessageDrivenContext, this=17243666

19:32:12,487 INFO [TextMDB] TextMDB.ejbCreate, this=17243666

19:32:12,537 INFO [TextMDB] TextMDB.onMessage, this=28532430

19:32:12,537 INFO [TextMDB] TextMDB.sendReply, this=28532430, dest=QUEUE.A

19:32:12,537 INFO [TextMDB] TextMDB.onMessage, this=23715584

19:32:12,537 INFO [TextMDB] TextMDB.onMessage, this=23966866

19:32:12,537 INFO [TextMDB] TextMDB.onMessage, this=322649

19:32:12,547 INFO [TextMDB] TextMDB.onMessage, this=27534070

19:32:12,547 INFO [TextMDB] TextMDB.sendReply, this=23715584, dest=QUEUE.A

19:32:12,547 INFO [TextMDB] TextMDB.sendReply, this=23966866, dest=QUEUE.A

19:32:12,547 INFO [TextMDB] TextMDB.sendReply, this=322649, dest=QUEUE.A

19:32:12,567 INFO [TextMDB] TextMDB.sendReply, this=27534070, dest=QUEUE.A

19:32:12,647 INFO [TextMDB] TextMDB.onMessage, this=24814248

19:32:12,647 INFO [TextMDB] TextMDB.sendReply, this=24814248, dest=QUEUE.A

19:32:12,667 INFO [TextMDB] TextMDB.onMessage, this=1734943

19:32:12,677 INFO [TextMDB] TextMDB.sendReply, this=1734943, dest=QUEUE.A

19:32:12,687 INFO [TextMDB] TextMDB.onMessage, this=21845470

19:32:12,687 INFO [TextMDB] TextMDB.sendReply, this=21845470, dest=QUEUE.A

19:32:12,687 INFO [TextMDB] TextMDB.onMessage, this=17243666

19:32:12,697 INFO [TextMDB] TextMDB.onMessage, this=403211

19:32:12,727 INFO [TextMDB] TextMDB.sendReply, this=17243666, dest=QUEUE.A

19:32:12,727 INFO [TextMDB] TextMDB.sendReply, this=403211, dest=QUEUE.A

Items of note in this example include:

• The JMS client has no explicit knowledge that it is dealing with an MDB. The client simply uses the standard JMS APIs to send messages to a queue and receive messages from another queue.
• The MDB declares whether it will listen to a queue or topic in the ejb-jar.xml descriptor. The name of the queue or topic must be specified using a jboss.xml descriptor. In this example the MDB also sends messages to a JMS queue. MDBs may act as queue senders or topic publishers within their onMessage callback.
• The messages received by the client include a "processed by: NNN" suffix, where NNN is the hashCode value of the MDB instance that processed the message. This shows that many MDBs may actively process messages posted to a destination. Concurrent processing is one of the benefits of MDBs.

RMI IL (deprecated)

The first IL that was developed was based on Java's Remote Method Invocation (RMI). This is a robust IL since it is based on standard RMI technology, but it has a high overhead compared to other ILs and will likely be dropped in future releases.

NOTE: This IL will try to establish a TCP/IP socket from the server to the client. Therefore, clients that sit behind firewalls or have security restrictions prohibiting the use of SeverSockets should not use this IL.

OIL IL (deprecated)

The next IL that was developed was the "Optimized" IL (OIL). The OIL uses a custom TCP/IP protocol and serialization protocol that has very low overhead. This was the recommended socket based protocol until the addition of the UIL2 protocol.

NOTE: This IL will try to establish a TCP/IP socket from the server to the client. Therefore, clients that sit behind firewalls or have security restrictions prohibiting the use of SeverSockets should not use this IL.

UIL IL (deprecated)

The Unified Invocation Layer (UIL) was developed to allow clients that cannot have a connection created from the server back to the client due to firewall or other restrictions. It is almost identical to the OIL protocol except that a multiplexing layer is used to provide the bidirectional communication. The multiplexing layer creates two virtual sockets over one physical socket. This IL is slower than the OIL due to the higher overhead incurred by the multiplexing layer. This invocation layer is now deprecated in favor of UIL2.

UIL2 IL

The Unified version 2 Invocation Layer (UIL2) is a variation of the UIL protocol that also uses a single socket between the client and server. However, unlike all other socket based invocation layers like RMI, UIL and OIL which use a blocking round-trip message at the socket level, the UIL2 protocol uses true asynchronous send and receive messaging at the transport level. This provides for improved throughput and utilization and as such, it is the preferred socket invocation layer.

JVM IL

The Java Virtual Machine (JVM) Invocation Layer was developed to cut out the TCP/IP overhead when the JMS client is running in the same JVM as the server. This IL uses direct method calls for the server to service the client requests. This increases efficiency since no sockets are created and there is no need for the associated worker threads. This is the IL that should be used by Message Driven Beans (MDB) or any other component that runs in the same virtual machine as the server such as servlets, MBeans, or EJBs.

HTTP IL

The HTTP Invocation Layer (HTTPIL) allows for accessing the JBossMQ service over the HTTP or HTTPS protocols. This IL relies on the servlet deployed in the deploy/jms/jbossmq-httpil.sar to handle the http traffic. This IL is useful for access to JMS through a firewall when the only port allowed requires HTTP.

File PM

The File PM is a robust persistence manager that comes with JBossMQ. It creates separate directories for each of the destination created on the server, and stores each persistent message as a separate file in the appropriate directory. It has poor performance characteristics since it is frequently opening and closing files.

Rolling Logged PM

The Rolling Logged PM is also a file based persistence manager that has better performance than the File PM because it stores multiple messages in one file, reducing the overhead of opening/closing multiple files. This is a very fast PM but it is less transactionally reliable than the File PM due to its use of the FileOutputStream.flush() method call. On some operating systems/JVMs the FileOutputStream.flush() method does not guarantee that the data has been written to disk by the time the call returns.

JDBC2 PM

The JDBC2 PM is the second version of the original JDBC PM in JBossMQ 2.4.x. It has been substantially simplified and improved. This PM allows you to store persistent messages to a relational database using JDBC. The performance of this PM is directly related to the performance that can be obtained from the database. This PM has a very low memory overhead compared to the other persistence managers. Furthermore it is also highly integrated with the MessageCache to provide efficient persistence on a system that has a very active MessageCache.

Queues

Clients that are in the Point-to-Point paradigm typically use Queues. They expect that message sent to a Queue will be receive by only one other client once and only once. If multiple clients are receiving messages from a single queue, the messages will be load balanced across the receivers. Queue objects, by default, will be stored under the JNDI "queue/" sub context.

Topics

Topics are used in the Publish-Subscribe paradigm. When a client publishes a message to a topic, he expects that a copy of the message will be delivered to each client that has subscribed to the topic. Topic messages are delivered in the same manner a television show is delivered. Unless you have the TV on and are watching the show, you will miss it. Similarly, if the client is not up, running and receiving messages from the topics, it will miss messages published to the topic. To get around this problem of missing messages, clients can start a durable subscription. This is like having a VCR record a show you cannot watch at its scheduled time so that you can see what you missed when you turn your TV back on.

ClientSocketFactory: The javax.net.SocketFactory implementation class name to use on the client. If not specified the default factory will be obtained from javax.net.SocketFactory.getDefault() .

• SecurityDomain: Specify the security domain name to use with JBoss SSL aware socket factories. This is the JNDI name of the security manager implementation as described for the security-domain element of the jboss.xml and jboss-web.xml descriptors in Enabling Declarative Security in JBoss Revisited.

Configuring ILs for SSL

The UIL2 and OIL services support the use of SSL through custom socket factories that integrate JSSE using the security domain associated with the IL service. An example UIL2 service descriptor fragment that illustrates the use of the custom JBoss SSL socket factories is shown in See An example UIL2 config fragment for using SSL..

FIGURE 6-1. The jbossmq-state.xml content model

The default login-config.xml configuration for JBossMQ

<application-policy name = "jbossmq">

<authentication>

<login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"

flag = "required">

<module-option name="unauthenticatedIdentity">guest

</module-option>

<module-option name="sm.objectname">

jboss.mq:service=StateManager

</module-option>

</login-module>

</authentication>

</application-policy>

This integrates the DynamicStateManager jbossmq-state.xml security store into the JAAS based framework through the org.jboss.mq.sm.file.DynamicLoginModule. The configuration also maps any unauthenticated JBossMQ client to the "guest" role.

The configurable attributes of the SecurityManager are as follows:

• NextInterceptor: The JMX ObjectName of the next request interceptor. This attribute is used by all the interceptors to create the interceptor stack. The last interceptor in the chain should be the DestinationManager . This attribute should be setup via a <depends optional-attribute-name="NextInterceptor"> tag.
• DefaultSecurityConfig: This element specifies the default security configuration settings for destinations. This applies to temporary queues and topics as well as queues and topics that do not specifically specify a security configuration. The content model of this element is shown in See The destination security config content model..

FIGURE 6-2. The destination security config content model

• role: Each role that is allowed access to a destination is represented by a role element.
• role@name: The name attribute defines the name of the role.
• role@create: The create attribute is a true/false enum that indicates whether the role has the ability to create durable subscriptions on the topic.
• role@read: The read attribute is a true/false enum that indicates whether the role can receive messages from the destination.
• role@write: The write attribute is a true/false enum that indicates whether the role can send messages to the destination.
• SecurityDomain: Specify the security domain name to use for authentication and role based authorization. This is the JNDI name of the security manager implementation as described for the security-domain element of the jboss.xml and jboss-web.xml descriptors in Enabling Declarative Security in JBoss Revisited. Note however, that this attribute value cannot have the standard "java:/jaas" prefix and that this prefix is currently an assumed and hardcoded value.

You may be uncomfortable having to maintain your authentication and authorization information in an XML file. You can use any standard security store such as a database or LDAP server by simply updating the JAAS login-config.xml to provide the same username to password and user to role mappings as the DynamicStateManager . For example, to use a JDBC database, the following sample database tables and login-config.xml entry would work.

An example "JMSPasswords" username to password table

username	password
jduke	theduke

An example "JMSRoles" username to acl roles tabls

username	role
jduke	create
jduke	read
jduke	write

An alternate login-config.xml configuration for JBossMQ

<application-policy name = "jbossmq">

<authentication>

<login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule"

flag = "required">

<module-option name="unauthenticatedIdentity">guest

</module-option>

<module-option name="dsJndiName">java:/DefaultDS

</module-option>

<module-option name="principalsQuery">

select password from JMSPasswords where username = ?

</module-option>

<module-option name="rolesQuery">

select role, "Roles" from JMSRoles where username= ?

</module-option>

</login-module>

</authentication>

</application-policy>

For a complete description of the DatabaseServerLoginModule See org.jboss.security.auth.spi.DatabaseServerLoginModule.

Default JDBC2 PeristenceManager SqlProperties

<attribute name="SqlProperties">

BLOB_TYPE=OBJECT_BLOB

INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)

INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)

SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS

SELECT_MAX_TX = SELECT MAX(TXID) FROM JMS_MESSAGES

SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE DESTINATION=?

SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?

MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?

UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?

UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?

UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?

DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE TXID IN (SELECT TXID FROM JMS_TRANSACTIONS) AND TXOP=?

DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?

DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?

DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?

CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \

DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \

MESSAGEBLOB OBJECT, PRIMARY KEY (MESSAGEID, DESTINATION) )

CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER )

</attribute>

A sample JDBC2 PeristenceManager SqlProperties for Oracle

<attribute name="SqlProperties">

BLOB_TYPE=BINARYSTREAM_BLOB

INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)

INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)

SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS

SELECT_MAX_TX = SELECT MAX(TXID) FROM JMS_MESSAGES

SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE DESTINATION=?

SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?

MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?

UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?

UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?

UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?

DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE TXID IN (SELECT TXID FROM JMS_TRANSACTIONS) AND TXOP=?

DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?

DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?

DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?

CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \

DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \

MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION) )

CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER )

</attribute>

org.jboss.mq.server.jmx.Queue

The org.jboss.mq.server.jmx.Queue is used to define a Queue Destination on the JBossMQ server. The "name" attribute of the JMX object name of this MBean is used to determine the destination name. For example, if the JMX MBean begins with:

<mbean code="org.jboss.mq.server.jmx.Queue"

name="jboss.mq.destination:service=Queue,name=testQueue">

Then, the JMX object name is "jboss.mq.destination:service=Queue,name=testQueue" and the name of the queue is "testQueue". The configurable attributes are as follows:

• DestinationManager: The JMX ObjectName of the destination manager service for the server. This attribute should be set via a <depends optional-attribute-name="DestinationManager"> XML tag.
• SecurityManager: The JMX ObjectName of the security manager service that is being used to validate client requests. This attribute should be set via a <depends optional-attribute-name="SecurityManager"> XML tag.
• SecurityConf: This element specifies a XML fragment which describes the access control list to be used by the SecurityManager to authorize client operations against the destination. The content model is the same as that shown in Figure 6-2 for the SecurityManager SecurityConf attribute.
• JNDIName: The location in JNDI to which the queue object will be bound. If this is not set it will default to "queue/queue-name".
• MaxDepth: The MaxDepth is an upper limit to the backlog of messages that can exist for a destination, and if exceeded, attempts to add new messages will result in a org.jboss.mq.DestinationFullException . The MaxDepth can still be exceeded in a number of situations, e.g. when a message is knacked back into the queue. Also transactions performing read committed processing, look at the current size of queue, ignoring any messages that may be added as a result of the current transaction or other transactions. This is because we don't want the transaction to fail during the commit phase when the message is physically added to the queue.
• MessageCounterHistoryDayLimit: Sets the destination message counter history day limit with a value < 0 indicating unlimited history, a 0 value disabling history, and a value > 0 giving the history days count.

Additional read-only attributes that provide statistics information include:

• MessageCounter: An array of org.jboss.mq.server.MessageCounter instances that provide statistics for this destination.
• QueueDepth: The current backlog of waiting messages.
• ReceiversCount: The number of receivers currently associated with the queue.
• ScheduledMessageCount: The number of messages waiting in the queue for their scheduled delivery time to arrive.
• String listMessageCounter(): This operation generates an html table that contains
• Type: Either Queue or Topic indicating the destination type.
• Name: The name of the destination.
• Subscription: The subscription ID for a topic.
• Durable: A boolean indicating if the topic subscription is durable.
• Count: The number of message delivered to the destination.
• CountDelta: The change in message count since the previous access of count.
• Depth: The number of messages in the destination.
• DepthDelta: The change in the number of messages in the destination since the previous access of depth.
• Last Add: The date/time string in DateFormat.SHORT/DateFormat.MEDIUM format of the last time a message was added to the destination.
• void resetMessageCounter(): This zeros all destination counts and last added times.
• String listMessageCounterHistory(): This operation display an html table showing the hourly message counts per hour for each day of history.
• void resetMessageCounterHistory(): This operation resets the day history message counts.

org.jboss.mq.server.jmx.Topic

The org.jboss.mq.server.jmx.Topic is used to define a Topic Destination on the JBossMQ server. The "name" attribute of the JMX object name of this MBean is used to determine the destination name. For example, if the JMX MBean begins with:

<mbean code="org.jboss.mq.server.jmx.Topic"

name="jboss.mq.destination:service=Topic,name=testTopic">

Then, the JMX object name is "jboss.mq.destination:service=Topic,name=testTopic" and the name of the topic is "testTopic". The configurable attributes are as follows:

• DestinationManager: The JMX object name of the Destination Manager configured for the server. This attribute should be setup via a <depends optional-attribute-name="DestinationManager"> XML tag.
• SecurityManager: The JMX object name of the Security Manager that is being used to validate client requests. This attribute should be setup via a <depends optional-attribute-name="SecurityManager"> XML tag.
• SecurityConf: This element specifies a XML fragment which describes the access control list to be used by the SecurityManager to authorize client operations against the destination. The content model is the same as that shown in Figure 6-2 for the SecurityManager SecurityConf attribute.
• JNDIName: The location in JNDI to which the queue object will be bound. If this is not set it will default to "topic/topic-name".
• MaxDepth: The MaxDepth is an upper limit to the backlog of messages that can exist for a destination, and if exceeded, attempts to add new messages will result in a org.jboss.mq.DestinationFullException . The MaxDepth can still be exceeded in a number of situations, e.g. when a message is knacked back into the queue. Also transactions performing read committed processing, look at the current size of queue, ignoring any messages that may be added as a result of the current transaction or other transactions. This is because we don't want the transaction to fail during the commit phase when the message is physically added to the topic.
• MessageCounterHistoryDayLimit: Sets the destination message counter history day limit with a value < 0 indicating unlimited history, a 0 value disabling history, and a value > 0 giving the history days count.

Additional read-only attributes that provide statistics information include:

• AllMessageCount: The message count across all queue types associated with the topic.
• AllSubscriptionsCount: The count of durable and non-durable subscriptions.
• DurableMessageCount: The count of messages in durable subscription queues.
• DurableSubscriptionsCount: The count of durable subscribers.
• MessageCounter: An array of org.jboss.mq.server.MessageCounter instances that provide statistics for this destination.
• NonDurableMessageCount: The count on messages in non-durable subscription queues.
• NonDurableSubscriptionsCount: The count of non-durable subscribers.
• String listMessageCounter(): This operation generates an html table that contains
• Type: Either Queue or Topic indicating the destination type.
• Name: The name of the destination.
• Subscription: The subscription ID for a topic.
• Durable: A boolean indicating if the topic subscription is durable.
• Count: The number of message delivered to the destination.
• CountDelta: The change in message count since the previous access of count.
• Depth: The number of messages in the destination.
• DepthDelta: The change in the number of messages in the destination since the previous access of depth.
• Last Add: The date/time string in DateFormat.SHORT/DateFormat.MEDIUM format of the last time a message was added to the destination.
• void resetMessageCounter(): This zeros all destination counts and last added times.
• String listMessageCounterHistory(): This operation display an html table showing the hourly message counts per hour for each day of history.
• void resetMessageCounterHistory(): This operation resets the day history message counts.

Creating Queues At Runtime

Applications that require the dynamic creation of queues at runtime can use the Destination Manager's MBean createQueue method:

void createQueue(String name, String jndiLocation)

This method creates a queue with the given name and binds it in JNDI at the jndiLocation. Queues created via this method exist until the server is restarted. To destroy a previously created Queue, you would issue a:

void destroyQueue(String name)

Creating Topics At Runtime

Applications that require the dynamic creation of topics at runtime can use the Destination Manager's MBean createTopic method:

void createTopic(String name, String jndiLocation)

This method creates a topic with the given name and binds it in JNDI at the jndiLocation. Topics created via this method exist until the server is restarted. To destroy a previously created Topic, you would issue a:

void destroyTopic(String name)

Managing a JBossMQ User IDs at Runtime

The org.jboss.mq.sm.file.DynamicStateManager 's MBean can be used to add and remove user ids and roles at runtime. To add a user id, you would use:

void addUser(String name, String password, String clientID)

This method creates a user id with the given name and password and configures him to have the given clientID. To remove a previously created user id, you would call the following method:

void removeUser(String name)

To manage the roles that the user ids belong to, you would use the following set of methods to create roles, remove roles, add users to roles, and remove users from roles:

void addRole(String name)

void removeRole(String name)

void addUserToRole(String roleName, String user)

void removeUserFromRole(String roleName, String user)

A JMSProviderLoader for accessing a remote JBossMQ server

<mbean code="org.jboss.jms.jndi.JMSProviderLoader"

name="jboss.mq:service=JMSProviderLoader,name=RemoteJBossMQProvider">

<attribute name="ProviderName">RemoteJMSProvider</attribute>

<attribute name="ProviderUrl">jnp://remotehost:1099</attribute>

<attribute name="ProviderAdapterClass">

org.jboss.jms.jndi.JBossMQProvider

</attribute>

<attribute name="QueueFactoryRef">XAConnectionFactory</attribute>

<attribute name="TopicFactoryRef">XAConnectionFactory</attribute>

• </mbean>

The RemoteJMSProvider can be referenced on the mdb invoker config as shown in the jboss.xml fragment given in See A jboss.xml fragment for specifying the MDB JMS provider adaptor. .

A jboss.xml fragment for specifying the MDB JMS provider adaptor

...

<proxy-factory-config>

<JMSProviderAdapterJNDI>RemoteJMSProvider</JMSProviderAdapterJNDI>

<ServerSessionPoolFactoryJNDI>StdJMSPool

</ServerSessionPoolFactoryJNDI>

<MaximumSize>15</MaximumSize>

<MaxMessages>1</MaxMessages>

<MDBConfig>

<ReconnectIntervalSec>10</ReconnectIntervalSec>

<DLQConfig>

<DestinationQueue>queue/DLQ</DestinationQueue>

<MaxTimesRedelivered>10</MaxTimesRedelivered>

<TimeToLive>0</TimeToLive>

</DLQConfig>

</MDBConfig>

</proxy-factory-config>

Incidently, because one can specify multiple <invoker-proxy-binding>s, this allows an MDB to listen to the same queue/topic on multiple servers by configuring multiple bindings with different JMSProviderAdapterJNDI settings.

Alternatively, one can integrate the JMS provider using JCA configuration like that shown in See A jms-ds.xml descriptor for integrating a JMS provider adaptor via JCA.

A jms-ds.xml descriptor for integrating a JMS provider adaptor via JCA

<tx-connection-factory>

<jndi-name>RemoteJmsXA</jndi-name>

<xa-transaction/>

<adapter-display-name>JMS Adapter</adapter-display-name>

<config-property name="JMSProviderAdapterJNDI"

type="java.lang.String">RemoteJMSProvider</config-property>

<config-property name="SessionDefaultType"

type="java.lang.String">javax.jms.Topic</config-property>

 

<security-domain-and-application>JmsXARealm

</security-domain-and-application>

</tx-connection-factory>