Release Notes - HornetQ - Version 2.4.1 Final
+ ++ +
22th January 2014
+ +These are the release notes for HornetQ 2.4.1.Final+ +For full description of the contents please see the +HornetQ project JIRA.
+ +2.4.1.Final is a patch release built on 2.4.0.Final. + +
+ +For more info on what this release has to offer please refer to the quick start guide or the user manual. Enjoy!! diff --git a/docs/design-guide/en/Author_Group.xml b/docs/design-guide/en/Author_Group.xml new file mode 100644 index 0000000000..2d9b1bddd8 --- /dev/null +++ b/docs/design-guide/en/Author_Group.xml @@ -0,0 +1,30 @@ + + + + +%BOOK_ENTITIES; +]> +
0.0.0.0 to accept connection from all the
+ host's network interfaces. It's not valid to specify multiple addresses when
+ specifying the host for a connector; a connector makes a connection to one
+ specific address.ServerLocator with the addIncomingInterceptor(Interceptor) or
+ addOutgoingInterceptor(Interceptor) methods.Creates a thread pool that creates new threads as needed, but will reuse previously + constructed threads when they are available, and uses the provided ThreadFactory to create + new threads when needed.+ Threads from this pool which are idle for more than 60 seconds will time out and be + removed. If old IO connections were serviced from the standard pool the pool would + easily get exhausted if too many connections were made, resulting in the server "hanging" + since it has no remaining threads to do anything else. However, even an unbounded thread + pool can run into trouble if it becomes too large. If you require the server to handle + many concurrent connections you should use NIO, not old IO.
0.0.0.0，
+ 则接收器将从主机上所有的网络接口中接受连接请求。连接器不允许指定多个主机地址，它只能与一个
+ 地址建立连接。ClientSessionFactory
+ 的addInterceptor()方法可以用来添加拦截器。Embedded Example
+This example shows how to setup and run HornetQ embedded with remote clients connecting.
+HornetQ was designed to use POJOs (Plain Old Java Objects), what makes embedding HornetQ as simple as instantiating a few objects.
+ +HornetQ Embedded could be used from very simple use cases with only InVM support to very complex cases with clustering, persistence and fail over.
+ + +Example step-by-step
+To run the example, simply type mvn -Pserver from this directory to start the server and mvn -Pclient to run the client example
In this we don't use any configuration files. (Everything is embedded). We simply instantiate ConfigurationImpl, HornetQServer, start it and operate on JMS regularly
++
-
+
- On EmbeddedServer: Create the Configuration, and set the properties accordingly +
- On EmbeddedServer: Create and start the server +
- As we are not using a JNDI environment we instantiate the objects directly +
- Create a Core Queue +
- Create the session and producer +
- Create and send a Message +
- Create the message consumer and start the connection +
- Receive the message +
- Be sure to close our resources! + +
+ Configuration configuration = new ConfigurationImpl(); + configuration.setEnablePersistence(false); + configuration.setSecurityEnabled(false); ++ +
+ HornetQServer server = HornetQ.newHornetQServer(configuration); + server.start(); ++ +
+ ServerLocator serverLocator = HornetQClient.createServerLocatorWithoutHA(new TransportConfiguration(NettyConnectorFactory.class.getName())); + ClientSessionFactory sf = serverLocator.createSessionFactory(); ++ +
+ ClientSession coreSession = sf.createSession(false, false, false); + final String queueName = "queue.exampleQueue"; + coreSession.createQueue(queueName, queueName, true); + coreSession.close(); ++ +
+ session = sf.createSession(); + + ClientProducer producer = session.createProducer(queueName); ++ +
+ ClientMessage message = session.createMessage(false);
+ message.putStringProperty(propName, "Hello sent at " + new Date());
+ System.out.println("Sending the message.");
+ producer.send(message);
+
+
+ + ClientConsumer messageConsumer = session.createConsumer(queueName); + session.start(); ++ +
+ ClientMessage messageReceived = messageConsumer.receive(1000);
+ System.out.println("Received TextMessage:" + messageReceived.getProperty(propName));
+
+
+
+ if (sf != null)
+ {
+ sf.close();
+ }
+
+ Embedded Example
+ +This example shows how to setup and run HornetQ embedded.
+HornetQ was designed to use POJOs (Plain Old Java Objects), what makes embedding HornetQ as simple as instantiating a few objects.
+In this example, we are using two jars:
+-
+
- hornetq-server.jar +
- netty.jar +
HornetQ Embedded could be used from very simple use cases with only InVM support to very complex cases with clustering, persistence and fail over.
+ +Example step-by-step
+To run the example, simply type mvn -Pexample from this directory
In this we don't use any configuration files. (Everything is embedded). We simply instantiate ConfigurationImpl, HornetQServer, start it and operate on JMS regularly
+ +-
+
- Create the Configuration, and set the properties accordingly +
- Create and start the server +
- As we are not using a JNDI environment we instantiate the objects directly +
- Create a Core Queue +
- Create the session and producer +
- Create and send a Message +
- Create the message consumer and start the connection +
- Receive the message +
- Be sure to close our resources! + +
- Stop the server + +
+ Configuration configuration = new ConfigurationImpl(); + configuration.setEnablePersistence(false); + configuration.setSecurityEnabled(false); + configuration.getAcceptorConfigurations().add(new TransportConfiguration(InVMAcceptorFactory.class.getName())); ++ +
+ HornetQServer server = HornetQ.newHornetQServer(configuration); + server.start(); ++ +
+ ServerLocator serverLocator = HornetQClient.createServerLocatorWithoutHA(new TransportConfiguration(InVMConnectorFactory.class.getName())); + ClientSessionFactory sf = serverLocator.createSessionFactory(); ++ +
+ ClientSession coreSession = sf.createSession(false, false, false); + final String queueName = "queue.exampleQueue"; + coreSession.createQueue(queueName, queueName, true); + coreSession.close(); ++ +
+ session = sf.createSession(); + + ClientProducer producer = session.createProducer(queueName); ++ +
+ ClientMessage message = session.createMessage(false);
+ message.putStringProperty(propName, "Hello sent at " + new Date());
+ System.out.println("Sending the message.");
+ producer.send(message);
+
+
+ + ClientConsumer messageConsumer = session.createConsumer(queueName); + session.start(); ++ +
+ ClientMessage messageReceived = messageConsumer.receive(1000);
+ System.out.println("Received TextMessage:" + messageReceived.getProperty(propName));
+
+
+
+ if (sf != null)
+ {
+ sf.close();
+ }
+
+
+ + server.stop(); ++
Micro Container Example
+ +This examples shows how to setup and run HornetQ through the Micro Container.
+Refer to the user's manual for the list of required Jars, since JBoss Micro Container requires a few jars.
+Example step-by-step
+To run the example, simply type mvn verify from this directory
In this we don't use any configuration files. (Everything is embedded). We simply instantiate ConfigurationImpl, HornetQServer, start it and operate on JMS regularly
+ +-
+
+
- Start the server +
- As we are not using a JNDI environment we instantiate the objects directly +
- Create a Core Queue +
- Create the session and producer +
- Create and send a Message +
- Create the message consumer and start the connection +
- Receive the message +
- Be sure to close our resources! + +
- Stop the server + +
+ hornetq = new HornetQBootstrapServer("./server0/hornetq-beans.xml");
+ hornetq.run();
+
+
+ + ServerLocator serverLocator = HornetQClient.createServerLocatorWithoutHA(new TransportConfiguration(NettyConnectorFactory.class.getName())); + ClientSessionFactory sf = serverLocator.createSessionFactory(); ++ +
+ ClientSession coreSession = sf.createSession(false, false, false); + final String queueName = "queue.exampleQueue"; + coreSession.createQueue(queueName, queueName, true); + coreSession.close(); ++ +
+ session = sf.createSession(); + + ClientProducer producer = session.createProducer(queueName); ++ +
+ ClientMessage message = session.createMessage(false);
+ message.putStringProperty(propName, "Hello sent at " + new Date());
+ System.out.println("Sending the message.");
+ producer.send(message);
+
+
+ + ClientConsumer messageConsumer = session.createConsumer(queueName); + session.start(); ++ +
+ ClientMessage messageReceived = messageConsumer.receive(1000);
+ System.out.println("Received TextMessage:" + messageReceived.getProperty(propName));
+
+
+
+ if (sf != null)
+ {
+ sf.close();
+ }
+
+
+ + hornetq.shutdown(); ++
Twitter Connector Service Example
+ +This example shows you how to configure HornetQ to use the Twitter Connector Service.
+ +HornetQ supports 2 types of Twitter connector, incoming and outgoing. + Incoming connector consumes from twitter and forwards to a configurable address. + Outgoing connector consumes from a configurable address and forwards to twitter. +
+ +In this example, incoming connector and outgoing connector is related to same twitter account. + So if you send a message to an outgoing address, outgoing connector forwards it to twitter, + and then incoming connector consumes it and forwards to incoming address.
+ +Example step-by-step
+To run the server, simply type mvn-Dtwitter.consumerKey=consumer -Dtwitter.consumerSecret=secret -Dtwitter.accessToken=token -Dtwitter.accessTokenSecret=secret verify
+ from this directory but replacing the system properties with those of the twitter account you want to use. Then run the example
+ by using the command mvn -Pexample package
-
+
- First we need to create a ClientSessionFactory with Netty transport configuration +
- We create a core session with auto-commit mode +
- We Create a core producer for queue.outgoingQueue +
- We create a core consumer for queue.incomingQueue +
- We create a core message that we are going to send +
- We send the message to queue.outgoingQueue +
- We start the session +
- We will receive a message from queue.incomingQueue. + Outgoing connector forwards a message(we sent before) to twitter immediately. + Since incoming connector consumes from twitter and forwards to queue.incomingQueue + every 60 seconds, It will be received in 60+x seconds. +
- And finally, remember to close core session and ClientSessionFactory in a
finallyblock.
+
+
+ csf = HornetQClient.createClientSessionFactory(new TransportConfiguration(NettyConnectorFactory.class.getName()));
+
+
+
+ session = csf.createSession(true,true);
+
+
+
+ ClientProducer cp = session.createProducer(OUTGOING_QUEUE);
+
+
+
+ ClientConsumer cc = session.createConsumer(INCOMING_QUEUE);
+
+
+
+ ClientMessage cm = session.createMessage(org.hornetq.api.core.Message.TEXT_TYPE,true);
+String testMessage = System.currentTimeMillis() + ": twitter connector test example";
+cm.getBodyBuffer().writeString(testMessage);
+
+
+
+ cp.send(cm);
+
+
+
+ session.start();
+
+
+
+ ClientMessage received = cc.receive(70 * 1000);
+received.acknowledge();
+String receivedText = received.getBodyBuffer().readString();
+
+
+
+ finally
+{
+ if(session != null)
+ {
+ session.close();
+ }
+ if(csf != null)
+ {
+ csf.close();
+ }
+}
+
+
+
+
+ Vert.x Connector Service Example
+ +This example shows you how to configure HornetQ to use the Vert.x Connector Service.
+ +HornetQ supports 2 types of Vert.x connector, incoming and outgoing. + Incoming connector consumes from Vert.x event bus and forwards to a configurable address. + Outgoing connector consumes from a configurable address and forwards to a configurable Vert.x event bus. +
+ +In this example, an incoming connector and an outgoing connector are configured. A simple java Verticle + is deployed. The verticle registers a message handler on the outgoing connector's address ("outgoing.vertx.address"). + A String message is sent to Vert.x event bus on the incoming connector's address("incoming.vertx.address"). + The message then will be forwarded to a HornetQ queue by the incoming connector. The outgoing connector listens to + the HornetQ queue and forwards the message from HornetQ to Vert.x event bus on the outgoing connector's address. + The verticle finally receives the message from it's event bus.
+ +For more information on Vert.x concept please visit the Vertx site
+ +Example step-by-step
+To run the server, simply type mvn verify
+ from this directory.
-
+
- First we need to create a Vert.x PlatformManager +
- We deploy a Verticle using the platformManager +
- We register a message handler with the event bus in the Verticle to listen on the outgoing connector's address. +
- We send a message to incoming connector's address via event bus +
- The message will eventually arrives at the Verticle's message handler. +
+ platformManager = PlatformLocator.factory.createPlatformManager(PORT, HOST);
+
+
+
+ String verticle = "org.hornetq.core.example.ExampleVerticle";
+ platformManager.deployVerticle(verticle, null, new URL[0], 1, null,
+ new Handler>(){
+
+ @Override
+ public void handle(AsyncResult result)
+ {
+ if (!result.succeeded())
+ {
+ throw new RuntimeException("failed to deploy verticle", result.cause());
+ }
+ latch0.countDown();
+ }
+
+ });
+
+
+
+ EventBus eventBus = vertx.eventBus();
+ eventBus.registerHandler(VertxConnectorExample.OUTGOING,
+ new Handler>() {
+ @Override
+ public void handle(Message startMsg)
+ {
+ Object body = startMsg.body();
+ System.out.println("Verticle receives a message: " + body);
+ VertxConnectorExample.result.set(VertxConnectorExample.MSG.equals(body));
+ latch0.countDown();
+ }
+ });
+
+
+
+
+
+ EventBus bus = platformManager.vertx().eventBus();
+ bus.send(INCOMING, MSG);
+
+
+
+ EJB/JMS Transaction Example
+ +The example application will invoke an EJB which is deployed within WildFly which will:
+-
+
- start an XA transaction +
- send a JMS message +
- update an in-memory database +
- commit the transaction +
The example application will then receive the message sent by the EJB.
+ +WildFly configuration
+ +The example leverages the Arquillian framework to run a WildFly instance and deploy the MDB.
+ +Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
The example code is composed of two main classes:
+-
+
EJBClientExample - the example application
+ SendMessageBean - a Stateless EJB with a remote interface
+
Example Application
+ +Let's take a look at EJBClientExample first.
+ +-
+
- First we need to get an initial context so we can look-up the EJB. This initial context will get it's properties from the jboss-ejb-client.properties. +
- We look up the EJB +
- We create the DB table which will be updated if it does not already exist +
- We invoke the EJB's
sendAndUpdatemethod. This method will send a JMS text message (with the text passed in parameter) + and insert a row in the database table with the text and the message's JMS Message ID
+ - We need to get a new initial context so we can look-up the JMS connection factory and destination objects from JNDI. +
- We look up the JMS connection factory +
- We lookup the JMS queue +
- We create a connection, a session and a message consumer for the queue +
- We start the JMS connection +
- We receive a message from the queue. It corresponds to the message sent by the EJB +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+ Properties env = new Properties(); + env.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming"); + InitialContext initialContext = new InitialContext(); ++ +
+ SendMessageService service = (SendMessageService) initialContext.lookup("ejb:/test//SendMessageBean!org.hornetq.javaee.example.server.SendMessageService");
+
+
+ + service.createTable(); ++ +
+ service.sendAndUpdate("This is a text message");
+
+
+ We will now consume the JMS message which was sent by the EJB at step 4.
+ ++ env = new Properties(); + env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); + env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080"); + initialContext = new InitialContext(env); ++ +
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("jms/RemoteConnectionFactory");
+
+
+
+ Queue queue = (Queue)initialContext.lookup("jms/queues/testQueue");
+
+
+
+ connection = cf.createConnection("guest", "password");
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+ MessageConsumer consumer = session.createConsumer(queue);
+
+
+ + connection.start(); ++ +
+ TextMessage messageReceived = (TextMessage)consumer.receive(5000);
+ System.out.println("Received message: " + messageReceived.getText() + " (" + messageReceived.getJMSMessageID() + ")");
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ EJB Example
+ +Let's now take a look at the EJB example
+ +-
+
- First, we create a new initial context +
- We look up the JMS XA Connection Factory (which is bound to
java:/JmsXA)
+ - We look up the JMS Queue +
- We create a JMS connection, a session and a message producer for the queue +
- We create a text message with the text passed in parameter of the EJB method +
- We send the message to the queue +
- We now lookup the JDBC XA DataSource +
- We retrieve a JDBC connection +
- We create a prepared statement to insert the text and message's ID in the DB table +
- We execute the prepared statement +
- We close the prepared statement +
- And finally, always remember to close all your connections and resources (for both JMS and JDBC) after use, in a
finallyblock.
+
+ ic = new InitialContext(); ++ +
+ ConnectionFactory cf = (ConnectionFactory)ic.lookup("java:/JmsXA");
+
+
+
+ Queue queue = (Queue)ic.lookup("queue/testQueue");
+
+
+ + jmsConnection = cf.createConnection(); + Session session = jmsConnection.createSession(false, Session.AUTO_ACKNOWLEDGE); + MessageProducer messageProducer = session.createProducer(queue); ++ +
+ TextMessage message = session.createTextMessage(text); ++ +
+ messageProducer.send(message);
+ System.out.println("Sent message: " + message.getText() + "(" + message.getJMSMessageID() + ")");
+
+
+
+ DataSource ds = (DataSource)ic.lookup("java:/XADS");
+
+
+ + jdbcConnection = ds.getConnection(); ++ +
+ PreparedStatement pr = jdbcConnection.prepareStatement("INSERT INTO " + TABLE
+ + " (id, text) VALUES ('" + message.getJMSMessageID() + "', '" + text + "');");
+
+
+ + pr.execute(); ++ +
+ pr.close(); ++ +
+ finally
+ {
+ if (ic != null)
+ {
+ ic.close();
+ }
+ if (jmsConnection != null)
+ {
+ jmsConnection.close();
+ }
+ if (jdbcConnection != null)
+ {
+ jdbcConnection.close();
+ }
+ }
+
+ Java EE Resource Adapter Configuration Example
+ +This example demonstrates how to configure several properties on the HornetQ Resource Adapter. We setup two + WildFly. The enterprise application is being deployed in one application server while the MDBs and JMS + Connections are pointing to a remote server
+This example is composed of two message-driven beans (MDB), MDBQueueA and MDBQueueB, and a stateless session + bean StatelessSender, and a main class MDBRemoteClientExample.
+
MDBRemoteClientExample will invoke the StatelessSender bean on the second server which will in turn send a + message to 2 queues on the first server which will then be consumed by each MDB.
+MDBQueueA consumes the message locally.
+MDBQueueB is on the second server who's JCA Adapter is configured to consume remotely from the first server
+ +WildFly configuration
+ +The example leverages the Arquillian framework to run multiple WildFly instances and deploy the MDBs and SLSB.
+ +Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
-
+
- First we need to get an initial context so we can look-up the EJB. This initial context will get it's properties from the jboss-ejb-client.properties. +
- Getting a reference to the Stateless Bean +
- Calling the Stateless Bean +
- On the second server we invoke the EJB StatelessSender: This will send 2 messages to server 1 using the configured outbound adapter +
- Create a connection to a remote server using a connection-factory we injected. JCA will actually manage this through a connection pool +
- Send a message to a QueueA on server1, which will be received by MDBQueueA on server1 +
- Send a message to a QueueB on the remote server1, which will be received by MDBQueueA on server2 +
- Close the connection. (Since this is a JCA connection, this close will return the connection back to the connection pool) +
- The message is received by MDBQueueA on server1 which consumed from a local queue + +
- Another message is received on MDBQueueB on server2 which consumed from a remote queue on server1.
+
+
+@MessageDriven(name = "MDB_QueueB", + activationConfig = + { + @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), + @ActivationConfigProperty(propertyName = "destination", propertyValue = "B"), + @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false") + }) +@ResourceAdapter("hornetq-ra-remote.rar") +public class MDBQueueB implements MessageListener +{ + public void onMessage(Message message)... ++
+ Properties env = new Properties(); + env.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming"); + initialContext = new InitialContext(env); ++ +
+ StatelessSenderService sender = (StatelessSenderService)initialContext.lookup("ejb:/test//StatelessSender!org.hornetq.javaee.example.server2.StatelessSenderService");
+
+
+
+ sender.sendHello("Hello there MDB!");
+
+
+
+ Queue destQueueA = HornetQJMSClient.createQueue("A");
+ Queue destQueueB = HornetQJMSClient.createQueue("B");
+
+
+
+ Connection conn = connectionFactory.createConnection("guest", "password");
+
+
+ + Session sess = conn.createSession(false, Session.AUTO_ACKNOWLEDGE); + MessageProducer prodA = sess.createProducer(destQueueA); + prod.send(sess.createTextMessage(message)); ++ +
+ MessageProducer prodB = sess.createProducer(destQueueB); + prodB.send(sess.createTextMessage(message)); ++ +
+ conn.close(); ++ +
+@MessageDriven(name = "MDB_QueueA",
+ activationConfig =
+ {
+ @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
+ @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/A")
+ })
+public class MDBQueueA implements MessageListener
+{
+ public void onMessage(Message message)...
+
+
+ Java EE JCA Resource Adapter Remote Server Configuration Example
+This example demonstrates how to configure the Resource adapter to connect to a remote HornetQ server
+This example is composed of a message driven bean and a client
+
MDBRemoteServerClientExample will send a message to the MDB via a queue and wait for the MDB to send a response via + a reply queue
+ +WildFly configuration
+ +The example leverages the Arquillian framework to run a WildFly instance and deploy the MDB.
+ +Configuring the incoming JCA resource adapter
+ +The MDB will consume messages via the inflow JCA resource adapter. This can be configured in 2 ways:
+-
+
- via a pooled-connection-factory in the "messaging" subsystem +
- via the activation configuration properties on the MDB set either via annotations or ejb-jar.xml +
In this example the MDB is annotated with @ResourceAdapter("hornetq-ra-remote.rar") which refers to
+ this pooled-connection-factory:
+ <pooled-connection-factory name="hornetq-ra-remote"> + <transaction mode="xa"/> + <user>guest</user> + <password>password</password> + <connectors> + <connector-ref connector-name="remote-http-connector"/> + </connectors> + <entries> + <entry name="java:/RemoteJmsXA"/> + </entries> + </pooled-connection-factory> ++
This configuration ensures the MDB will consume from the remote queue.
+ +Configuring the outgoing JCA resource adapter
+ +The same pooled-connection-factory used for JCA inflow also configures an outgoing JCA connection factory which Java EE components can use to send messages to the same remote HornetQ Server.
++ <pooled-connection-factory name="hornetq-ra-remote"> + <transaction mode="xa"/> + <user>guest</user> + <password>password</password> + <connectors> + <connector-ref connector-name="remote-http-connector"/> + </connectors> + <entries> + <entry name="java:/RemoteJmsXA"/> + </entries> + </pooled-connection-factory> ++ +
Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
-
+
- First we need to get an initial context so we can send a JMS message to the second server. +
- Look up the MDB's queue +
- look up the connection factory +
- We then create a connection +
- we then create a session +
- we now create a message producer to send the message +
- create a text message and send it +
- The MDB receives the text message +
- The MDB looks up the reply queue +
- The MDB creates a connection +
- The MDB creates a session +
- The MDB creates a message producer to send the message +
- The MDB creates and sends a text message +
- The MDB closes the connection which returns it to the pool +
- The client now looks up the reply queue +
- and creates a message consumer to receive the message +
- starting the connection starts delivery +
- The message consumer receives the text message +
- and we always clear up out JMS resources +
+ final Properties env = new Properties(); + + env.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming"); + + env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); + + env.put(Context.PROVIDER_URL, "http-remoting://localhost:8180"); + + initialContext = new InitialContext(env); ++
+ Queue queue = (Queue) initialContext.lookup("queues/mdbQueue");
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("jms/RemoteConnectionFactory");
+
+
+ connection = cf.createConnection("guest", "password");
+
+ + Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); ++
+ MessageProducer producer = session.createProducer(queue); ++
+ producer.send(session.createTextMessage("a message"));
+
+ + TextMessage tm = (TextMessage)message; ++
+ Queue destQueue = HornetQJMSClient.createQueue("mdbReplyQueue");
+
+ + Connection connection = connectionFactory.createConnection(); ++
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); ++
+ MessageProducer producer = session.createProducer(destQueue); ++
+ producer.send(session.createTextMessage("A reply message"));
+
+ + connection.close(); ++
+ Queue replyQueue = (Queue) initialContext.lookup("queues/mdbReplyQueue");
+
+ + MessageConsumer consumer = session.createConsumer(replyQueue); ++
+ connection.start(); ++
+ TextMessage textMessage = (TextMessage) consumer.receive(5000); ++
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+
+ JMS Bridge Example
+ +This example shows how to configure and run a JMS Bridge in WildFly.
+ A bridge receives messages from a source JMS destination and forwards them to a target destination.
The source and target destinations can be on different servers, even from different JMS providers. For example, you can use this + JMS Bridge to bridge a legacy JMS provider to HornetQ during migration.
+ +This example will show how to configure and run the simplest bridge:
+-
+
- the source and target destinations are hosted by a single WildFly instance +
- the bridge is run on the same WildFly instance +
- every time a message is consumed by the bridge from the source, it is forward to the target +
- The application client will send a message to the source and consume the "same" message from the target to + show that the two destinations were indeed bridged. +
JMS Bridge configuration
+ +The JMS Bridge is configured in the "messaging" subsystem.
+
The Bridge is deployed in the application server when you simply type ./build.sh deploy (or build.bat deploy on windows) (it is copied to ${JBOSS_HOME}/server/default-with-hornetq/deploy/).
Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
The example is simple: the application will send a message to the source queue and consume the same message + from the target queue.
+The bridge is configured in the messaging subsystem:
+ ++ <jms-bridge name="myBridge"> + <source> + <connection-factory name="ConnectionFactory" /> + <destination name="queue/sourceQueue" /> + </source> + <target> + <connection-factory name="ConnectionFactory" /> + <destination name="queue/targetQueue" /> + </target> + <quality-of-service>AT_MOST_ONCE</quality-of-service> + <failure-retry-interval>1000</failure-retry-interval> + <max-retries>7890</max-retries> + <max-batch-size>1</max-batch-size> + <max-batch-time>1000</max-batch-time> + </jms-bridge> ++ +
-
+
- First we need to get an initial context so we can look up the JMS resources + +
- We look up the JMS ConnectionFactory +
- We look up the JMS source queue +
- We create a JMS connection, a session and a message producer for the source queue +
- We create and send a message to the source queue. We also display its Message ID. +
- We close the source connection +
- We look up the JMS target queue +
- We create a connection, a session and a message consumer for the target queue +
- We start the JMS connection to receive messages from the target +
- We receive a message from the target queue. It has the same content than the message sent to the source queue +
- We now display the received message ID. It is not the same than the ID of the message sent to the source queue. + The message received from the target queue was sent by the bridge, not by the source message producer +
- If you need to retrieve the message ID of the message sent to the source, you can use the property
HQ_BRIDGE_MSG_ID_LIST
+ - And finally, always remember to close the JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+ final Properties env = new Properties(); + + env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); + + env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080"); + + initialContext = new InitialContext(env); ++ +
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/jms/RemoteConnectionFactory");
+
+
+ First, we will send a message to the source queue.
+ +
+ Queue sourceQueue = (Queue)initialContext.lookup("jms/queues/sourceQueue");
+
+
+
+ sourceConnection = cf.createConnection("guest", "password");
+ Session sourceSession = sourceConnection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+ MessageProducer sourceProducer = sourceSession.createProducer(sourceQueue);
+
+
+
+ TextMessage message = sourceSession.createTextMessage("this is a text message");
+ sourceProducer.send(message);
+ System.out.format("Sent message to %s: %s\n",
+ ((Queue)message.getJMSDestination()).getQueueName(),
+ message.getText());
+ System.out.format("Message ID : %s\n", message.getJMSMessageID());
+
+
+ + sourceConnection.close(); ++ +
Now that a message has been sent to the source queue, we will consume a message
+ from the target queue.
+ If the bridge runs correctly, it will have consumed the message from the source and
+ resent it to the target so that we can consume a message from it.
+ Queue targetQueue = (Queue)initialContext.lookup("jms/queues/targetQueue");
+
+
+ + targetConnection = cf.createConnection(); + Session targetSession = targetConnection.createSession(false, Session.AUTO_ACKNOWLEDGE); + MessageConsumer targetConsumer = targetSession.createConsumer(targetQueue); ++ +
+ targetConnection.start(); ++ +
+ TextMessage messageReceived = (TextMessage)targetConsumer.receive(15000);
+ System.out.format("\nReceived from %s: %s\n",
+ ((Queue)messageReceived.getJMSDestination()).getQueueName(),
+ messageReceived.getText());
+
+
+
+
+ System.out.format("Message ID : %s\n", messageReceived.getJMSMessageID());
+
+
+
+ System.out.format("Bridged Message ID : %s\n", messageReceived.getStringProperty("HQ_BRIDGE_MSG_ID_LIST"));
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (sourceConnection != null)
+ {
+ sourceConnection.close();
+ }
+ if (targetConnection != null)
+ {
+ targetConnection.close();
+ }
+ }
+
+ Java EE Injected JMSContext Example
+ +This example shows you how to inject a JMSContext into an MDB and use it to send a reply to a JMS Client
+ +Wildfly configuration
+ +The example leverages the JBoss Arquillian framework to run an Wildfly 8 instance and deploy the MDB.
+ +Example step-by-step
+download The latest Wildfly 8 from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+To run the example simply type mvn testfrom the example directory
-
+
- Firstly in the MDB we inject the JMSContext. This will use the Default Connection Factory configured. + +
- We then map the reply queue as a resource. + +
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. +
- We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMSContext inside the try-with-resource block so it auto closes +
- We create a JMS Producer and send a String as a message. +
- We start the context so we can receive messages. +
- We look up the reply queue. +
- We receive the body, as a String, of the reply message. +
- And finally, close the initial context. + +
+
+ @Inject
+ javax.jms.JMSContext context;
+
+
+
+ @Resource(mappedName = "java:/queue/replyQueue")
+ Queue replyQueue;
+
+
+
+ final Properties env = new Properties();
+
+ env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
+
+ env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080");
+
+ initialContext = new InitialContext(env);
+
+
+
+
+
+ Queue queue = (Queue)initialContext.lookup("jms/queues/testQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("jms/RemoteConnectionFactory");
+
+
+
+
+ try
+ (
+ // Step 6.Create a JMS Connection inside the try-with-resource block so it will auto close
+ JMSContext context = cf.createContext("guest", "password")
+ )
+
+
+
+
+ context.createProducer().send(queue, "This is a text message");
+
+
+
+ context.start();
+
+
+
+ Queue replyQueue = (Queue)initialContext.lookup("jms/queues/replyQueue");
+
+
+
+ String text = context.createConsumer(replyQueue).receiveBody(String.class);
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ }
+
+
+
+
+ Java EE MDB Bean Managed Transaction Example
+ +This example shows you how to send a message to an MDB configured to use Bean Managed Transactions
+The example will send deploy a simple MDB and demonstrate sending a message and the MDB consuming it.
+ +The example leverages the JBoss Arquillian framework to run a WildFly instance and deploy the MDB.
+ +Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
jndi.propertiesfile in the directoryconfig
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text messages that we are going to send. +
- We send messages to the queue +
- The MDB receives the message
+ We know the message is a TextMessage so we cast to it. +
+ - The MDB gets the text and prints it + +
- Now we can do something within a user transaction, let's just start and commit it + +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+ final Properties env = new Properties(); + + env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); + + env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080"); + + initialContext = new InitialContext(env); ++ +
+ Queue queue = (Queue)initialContext.lookup("jms/queues/testQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/jms/RemoteConnectionFactory");
+
+
+
+ connection = cf.createConnection("guest", "password");
+
+
+ + Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); ++ +
+ MessageProducer messageProducer = session.createProducer(queue); ++ +
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+ + messageProducer.send(message); ++ +
+ TextMessage tm = (TextMessage)message; ++ +
+ String text = tm.getText();
+ System.out.println("message " + text + " received");
+
+
+
+ UserTransaction tx = ctx.getUserTransaction();
+
+ if(tx != null)
+ {
+ tx.begin();
+ System.out.println("we're in the middle of a transaction: " + tx);
+ tx.commit();
+ }
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ Java EE MDB SetRollbackOnly with DLQ Example
+ +This example shows you how to send a message to an MDB and then roll back the transaction forcing delivery of the message to a DLQ.
+The example will send deploy a simple MDB and demonstrate sending a message, MDB consuming it, and then the + standalone client consuming it from the DLQ and printing out the special DLQ properties "_HQ_ORIG_ADDRESS" + and "_HQ_ORIG_QUEUE".
+ +The example leverages the JBoss Arquillian framework to run a WildFly instance and deploy the MDB.
+ +Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
jndi.propertiesfile in the directoryconfig
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text messages that we are going to send. +
- We send messages to the queue +
- The MDB receives the message
+ We know the message is a TextMessage so we cast to it.
+ - The MDB gets the text and prints it +
- The MDB rolls back the container-managed transaction to send the message to the DLQ +
- Perform a lookup on the DLQ +
- Create the consumer and start the connection +
- Receive the message. +
- Print the special DLQ properties +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+ final Properties env = new Properties(); + + env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); + + env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080"); + + initialContext = new InitialContext(env); ++ +
+ Queue queue = (Queue)initialContext.lookup("jms/queues/testQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/jms/RemoteConnectionFactory");
+
+
+
+ connection = cf.createConnection("guest", "password");
+
+
+ + Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); ++ +
+ MessageProducer messageProducer = session.createProducer(queue); ++ +
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+ + producer.send(message); ++ +
+ TextMessage tm = (TextMessage)message; ++ +
+ String text = textMessage.getText();
+ System.out.println("message " + text + " received");
+
+
+ + ctx.setRollbackOnly(); ++ +
+ destination = (Destination) initialContext.lookup("jms/queues/dlq");
+
+
+ + MessageConsumer consumer = session.createConsumer(destination); + connection.start(); ++ +
+ message = (TextMessage) consumer.receive(3000); ++ +
+ System.out.println("Original address: " + message.getStringProperty("_HQ_ORIG_ADDRESS"));
+ System.out.println("Original queue: " + message.getStringProperty("_HQ_ORIG_QUEUE"));
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ Java EE MDB SetRollbackOnly Example
+ +This example shows you how to send a message to an MDB and then roll back the transaction forcing re delivery
+The example will send deploy a simple MDB and demonstrate sending a message and the MDB consuming it twice.
+ +The example leverages the JBoss Arquillian framework to run a WildFly instance and deploy the MDB.
+ +Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
jndi.propertiesfile in the directoryconfig
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text messages that we are going to send. +
- We send messages to the queue +
- The MDB receives the message
+ We know the message is a TextMessage so we cast to it. +
+ - The MDB gets the text and prints it, if its the first time we roll back + +
- The message is received again but this time we just print the text + +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+ final Properties env = new Properties(); + + env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); + + env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080"); + + initialContext = new InitialContext(env); ++ +
+ Queue queue = (Queue)initialContext.lookup("jms/queues/testQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/jms/RemoteConnectionFactory");
+
+
+
+ connection = cf.createConnection("guest", "password");
+
+
+ + Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); ++ +
+ MessageProducer messageProducer = session.createProducer(queue); ++ +
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+ + messageProducer.send(message); ++ +
+ TextMessage tm = (TextMessage)message; ++ +
+ String text = textMessage.getText();
+
+ if(!textMessage.getJMSRedelivered())
+ {
+ //Step 11. rollback delivery of message if the first time
+ System.out.println("message " + text + " received for the first time");
+ ctx.setRollbackOnly();
+ }
+
+
+
+ System.out.println("message " + text + " received for the second time");
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ Java EE MDB using a local transaction Example
+ +This example shows you how to send a message to an MDB and deliver it within a local transaction
+The example will send deploy a simple MDB and demonstrate sending a message and the MDB consuming it, throwing an exception and the message being re delivered.
+ +The example leverages the JBoss Arquillian framework to run a WildFly instance and deploy the MDB.
+ +Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
jndi.propertiesfile in the directoryconfig
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text messages that we are going to send. +
- We send messages to the queue +
- The MDB receives the message
+ We know the message is a TextMessage so we cast to it. +
+ - The MDB gets the text and prints it, we take a quick look at the transaction and throw an exception. + +
- The MDB receives the message again and we print a message. + +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+ final Properties env = new Properties(); + + env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); + + env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080"); + + initialContext = new InitialContext(env); ++ +
+ Queue queue = (Queue)initialContext.lookup("jms/queues/testQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/jms/RemoteConnectionFactory");
+
+
+
+ connection = cf.createConnection("guest", "password");
+
+
+ + Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); ++ +
+ MessageProducer messageProducer = session.createProducer(queue); ++ +
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+ + messageProducer.send(message); ++ +
+ TextMessage tm = (TextMessage)message; ++ +
+ System.out.println("message " + text + " received");
+
+ if (!textMessage.getJMSRedelivered())
+ {
+ //Step 11. On first delivery get the transaction, take a look, and throw an exception
+ Transaction tx = tm.getTransaction();
+
+ if (tx != null)
+ {
+ System.out.println("something is wrong, there should be no global transaction: " + tx);
+ }
+ else
+ {
+ System.out.println("there is no global transaction, although the message delivery is using a local transaction");
+ System.out.println("let's throw an exception and see what happens");
+ throw new RuntimeException("DOH!");
+ }
+ }
+
+
+
+ System.out.println("The message was redelivered since the message delivery used a local transaction");
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ Java EE MDB Container Managed Transaction with NOT_SUPPORTED transaction Example
+ +This example shows you how to send a message to an MDB
+The example will deploy a simple MDB and send a message. The MDB consuming it will not use a transaction.
+ +The example leverages the JBoss Arquillian framework to run a WildFly instance and deploy the MDB.
+ +Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
jndi.propertiesfile in the directoryconfig
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text messages that we are going to send. +
- We send messages to the queue +
- The MDB receives the message
+ We know the message is a TextMessage so we cast to it. +
+ - The MDB gets the text and prints it + +
- We look at the transaction to make sure there isn't one + +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+ final Properties env = new Properties(); + + env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); + + env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080"); + + initialContext = new InitialContext(env); ++ +
+ Queue queue = (Queue)initialContext.lookup("jms/queues/testQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/jms/RemoteConnectionFactory");
+
+
+
+ connection = cf.createConnection("guest", "password");
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(queue);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+
+ messageProducer.send(message);
+
+
+
+ TextMessage tm = (TextMessage)message;
+
+
+
+ String text = tm.getText();
+ System.out.println("message " + text + " received");
+
+
+
+
+ Transaction tx = tm.getTransaction();
+
+ if(tx == null)
+ {
+ System.out.println("tx is null, just as expected");
+ }
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ Java EE MDB Container Managed Transactions Example
+ +This example shows you how to send a message to an MDB that is delivered within a transaction controlled by the container
+The example will send deploy a simple MDB and demonstrate sending a message and the MDB consuming it
+ +The example leverages the JBoss Arquillian framework to run a WildFly instance and deploy the MDB.
+ +Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
jndi.propertiesfile in the directoryconfig
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text messages that we are going to send. +
- We send messages to the queue +
- The MDB receives the message
+ We know the message is a TextMessage so we cast to it. +
+ - We take alook at the transaction and see that it is running. + +
- The MDB gets the text and prints it + +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+ final Properties env = new Properties(); + + env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); + + env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080"); + + initialContext = new InitialContext(env); ++ +
+ Queue queue = (Queue)initialContext.lookup("jms/queues/testQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/jms/RemoteConnectionFactory");
+
+
+
+ connection = cf.createConnection("guest", "password");
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(queue);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+
+ messageProducer.send(message);
+
+
+
+ TextMessage tm = (TextMessage)message;
+
+
+
+ Transaction tx = tm.getTransaction();
+
+ if(tx != null)
+ {
+ System.out.println("we're in the middle of a transaction: " + tx);
+ }
+
+
+
+ String text = tm.getText();
+ System.out.println("message " + text + " received");
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ Java EE MDB Message Selector Example
+ +This example shows you how to send a message to an MDB that is configured to use a message selector
+The example will send deploy a simple MDB and demonstrate sending a message and the MDB consuming only the message that matches the message selector.
+ +The example leverages the JBoss Arquillian framework to run a WildFly instance and deploy the MDB.
+ +Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
jndi.propertiesfile in the directoryconfig
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text messages that we are going to send. +
- Set the color property on the message to 'BLUE'. +
- We send messages to the queue +
- We create a second JMS text message that we are going to send. +
- Set the color property on the message to 'RED'. +
- We send messages to the queue +
- The MDB receives the message
+ We know the message is a TextMessage so we cast to it. +
+ - We get the color property to check it + +
- The MDB gets the text and color and print it + +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+ final Properties env = new Properties(); + + env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); + + env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080"); + + initialContext = new InitialContext(env); ++ +
+ Queue queue = (Queue)initialContext.lookup("jms/queues/testQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/jms/RemoteConnectionFactory");
+
+
+
+ connection = cf.createConnection("guest", "password");
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(queue);
+
+
+
+ TextMessage blueMessage = session.createTextMessage("This is a text message");
+
+
+
+ blueMessage.setStringProperty("color", "BLUE");
+
+
+
+ messageProducer.send(blueMessage);
+
+
+
+ TextMessage redMessage = session.createTextMessage("This is a text message");
+
+
+
+ redMessage.setStringProperty("color", "RED");
+
+
+
+ messageProducer.send(redMessage);
+
+
+
+ TextMessage tm = (TextMessage)message;
+
+
+
+ String color = textMessage.getStringProperty("color");
+
+
+
+ String text = tm.getText();
+ System.out.println("message " + text + " received color=" + color);
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ Java EE MDB Remote Failover Static Example
+ +This example shows you how to send a message to an MDB that is configured to consume from a live/backup pair.
+The example will send deploy a simple MDB to one Wildfly instance. Then it will send a message to the live server of the live/backup pair + which will be consumed by the MDB after which the MDB will send a reply message which will be consumed by the example program. Then the live + server will be stopped so that the backup takes over and the process will be repeated.
+ +Unlike the "Java EE MDB Remote Failover Example," this example uses a "static" configuration for finding all the nodes. In other words + it doesn't use UDP multicast for server discovery.
+ +The example leverages the JBoss Arquillian framework to run a WildFly instance and deploy the MDB.
+ +Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
jndi.propertiesfile in the directoryconfig
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text messages that we are going to send. +
- We send the message to the queue +
- MDB receives the message +
- Get and print the text +
- Create a JMS connection using the injected connection factory +
- Create a JMS session +
- Create a producer +
- Create a message and send it to the reply queue +
- Client looks up the reply queue +
- Create a consumer +
- Start the connection +
- Receive the message and print it out +
- Kill the live server. At this point both the standalone client and the MDB will fail-over to the backup. +
- Create another message +
- Send the message +
- The MDB will receive the message and send another message to the reply queue which the client then receives +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+ final Properties env = new Properties(); + + env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); + + env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080"); + + initialContext = new InitialContext(env); ++ +
+ Queue queue = (Queue) initialContext.lookup("/queues/inQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/jms/RemoteConnectionFactory");
+
+
+
+ connection = cf.createConnection("guest", "password");
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(queue);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+
+ messageProducer.send(message);
+
+
+
+ TextMessage textMessage = (TextMessage)message;
+
+
+
+ String text = textMessage.getText();
+
+ System.out.println("message " + text);
+
+
+
+ conn = connectionFactory.createConnection();
+
+
+
+ Session sess = conn.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer producer = sess.createProducer(replyQueue);
+
+
+
+ producer.send(sess.createTextMessage("this is a reply"));
+
+
+
+ queue = (Queue) initialContext.lookup("/queues/outQueue");
+
+
+
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+
+
+ connection.start();
+
+
+
+ message = (TextMessage) messageConsumer.receive(20000);
+
+ System.out.println("message.getText() = " + message.getText());
+
+
+
+ killer.kill();
+
+
+
+ message = session.createTextMessage("This is another text message");
+
+
+
+ producer.send(message);
+
+
+
+ message = (TextMessage) messageConsumer.receive(20000);
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ Java EE MDB Remote Failover Example
+ +This example shows you how to send a message to an MDB that is configured to consume from a live/backup pair.
+The example will send deploy a simple MDB to one Wildfly instance. Then it will send a message to the live server of the live/backup pair + which will be consumed by the MDB after which the MDB will send a reply message which will be consumed by the example program. Then the live + server will be stopped so that the backup takes over and the process will be repeated.
+ +Unlike the "Java EE MDB Remote Failover Static Example," this example uses a "dynamic" configuration for finding all the nodes. In other words + it uses UDP multicast for server discovery.
+ +The example leverages the JBoss Arquillian framework to run a WildFly instance and deploy the MDB.
+ +Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
jndi.propertiesfile in the directoryconfig
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text messages that we are going to send. +
- We send the message to the queue +
- MDB receives the message +
- Get and print the text +
- Create a JMS connection using the injected connection factory +
- Create a JMS session +
- Create a producer +
- Create a message and send it to the reply queue +
- Client looks up the reply queue +
- Create a consumer +
- Start the connection +
- Receive the message and print it out +
- Kill the live server. At this point both the standalone client and the MDB will fail-over to the backup. +
- Create another message +
- Send the message +
- The MDB will receive the message and send another message to the reply queue which the client then receives +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+ final Properties env = new Properties(); + + env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); + + env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080"); + + initialContext = new InitialContext(env); ++ +
+ Queue queue = (Queue) initialContext.lookup("/queues/inQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/jms/RemoteConnectionFactory");
+
+
+
+ connection = cf.createConnection("guest", "password");
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(queue);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+
+ messageProducer.send(message);
+
+
+
+ TextMessage textMessage = (TextMessage)message;
+
+
+
+ String text = textMessage.getText();
+
+ System.out.println("message " + text);
+
+
+
+ conn = connectionFactory.createConnection();
+
+
+
+ Session sess = conn.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer producer = sess.createProducer(replyQueue);
+
+
+
+ producer.send(sess.createTextMessage("this is a reply"));
+
+
+
+ queue = (Queue) initialContext.lookup("/queues/outQueue");
+
+
+
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+
+
+ connection.start();
+
+
+
+ message = (TextMessage) messageConsumer.receive(20000);
+
+ System.out.println("message.getText() = " + message.getText());
+
+
+
+ killer.kill();
+
+
+
+ message = session.createTextMessage("This is another text message");
+
+
+
+ producer.send(message);
+
+
+
+ message = (TextMessage) messageConsumer.receive(20000);
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ Java EE MDB TX Send Example
+ +This example shows you how to send a message to an MDB that returns a reply using the same XA transaction.
+The example will send deploy a simple MDB and demonstrate sending a message and the MDB consuming it.
+ +The example leverages the JBoss Arquillian framework to run a WildFly instance and deploy the MDB.
+ +Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
jndi.propertiesfile in the directoryconfig
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text messages that we are going to send. +
- We send messages to the queue +
- The MDB receives the message
+ We know the message is a TextMessage so we cast to it. +
+ - The MDB gets the text and prints it + +
- The MDB creates a JMS connection + +
- The MDB creates a JMS session + +
- The MDB creates a JMS message producer + +
- The MDB creates a text message and sends it to the reply queue + +
- The Client creates a JMS message consumer using the injected reply queue + +
- The Client starts the connection so it can receive messages + +
- The Client receives the reply and prints it out + +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+ final Properties env = new Properties(); + + env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); + + env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080"); + + initialContext = new InitialContext(env); ++ +
+ Queue queue = (Queue) initialContext.lookup("jms/queues/testQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/jms/RemoteConnectionFactory");
+
+
+
+ connection = cf.createConnection("guest", "password");
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(queue);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+
+ messageProducer.send(message);
+
+
+
+ TextMessage tm = (TextMessage)message;
+
+
+
+ String text = tm.getText();
+ System.out.println("message " + text + " received");
+
+
+
+
+ conn = connectionFactory.createConnection();
+
+
+
+
+ Session sess = conn.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+ MessageProducer producer = sess.createProducer(replyQueue);
+
+
+
+
+ producer.send(sess.createTextMessage("this is a reply"));
+
+
+
+
+ MessageConsumer messageConsumer = session.createConsumer(replyQueue);
+
+
+
+
+ connection.start();
+
+
+
+
+ message = (TextMessage) messageConsumer.receive(5000);
+
+ System.out.println("message.getText() = " + message.getText());
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ Java EE XA Recovery Example
+ +This example will demonstrate XA recovery in WildFly with a HornetQ XA resource and a "buggy" XA resource.
+ +The example application will invoke an EJB which will send a JMS message in a transaction.
+ The server will crash while the transaction has not been committed (it is in the prepared state).
+ On server restart, the transaction will be recovered and the JMS message will finally be sent.
+ The example application will then receive the message.
+
+
The example leverages the JBoss Arquillian framework to run a WildFly instance and deploy the MDB.
+ +XA Recovery configuration
+ +In previous versions of JBoss Application Server (the precursor to WildFly) the XA recovery configuration was manual. + However, in WildFly the XA recovery configuration is completely automated.
+ +Example step-by-step
+ +download WildFly 8.0.0.Final from here and install.
+set the JBOSS_HOME property to point to the WildFly install directory
+type mvn verify from the example directory to run
The example code is composed of 3 main classes:
+-
+
XARecoveryExampleStepOneandXARecoveryExampleStepTwo
+ - the client application to invoke the EJB and receive the message +
XARecoveryExampleBean
+ - a Stateless EJB3 which performs all the XA logic +
Example Application
+ +Let's take a look at XARecoveryExampleStepOne first.
+ +-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the jndi.properties + +
- We look up the EJB +
- We invoke the EJB's
sendmethod. This method will send a JMS text message (with the text passed in parameter) + and crash the server when committing the transaction
+
+
+ Properties env = new Properties();
+ env.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
+ initialContext = new InitialContext(env);
+
+
+
+
+ XARecoveryExampleService service = (XARecoveryExampleService) initialContext.lookup("ejb:/test//XARecoveryExampleBean!org.hornetq.javaee.example.server.XARecoveryExampleService");
+
+
+
+ String message = "This is a text message sent at " + new Date();
+ System.out.println("invoking the EJB service with text: " + message);
+ try
+ {
+ service.send(message);
+ }
+ catch (Exception e)
+ {
+ System.out.println("#########################");
+ System.out.println("The server crashed: " + e.getMessage());
+ System.out.println("#########################");
+ }
+
+
+ At that time, the server is crashed and is automatically restarted by the test runner (i.e. XARecoveryRunnerTest).
+Let's take a look at XARecoveryExampleStepTwo now.
+ +-
+
- We will try to receive a message. Once the server is restarted, the message will be recovered and the consumer will receive it. +
- And finally, always remember to close your resources after use, in a
finallyblock.
+
+
+ boolean received = false;
+ while (!received)
+ {
+ try
+ {
+ Thread.sleep(15000);
+ receiveMessage();
+ received = true;
+ }
+ catch (Exception e)
+ {
+ System.out.println(".");
+ }
+ }
+
+ The receiveMessage() method contains code to receive a text message from the
+ JMS Queue and display it.
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ }
+
+ Let's now take a look at the EJB example
+ +In order to crash the server while a transaction is prepared, we will use a failing XAResource
+ which will crash the server (calling Runtime.halt()) in its commit phase.
We will manage ourselves the transaction and its resources enlistment/delistment to be sure that the failing XAResource + will crash the server after the JMS XA resources is prepared but before it is committed.
+ +-
+
- First, we create a new initial context +
- We look up the Transaction Manager +
- We look up the JMS XA Connection Factory (which is bound to
java:/JmsXA)
+ - We look up the JMS Queue +
- We create a JMS XA connection, a XA session and a message producer for the queue +
- We create a
FailingXAResource. For this example purpose, this XAResource implementation will + callRuntime.halt()from itscommit()method
+ - We begin the transaction and retrieve it from the transaction manager +
- We enlist the failing XAResource +
- We enlist the JMS XA Resource +
- We create a text message with the text passed in parameter of the EJB method and send it +
- We delist the failing XAResource +
- We delist the JMS XA Resource +
- We commit the transaction +
- endpoint - The endpoint or URL of you AeroGear application +
- queue - The name of the queue to consume from +
- application-id - The application id of your mobile application in AeroGear +
- master-secret - the secret of your mobile application in AeroGear +
- ttl - The time to live for the message once AeroGear receives it +
- badge - The badge the mobile app should use for the notification +
- sound - The sound the mobile app should use for the notification +
- filter - A message filter(selector) to use on the connector +
- retry-interval - If an error occurs on send, how long before we try again +
- retry-attempts - How many times we should try to reconnect after an error +
- variants - A comma separated list of variants that should get the message +
- aliases - A list of aliases that should get the message +
- device-types - A list of device types that should get the message +
- We create our JMS Connection, Session, MessageProducer and MessageConsumer on server 1 +
- We set a JMS ExceptionListener on the connection. On failure this will be called and the connection, + session, etc. will be manually recreated on the backup node. +
- We send some messages to server 1, the live server. +
- We consume those messages on server 1. +
- We now cause server 1, the live server to crash. After a little while the connection's + ExceptionListener will register the failure and reconnection will occur. +
- The connection's ExceptionListener gets called, and we lookup the JMS objects and + recreate the connection, session, etc on the other node 0. +
- We are now connected to the other node. We now send some more messages. +
- And consume them. +
- And finally (no pun intended), always remember to close your resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - We create an initial context for looking up JNDI on node 0 +
- We look up the sausage-factory queue from node 0 +
- We look up a JMS ConnectionFactory object from node 0 +
- We create an initial context for looking up JNDI on node 1 +
- We look up the mincing-machine queue on node 1 +
- We look up a JMS ConnectionFactory object from node 1 +
- We create a JMS Connection connection0 which is a connection to server 0 +
- We create a JMS Connection connection1 which is a connection to server 1 +
- We create a JMS Session on server 0 +
- We create a JMS Session on server 1 +
- We start the connection to ensure delivery occurs on them +
- We create a JMS MessageConsumer object on server 1 +
- We create a JMS MessageProducer object on server 0. +
- We create and send a message representing an aardvark with a green hat to the sausage-factory + on node 0 +
- We successfully receive the aardvark message from the mincing-machine one node 1. The aardvark's + hat is now blue since it has been transformed! +
- We create and send another message, this time representing a sasquatch with a mauve hat to the + sausage-factory on node 0. This won't be bridged to the mincing-machine since we only want aardvarks, not sasquatches. +
- We don't receive the sasquatch message since it's not an aardvark! +
- And finally (no pun intended), always remember to close your JMS resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create 2 JMS text messages that we are going to send. +
- We send messages to the queue +
- We create a JMS QueueBrowser.
+ We have not specified a message selector so the browser will enumerate the entire content of the queue. +
+ - We browse the queue and display all the messages' text + +
- We close the browser once we have finished to use it +
- We create a JMS Message Consumer to receive the messages. +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- The 2 messages arrive at the consumer +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get its properties from client-jndi.properties +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We set a
ExceptionListeneron the connection to be notified after a problem occurred
+ - We start the connection +
- We create a MBean proxy to the HornetQServerControlMBean used to manage HornetQ server + (see JMX example for a complete explanation of the different steps) +
- Using the server MBean, we list the remote address connected to the server +
- We close the connections corresponding to this remote address +
- We display the exception received by the connection's ExceptionListener +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get its properties from client-jndi.properties +
- We look up the JMS Queue object from JNDI +
- We look up a JMS Connection Factory object from JNDI on server 0 +
- We create a JMS connection from the same connection factory, wait a little while to make sure broadcasts from all nodes have reached the client +
- We create JMS Sessions +
- We create JMS MessageProducer objects on the sessions +
- We send some messages on each producer +
- We start the connection to consume messages +
- We consume messages from the session A, one at a time. We reached message no 5 the first server will crash +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - Get an initial context for looking up JNDI from server 0. +
- Look-up the JMS Queue object from JNDI +
- Look-up a JMS Connection Factory object from JNDI on server 0 +
- We create 3 JMS connections from the same connection factory. Since we are using round-robin + load-balancing this should result in each sessions being connected to a different node of the cluster +
- We create JMS Sessions +
- We create JMS MessageProducer objects on the sessions +
- We send some messages on each producer +
- We start the connection to consume messages +
- We consume messages from the 3 session, one at a time.
+ We try to consume one more message than expected from each session. If + the session were not properly load-balanced, we would be missing a + message from one of the sessions at the end.
+ - And finally (no pun intended), always remember to close your JMS resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - Get an initial context for looking up JNDI from server 0. +
- Look-up the JMS Topic object from JNDI +
- Look-up a JMS Connection Factory object from JNDI on server 0 +
- Get an initial context for looking up JNDI from server 1. +
- Look-up a JMS Connection Factory object from JNDI on server 1 +
- We create a JMS Connection connection0 which is a connection to server 0 + and set the same client-id. +
- We create a JMS Connection connection1 which is a connection to server 1 + and set the same client-id. +
- We create a JMS Session on server 0 +
- We create a JMS Session on server 1 +
- We start the connections to ensure delivery occurs on them +
- We create JMS durable subscriptions with the same name and client-id on both nodes + of the cluster + +
- We create a JMS MessageProducer object on server 0. +
- We send some messages to server 0. +
- + We now consume those messages on *both* server 0 and server 1. + Note that the messages have been load-balanced between the two nodes, with some + messages on node 0 and others on node 1. + The "logical" subscription is distributed across the cluster an contains exactly one copy of all the messages sent. + +
- And finally (no pun intended), always remember to close your JMS resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - Get an initial context for looking up JNDI from server 0. +
- Look-up the JMS Queue object from JNDI +
- Look-up a JMS Connection Factory object from JNDI on server 0 +
- Get an initial context for looking up JNDI from server 1. +
- Look-up a JMS Connection Factory object from JNDI on server 1 +
- Get an initial context for looking up JNDI from server 2. +
- Look-up a JMS Connection Factory object from JNDI on server 2 +
- We create a JMS Connection connection0 which is a connection to server 0 +
- We create a JMS Connection connection0 which is a connection to server 1 +
- We create a JMS Connection connection0 which is a connection to server 2 +
- We create a JMS Session on server 0 +
- We create a JMS Session on server 1 +
- We create a JMS Session on server 2 +
- We start the connections to ensure delivery occurs on them +
- We create JMS MessageConsumer objects on server 0 +
- We create a JMS MessageProducer object on server 0, 1 and 2 +
- We send some messages to server 0, 1 and 2 with the same groupid set +
- We now consume those messages from server 0. We note the messages have all been sent to the same consumer on the same node +
- Finally, Be sure to close our resources! +
- Get an initial context for looking up JNDI from server 0. +
- Look-up the JMS Queue object from JNDI +
- Look-up a JMS Connection Factory object from JNDI on server 0 +
- Get an initial context for looking up JNDI from server 1. +
- Look-up a JMS Connection Factory object from JNDI on server 1 +
- We create a JMS Connection connection0 which is a connection to server 0 +
- We create a JMS Connection connection1 which is a connection to server 1 +
- We create a JMS Session on server 0 +
- We create a JMS Session on server 1 +
- We start the connections to ensure delivery occurs on them +
- We create JMS MessageConsumer objects on server 0 and server 1 +
- We create a JMS MessageProducer object on server 0. +
- We send some messages to server 0. +
- We now consume those messages on *both* server 0 and server 1. + We note the messages have been distributed between servers in a round robin fashion. + HornetQ has load balanced the messages between the available consumers on the different nodes. + HornetQ can be configured to always load balance messages to all nodes, or to only balance messages + to nodes which have consumers with no or matching selectors. See the user manual for more details. + JMS Queues implement point-to-point message where each message is only ever consumed by a + maximum of one consumer. +
- And finally (no pun intended), always remember to close your JMS resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - Get an initial context for looking up JNDI from server 0. +
- Look-up the JMS Queue object from JNDI +
- Look-up a JMS Connection Factory object from JNDI on server 0 +
- Get an initial context for looking up JNDI from server 1. +
- Look-up a JMS Connection Factory object from JNDI on server 1 +
- We create a JMS Connection connection0 which is a connection to server 0 +
- We create a JMS Connection connection1 which is a connection to server 1 +
- We create a JMS Session on server 0 +
- We create a JMS Session on server 1 +
- We start the connections to ensure delivery occurs on them +
- We create JMS MessageConsumer objects on server 0 and server 1 +
- We create a JMS MessageProducer object on server 0. +
- We send some messages to server 0. +
- We now consume those messages on *both* server 0 and server 1. + We note the messages have been distributed between servers in a round robin fashion. + HornetQ has load balanced the messages between the available consumers on the different nodes. + HornetQ can be configured to always load balance messages to all nodes, or to only balance messages + to nodes which have consumers with no or matching selectors. See the user manual for more details. + JMS Queues implement point-to-point message where each message is only ever consumed by a + maximum of one consumer. +
- And finally (no pun intended), always remember to close your JMS resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - create 4 terminals (3 for the servers and 1 for the example client) +
- in the first terminal, go to the
bindirectory and start the first server (with default configuration): +
+./run.sh ../config/stand-alone/clustered - in the second terminal, start the second server:
+
+export CLUSTER_PROPS="-Ddata.dir=../data-server2 -Djnp.port=2099 -Djnp.rmiPort=2098 -Dhornetq.remoting.netty.port=6445 -Dhornetq.remoting.netty.batch.port=6455" +./run.sh ../config/stand-alone/clustered - in the third terminal, start the third server (with default configuration):
+
+export CLUSTER_PROPS="-Ddata.dir=../data-server3 -Djnp.port=3099 -Djnp.rmiPort=3098 -Dhornetq.remoting.netty.port=7445 -Dhornetq.remoting.netty.batch.port=7455" +./run.sh ../config/stand-alone/clustered - finally, in the fourth terminal, start the example
+
+./build.sh runRemote(orbuild.bat runRemoteon windows)The example connects to the three cluster nodes using JNDI (which are retrieved from + server0, server1, and + server2' s JNDI properties file). The JNDI ports were specified + using the environment property
+ +jnp.port(or 1098 by default) when starting the 3 cluster nodes.For a description of the example code, please read the + clustered-topic example which is very similar (it has 2 nodes while this example has 3 nodes). + + + \ No newline at end of file diff --git a/examples/jms/clustered-standalone/src/main/java/org/hornetq/jms/example/ClusteredStandaloneExample.java b/examples/jms/clustered-standalone/src/main/java/org/hornetq/jms/example/ClusteredStandaloneExample.java new file mode 100644 index 0000000000..d047bcaf53 --- /dev/null +++ b/examples/jms/clustered-standalone/src/main/java/org/hornetq/jms/example/ClusteredStandaloneExample.java @@ -0,0 +1,197 @@ +/* + * Copyright 2005-2014 Red Hat, Inc. + * Red Hat licenses this file to you under the Apache License, version + * 2.0 (the "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * http://www.apache.org/licenses/LICENSE-2.0 + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + * implied. See the License for the specific language governing + * permissions and limitations under the License. + */ +package org.hornetq.jms.example; + +import javax.jms.Connection; +import javax.jms.ConnectionFactory; +import javax.jms.MessageConsumer; +import javax.jms.MessageProducer; +import javax.jms.Session; +import javax.jms.TextMessage; +import javax.jms.Topic; +import javax.naming.InitialContext; + +import org.hornetq.common.example.HornetQExample; + +/** + * + * This example demonstrates a distributed topic, and needs three servers to be started before the example is run. + * + * The example will not spawn the servers itself. + * + * The servers should be started using ./run.sh ../config/stand-alone/clustered + * + * If running on the same physical box, make sure that each server: + * + * a) uses a different data directory + * b) uses different ports for the netty acceptor + * c) uses different ports for JNDI + * + * Update server[0|1|2]/client-jndi.properties to the correct ports and hosts for the 3 servers + * + * @author Tim Fox + * + * + */ +public class ClusteredStandaloneExample extends HornetQExample +{ + public static void main(final String[] args) + { + new ClusteredStandaloneExample().run(args); + } + + @Override + public boolean runExample() throws Exception + { + Connection connection0 = null; + + Connection connection1 = null; + + Connection connection2 = null; + + InitialContext initialContext0 = null; + InitialContext initialContext1 = null; + InitialContext initialContext2 = null; + + try + { + initialContext0 = getContext(0); + + initialContext1 = getContext(1); + + initialContext2 = getContext(2); + + // First we demonstrate a distributed topic. + // We create a connection on each node, create a consumer on each connection and send some + // messages at a node and verify they are all received by all consumers + + ConnectionFactory cf0 = (ConnectionFactory)initialContext0.lookup("/ConnectionFactory"); + + System.out.println("Got cf " + cf0); + + ConnectionFactory cf1 = (ConnectionFactory)initialContext1.lookup("/ConnectionFactory"); + + System.out.println("Got cf " + cf1); + + ConnectionFactory cf2 = (ConnectionFactory)initialContext2.lookup("/ConnectionFactory"); + + System.out.println("Got cf " + cf2); + + Topic topic = (Topic)initialContext0.lookup("/topic/ExampleTopic"); + + connection0 = cf0.createConnection(); + + connection1 = cf1.createConnection(); + + connection2 = cf2.createConnection(); + + connection0.start(); + + connection1.start(); + + connection2.start(); + + Session session0 = connection0.createSession(false, Session.AUTO_ACKNOWLEDGE); + + Session session1 = connection1.createSession(false, Session.AUTO_ACKNOWLEDGE); + + Session session2 = connection2.createSession(false, Session.AUTO_ACKNOWLEDGE); + + MessageConsumer messageConsumer0 = session0.createConsumer(topic); + + MessageConsumer messageConsumer1 = session1.createConsumer(topic); + + MessageConsumer messageConsumer2 = session2.createConsumer(topic); + + MessageProducer producer = session0.createProducer(topic); + + final int numMessages = 10; + + for (int i = 0; i < numMessages; i++) + { + TextMessage message = session0.createTextMessage("Message " + i); + + producer.send(message); + } + + for (int i = 0; i < numMessages; i++) + { + TextMessage message0 = (TextMessage)messageConsumer0.receive(2000); + + if (message0 == null) + { + return false; + } + + // System.out.println("Received message " + message0.getText()); + + TextMessage message1 = (TextMessage)messageConsumer1.receive(2000); + + if (message1 == null) + { + return false; + } + + // System.out.println("Received message " + message1.getText()); + + TextMessage message2 = (TextMessage)messageConsumer2.receive(2000); + + if (message2 == null) + { + return false; + } + + // System.out.println("Received message " + message2.getText()); + } + + producer.close(); + + messageConsumer0.close(); + + messageConsumer1.close(); + + messageConsumer2.close(); + + return true; + } + finally + { + // Step 12. Be sure to close our JMS resources! + if (initialContext0 != null) + { + initialContext0.close(); + } + if (initialContext1 != null) + { + initialContext1.close(); + } + if (initialContext2 != null) + { + initialContext2.close(); + } + if (connection0 != null) + { + connection0.close(); + } + if (connection1 != null) + { + connection1.close(); + } + if (connection2 != null) + { + connection2.close(); + } + } + } + +} diff --git a/examples/jms/clustered-standalone/src/main/resources/hornetq/server0/hornetq-configuration.xml b/examples/jms/clustered-standalone/src/main/resources/hornetq/server0/hornetq-configuration.xml new file mode 100644 index 0000000000..65473c94e3 --- /dev/null +++ b/examples/jms/clustered-standalone/src/main/resources/hornetq/server0/hornetq-configuration.xml @@ -0,0 +1,74 @@ +
++ + + diff --git a/examples/jms/clustered-standalone/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/clustered-standalone/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..3223b6846e --- /dev/null +++ b/examples/jms/clustered-standalone/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,19 @@ +target/server0/data/messaging/bindings + +target/server0/data/messaging/journal + +target/server0/data/messaging/largemessages + +target/server0/data/messaging/paging + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + ++ +${udp-address:231.7.7.7} +9876 +100 +netty-connector ++ + ++ +${udp-address:231.7.7.7} +9876 +10000 ++ + + + ++ jms + +netty-connector +500 +true +true +1 ++ + + + ++ ++ + + + + + + + diff --git a/examples/jms/clustered-standalone/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/clustered-standalone/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/clustered-standalone/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/clustered-standalone/src/main/resources/hornetq/server1/hornetq-configuration.xml b/examples/jms/clustered-standalone/src/main/resources/hornetq/server1/hornetq-configuration.xml new file mode 100644 index 0000000000..90742a9a41 --- /dev/null +++ b/examples/jms/clustered-standalone/src/main/resources/hornetq/server1/hornetq-configuration.xml @@ -0,0 +1,75 @@ ++ ++ + + + + diff --git a/examples/jms/clustered-standalone/src/main/resources/hornetq/server1/hornetq-jms.xml b/examples/jms/clustered-standalone/src/main/resources/hornetq/server1/hornetq-jms.xml new file mode 100644 index 0000000000..3223b6846e --- /dev/null +++ b/examples/jms/clustered-standalone/src/main/resources/hornetq/server1/hornetq-jms.xml @@ -0,0 +1,19 @@ +target/server1/data/messaging/bindings + +target/server1/data/messaging/journal + +target/server1/data/messaging/largemessages + +target/server1/data/messaging/paging + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + ++ +${udp-address:231.7.7.7} +9876 +100 +netty-connector ++ + ++ +${udp-address:231.7.7.7} +9876 +10000 ++ + + + ++ jms + +netty-connector +500 +true +true +1 ++ + + + ++ ++ + + + + + + + diff --git a/examples/jms/clustered-standalone/src/main/resources/hornetq/server1/hornetq-users.xml b/examples/jms/clustered-standalone/src/main/resources/hornetq/server1/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/clustered-standalone/src/main/resources/hornetq/server1/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/clustered-standalone/src/main/resources/hornetq/server2/hornetq-configuration.xml b/examples/jms/clustered-standalone/src/main/resources/hornetq/server2/hornetq-configuration.xml new file mode 100644 index 0000000000..641c9e0e9c --- /dev/null +++ b/examples/jms/clustered-standalone/src/main/resources/hornetq/server2/hornetq-configuration.xml @@ -0,0 +1,75 @@ ++ ++ + + + + diff --git a/examples/jms/clustered-standalone/src/main/resources/hornetq/server2/hornetq-jms.xml b/examples/jms/clustered-standalone/src/main/resources/hornetq/server2/hornetq-jms.xml new file mode 100644 index 0000000000..3223b6846e --- /dev/null +++ b/examples/jms/clustered-standalone/src/main/resources/hornetq/server2/hornetq-jms.xml @@ -0,0 +1,19 @@ +target/server2/data/messaging/bindings + +target/server2/data/messaging/journal + +target/server2/data/messaging/largemessages + +target/server2/data/messaging/paging + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + ++ +${udp-address:231.7.7.7} +9876 +100 +netty-connector ++ + ++ +${udp-address:231.7.7.7} +9876 +10000 ++ + + + ++ jms + +netty-connector +500 +true +true +1 ++ + + + ++ ++ + + + + + + + diff --git a/examples/jms/clustered-standalone/src/main/resources/hornetq/server2/hornetq-users.xml b/examples/jms/clustered-standalone/src/main/resources/hornetq/server2/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/clustered-standalone/src/main/resources/hornetq/server2/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/pom.xml b/examples/jms/clustered-static-discovery/pom.xml new file mode 100644 index 0000000000..3ca61c7dd6 --- /dev/null +++ b/examples/jms/clustered-static-discovery/pom.xml @@ -0,0 +1,191 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/readme.html b/examples/jms/clustered-static-discovery/readme.html new file mode 100644 index 0000000000..96ef23ca14 --- /dev/null +++ b/examples/jms/clustered-static-discovery/readme.html @@ -0,0 +1,180 @@ + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-clustered-static-discovery-example +jar +HornetQ JMS Clustered Static Discovery Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start0 ++ +start ++ +${basedir}/target/classes/hornetq/server0 ++ +start1 ++ +start ++ +1199 +1198 +${basedir}/target/classes/hornetq/server1 +true ++ +start2 ++ +start ++ +1299 +1298 +${basedir}/target/classes/hornetq/server2 +true ++ +start3 ++ +start ++ +1399 +1398 +${basedir}/target/classes/hornetq/server3 +true ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.StaticClusteredQueueExample ++ jnp://localhost:1099 + jnp://localhost:1199 + jnp://localhost:1299 + jnp://localhost:1399 + ++ ++ +exampleConfigDir +${basedir}/target/classes/hornetq ++ +stop0 ++ +stop ++ +${basedir}/target/classes/hornetq/server0 ++ +stop1 ++ +stop ++ +${basedir}/target/classes/hornetq/server1 ++ +stop2 ++ +stop ++ +${basedir}/target/classes/hornetq/server2 ++ +stop3 ++ +stop ++ +${basedir}/target/classes/hornetq/server3 ++ ++ +org.hornetq.examples.jms +hornetq-jms-clustered-static-discovery-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false ++ ++ +build.directory +${basedir}/target/ +HornetQ JMS Load Balanced Static Clustered Queue Example + + + + + +JMS Load Balanced Static Clustered Queue Example
+ +This example demonstrates a JMS queue deployed on two different nodes. The two nodes are configured to form a cluster + from a static list of nodes.
+We then create a consumer on the queue on each node, and we create a producer on only one of the nodes.
+We then send some messages via the producer, and we verify that both consumers receive the sent messages + in a round-robin fashion.
+In other words, HornetQ load balances the sent messages across all consumers on the cluster
+This example uses JNDI to lookup the JMS Queue and ConnectionFactory objects. If you prefer not to use + JNDI, these could be instantiated directly.
+Here's the relevant snippet from the server configuration, which tells the server to form a cluster between the two nodes + and to load balance the messages between the nodes.
++
+<cluster-connection name="my-cluster"> + <address>jms</address> + <connector-ref>netty-connector</connector-ref> + <retry-interval>500</retry-interval> + <use-duplicate-detection>true</use-duplicate-detection> + <forward-when-no-consumers>true</forward-when-no-consumers> + <max-hops>1</max-hops> + <static-connectors> + <connector-ref>server1-connector</connector-ref> + </static-connectors> + </cluster-connection> ++For more information on HornetQ load balancing, and clustering in general, please see the clustering + section of the user manual.
+Example step-by-step
+To run the example, simply type
+ +mvn verifyfrom this directory-
+
- Get an initial context for looking up JNDI from server 0. +
- Look-up the JMS Queue object from JNDI +
- Look-up a JMS Connection Factory object from JNDI on server 0 +
- Get an initial context for looking up JNDI from server 1. +
- Look-up a JMS Connection Factory object from JNDI on server 1 +
- We create a JMS Connection connection0 which is a connection to server 0 +
- We create a JMS Connection connection1 which is a connection to server 1 +
- We create a JMS Session on server 0 +
- We create a JMS Session on server 1 +
- We start the connections to ensure delivery occurs on them +
- We create JMS MessageConsumer objects on server 0 and server 1 +
- We create a JMS MessageProducer object on server 0. +
- We send some messages to server 0. +
- We now consume those messages on *both* server 0 and server 1. + We note the messages have been distributed between servers in a round robin fashion. + HornetQ has load balanced the messages between the available consumers on the different nodes. + HornetQ can be configured to always load balance messages to all nodes, or to only balance messages + to nodes which have consumers with no or matching selectors. See the user manual for more details. + JMS Queues implement point-to-point message where each message is only ever consumed by a + maximum of one consumer. +
- And finally (no pun intended), always remember to close your JMS resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+
+ ++ ic0 = getContext(0); +++
+ +Queue queue = (Queue)ic0.lookup("/queue/exampleQueue");++
+ +ConnectionFactory cf0 = (ConnectionFactory)ic0.lookup("/ConnectionFactory");++
+ +ic1 = getContext(1);++
+ +ConnectionFactory cf1 = (ConnectionFactory)ic1.lookup("/ConnectionFactory"); +++
+ ++ connection0 = cf0.createConnection(); +++
+ ++ connection1 = cf1.createConnection(); +++
+ ++ Session session0 = connection0.createSession(false, Session.AUTO_ACKNOWLEDGE); +++
+ ++ Session session1 = connection1.createSession(false, Session.AUTO_ACKNOWLEDGE); +++
+ ++ connection0.start(); + + connection1.start(); +++
+ ++ MessageConsumer consumer0 = session0.createConsumer(queue); + + MessageConsumer consumer1 = session1.createConsumer(queue); +++
+ ++ MessageProducer producer = session0.createProducer(queue);++
+ ++ final int numMessages = 10; + + for (int i = 0; i < numMessages; i++) + { + TextMessage message = session0.createTextMessage("This is text message " + i); + + producer.send(message); + + System.out.println("Sent message: " + message.getText()); + } +++
+ ++ for (int i = 0; i < numMessages; i += 2) + { + TextMessage message0 = (TextMessage)consumer0.receive(5000); + + System.out.println("Got message: " + message0.getText() + " from node 0"); + + TextMessage message1 = (TextMessage)consumer1.receive(5000); + + System.out.println("Got message: " + message1.getText() + " from node 1"); + } +++
+ ++ finally + { + if (connection0 != null) + { + connection0.close(); + } + + if (connection1 != null) + { + connection1.close(); + } + } +++ + + \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..6156e3c2fd --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,31 @@ +${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + + ++ + + ++ + +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + + + ++ jms + +netty-connector +500 +true +true +1 ++ +server1-connector ++ + + ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + + ++ true + +1000 + + +1.0 + + +-1 ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server0/jndi.properties b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server0/jndi.properties new file mode 100644 index 0000000000..e2a9832f8e --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server0/jndi.properties @@ -0,0 +1,2 @@ +java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory +java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server1/hornetq-configuration.xml b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server1/hornetq-configuration.xml new file mode 100644 index 0000000000..73cc56eaf8 --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server1/hornetq-configuration.xml @@ -0,0 +1,64 @@ ++ ++ + + + diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server1/hornetq-jms.xml b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server1/hornetq-jms.xml new file mode 100644 index 0000000000..6156e3c2fd --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server1/hornetq-jms.xml @@ -0,0 +1,31 @@ +${build.directory}/server1/data/messaging/bindings + +${build.directory}/server1/data/messaging/journal + +${build.directory}/server1/data/messaging/largemessages + +${build.directory}/server1/data/messaging/paging + + ++ + + ++ + +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + + + ++ jms + +netty-connector +500 +true +true +1 ++ +server0-connector ++ + + ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server1/hornetq-users.xml b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server1/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server1/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + + ++ true + +1000 + + +1.0 + + +-1 ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server1/jndi.properties b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server1/jndi.properties new file mode 100644 index 0000000000..e2a9832f8e --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server1/jndi.properties @@ -0,0 +1,2 @@ +java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory +java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server2/hornetq-configuration.xml b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server2/hornetq-configuration.xml new file mode 100644 index 0000000000..283121a90f --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server2/hornetq-configuration.xml @@ -0,0 +1,77 @@ + + ++ ++ + + + diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server2/hornetq-jms.xml b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server2/hornetq-jms.xml new file mode 100644 index 0000000000..abd44d82ea --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server2/hornetq-jms.xml @@ -0,0 +1,45 @@ + + +${build.directory}/server2/data/messaging/bindings + +${build.directory}/server2/data/messaging/journal + +${build.directory}/server2/data/messaging/largemessages + +${build.directory}/server2/data/messaging/paging + + ++ + + ++ + +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + + + ++ jms + +netty-connector +500 +true +true +1 ++ +server0-connector ++ + + ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server2/hornetq-users.xml b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server2/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server2/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + + ++ true + +1000 + + +1.0 + + +-1 + ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server2/jndi.properties b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server2/jndi.properties new file mode 100644 index 0000000000..629072e931 --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server2/jndi.properties @@ -0,0 +1,15 @@ +# +# Copyright 2009 Red Hat, Inc. +# Red Hat licenses this file to you under the Apache License, version +# 2.0 (the "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# http://www.apache.org/licenses/LICENSE-2.0 +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or +# implied. See the License for the specific language governing +# permissions and limitations under the License. +# + +java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory +java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server3/hornetq-configuration.xml b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server3/hornetq-configuration.xml new file mode 100644 index 0000000000..78503b493a --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server3/hornetq-configuration.xml @@ -0,0 +1,77 @@ + + ++ ++ + + + diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server3/hornetq-jms.xml b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server3/hornetq-jms.xml new file mode 100644 index 0000000000..abd44d82ea --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server3/hornetq-jms.xml @@ -0,0 +1,45 @@ + + +${build.directory}/server3/data/messaging/bindings + +${build.directory}/server3/data/messaging/journal + +${build.directory}/server3/data/messaging/largemessages + +${build.directory}/server3/data/messaging/paging + + ++ + + ++ + +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + + + ++ jms + +netty-connector +500 +true +true +1 ++ +server0-connector ++ + + ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server3/hornetq-users.xml b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server3/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server3/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + + ++ true + +1000 + + +1.0 + + +-1 + ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server3/jndi.properties b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server3/jndi.properties new file mode 100644 index 0000000000..e2a9832f8e --- /dev/null +++ b/examples/jms/clustered-static-discovery/src/main/resources/hornetq/server3/jndi.properties @@ -0,0 +1,2 @@ +java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory +java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces \ No newline at end of file diff --git a/examples/jms/clustered-static-oneway/pom.xml b/examples/jms/clustered-static-oneway/pom.xml new file mode 100644 index 0000000000..4ed9488357 --- /dev/null +++ b/examples/jms/clustered-static-oneway/pom.xml @@ -0,0 +1,169 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/clustered-static-oneway/readme.html b/examples/jms/clustered-static-oneway/readme.html new file mode 100644 index 0000000000..73726212d5 --- /dev/null +++ b/examples/jms/clustered-static-oneway/readme.html @@ -0,0 +1,229 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-clustered-static-oneway-example +jar +HornetQ JMS Clustered Static One Way Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start0 ++ +start ++ +${basedir}/target/classes/hornetq/server0 ++ +start1 ++ +start ++ +1199 +1198 +${basedir}/target/classes/hornetq/server1 +true ++ +start2 ++ +start ++ +1299 +1298 +${basedir}/target/classes/hornetq/server2 +true ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.ClusterStaticOnewayExample ++ jnp://localhost:1099 + jnp://localhost:1199 + jnp://localhost:1299 + ++ ++ +exampleConfigDir +${basedir}/target/classes/hornetq ++ +stop0 ++ +stop ++ +${basedir}/target/classes/hornetq/server0 ++ +stop1 ++ +stop ++ +${basedir}/target/classes/hornetq/server1 ++ +stop2 ++ +stop ++ +${basedir}/target/classes/hornetq/server2 ++ ++ +org.hornetq.examples.jms +hornetq-jms-clustered-static-oneway-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false ++ ++ +build.directory +${basedir}/target/ +HornetQ JMS Load Balanced Static Clustered Queue Example + + + + + +JMS Load Balanced Static Clustered One Way Queue Example
+ +This example demonstrates a JMS queue deployed on three different nodes. The three nodes are configured to form a one way cluster + from a static list of nodes.
+A one way cluster is different from a symmetrical cluster in that each node is only connected to one another node in + a chain type fashion, so server 0 -> server 1 -> server 2
+We then create a consumer on the queue on each node, and we create a producer on only one of the nodes.
+We then send some messages via the producer, and we verify that all consumers receive the sent messages + in a round-robin fashion.
+In other words, HornetQ load balances the sent messages across all consumers on the cluster
+This example uses JNDI to lookup the JMS Queue and ConnectionFactory objects. If you prefer not to use + JNDI, these could be instantiated directly.
+Here's the relevant snippet from the server configuration, which tells the server to form a one way cluster between the three nodes + and to load balance the messages between the nodes. Note that we have set allow-direct-connections-only to true, + this means that this server will only ever connect the address's specified in the list of connectors. ALso notice + that max-hops is 2, this is because server 0 is not directly connected to server 2, 2 hops in fact, so we + allow any updates from servers up to 2 hops away
++
++ <cluster-connection name="my-cluster"> + <address>jms</address> + <connector-ref>netty-connector</connector-ref> + <retry-interval>500</retry-interval> + <use-duplicate-detection>true</use-duplicate-detection> + <forward-when-no-consumers>true</forward-when-no-consumers> + <max-hops>2</max-hops> + <static-connectors allow-direct-connections-only="true"> + <connector-ref>server1-connector</connector-ref> + </static-connectors> + </cluster-connection> ++For more information on HornetQ load balancing, and clustering in general, please see the clustering + section of the user manual.
+Example step-by-step
+To run the example, simply type
+ +mvn verifyfrom this directory-
+
- Get an initial context for looking up JNDI from server 0. +
- Look-up the JMS Queue object from JNDI +
- Look-up a JMS Connection Factory object from JNDI on server 0 +
- grab an initial connection and wait, in reality you wouldn't do it this way but since we want to ensure an + equal load balance we do this and then create 4 connections round robined +
- We create a JMS Connection connection0 which is a connection to server 0 +
- We create a JMS Connection connection0 which is a connection to server 1 +
- We create a JMS Connection connection0 which is a connection to server 2 +
- We create a JMS Session on server 0 +
- We create a JMS Session on server 1 +
- We create a JMS Session on server 1 +
- We start the connections to ensure delivery occurs on them +
- We create JMS MessageConsumer objects on server 0 and server 1 +
- We create a JMS MessageProducer object on server 0. +
- We send some messages to server 0. +
- We now consume those messages on *both* server 0 and server 1. + We note the messages have been distributed between servers in a round robin fashion. + HornetQ has load balanced the messages between the available consumers on the different nodes. + HornetQ can be configured to always load balance messages to all nodes, or to only balance messages + to nodes which have consumers with no or matching selectors. See the user manual for more details. + JMS Queues implement point-to-point message where each message is only ever consumed by a + maximum of one consumer. +
- And finally (no pun intended), always remember to close your JMS resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+
+ ++ ic0 = getContext(0); +++
+ ++ Queue queue = (Queue)ic0.lookup("/queue/exampleQueue"); +++
+ + ++ ConnectionFactory cf0 = (ConnectionFactory)ic0.lookup("/ConnectionFactory"); +++
+ ++ initialConnection = cf0.createConnection(); +++
+ ++ connection0 = cf0.createConnection() +++
+ ++ connection1 = cf0.createConnection() +++
+ ++ connection2 = cf0.createConnection() +++
+ ++ Session session0 = connection0.createSession(false, Session.AUTO_ACKNOWLEDGE); +++
+ ++ Session session1 = connection1.createSession(false, Session.AUTO_ACKNOWLEDGE); +++
++ Session session2 = connection2.createSession(false, Session.AUTO_ACKNOWLEDGE); +++
+ + ++ connection0.start(); + + connection1.start(); + + connection2.start(); +++
+ + ++ MessageConsumer consumer0 = session0.createConsumer(queue); + + MessageConsumer consumer2 = session2.createConsumer(queue); + + MessageConsumer consumer3 = session3.createConsumer(queue); +++
+ ++ Session sendSession = getServerConnection(0, connection0, connection1, connection2).createSession(false, Session.AUTO_ACKNOWLEDGE); + + MessageProducer producer = sendSession.createProducer(queue); +++
+ ++ final int numMessages = 18; + + for (int i = 0; i < numMessages; i++) + { + TextMessage message = session0.createTextMessage("This is text message " + i); + + producer.send(message); + + System.out.println("Sent message: " + message.getText()); + } +++
+ ++ for (int i = 0; i < numMessages; i += 2) + { + TextMessage message0 = (TextMessage)consumer0.receive(5000); + + System.out.println("Got message: " + message0.getText() + " from node 0"); + + TextMessage message1 = (TextMessage)consumer1.receive(5000); + + System.out.println("Got message: " + message1.getText() + " from node 1"); + + TextMessage message2 = (TextMessage)consumer2.receive(5000); + + System.out.println("Got message: " + message2.getText() + " from node " + con2Node); + } +++
+ ++ finally + { + if (initialConnection != null) + { + initialConnection.close(); + } + + if (connection0 != null) + { + connection0.close(); + } + + if (connection1 != null) + { + connection1.close(); + } + + if (connection2 != null) + { + connection2.close(); + } + + if (ic0 != null) + { + ic0.close(); + } + } +++ + + \ No newline at end of file diff --git a/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..6156e3c2fd --- /dev/null +++ b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,31 @@ +${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + + ++ + + ++ + +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + + + ++ jms + +netty-connector +500 +true +true +2 ++ +server1-connector ++ + + ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + + ++ true + +1000 + + +1.0 + + +-1 ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server0/jndi.properties b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server0/jndi.properties new file mode 100644 index 0000000000..e2a9832f8e --- /dev/null +++ b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server0/jndi.properties @@ -0,0 +1,2 @@ +java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory +java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces \ No newline at end of file diff --git a/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server1/hornetq-configuration.xml b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server1/hornetq-configuration.xml new file mode 100644 index 0000000000..2109cf2fb5 --- /dev/null +++ b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server1/hornetq-configuration.xml @@ -0,0 +1,77 @@ + + ++ ++ + + + diff --git a/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server1/hornetq-jms.xml b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server1/hornetq-jms.xml new file mode 100644 index 0000000000..6156e3c2fd --- /dev/null +++ b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server1/hornetq-jms.xml @@ -0,0 +1,31 @@ +${build.directory}/server1/data/messaging/bindings + +${build.directory}/server1/data/messaging/journal + +${build.directory}/server1/data/messaging/largemessages + +${build.directory}/server1/data/messaging/paging + + ++ + + ++ + +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + + + ++ jms + +netty-connector +500 +true +true +2 ++ +server2-connector ++ + + ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server1/hornetq-users.xml b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server1/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server1/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + + ++ true + +1000 + + +1.0 + + +-1 ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server1/jndi.properties b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server1/jndi.properties new file mode 100644 index 0000000000..e2a9832f8e --- /dev/null +++ b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server1/jndi.properties @@ -0,0 +1,2 @@ +java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory +java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces \ No newline at end of file diff --git a/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server2/hornetq-configuration.xml b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server2/hornetq-configuration.xml new file mode 100644 index 0000000000..45d703fc84 --- /dev/null +++ b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server2/hornetq-configuration.xml @@ -0,0 +1,69 @@ + + ++ ++ + + + diff --git a/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server2/hornetq-jms.xml b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server2/hornetq-jms.xml new file mode 100644 index 0000000000..abd44d82ea --- /dev/null +++ b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server2/hornetq-jms.xml @@ -0,0 +1,45 @@ + + +${build.directory}/server2/data/messaging/bindings + +${build.directory}/server2/data/messaging/journal + +${build.directory}/server2/data/messaging/largemessages + +${build.directory}/server2/data/messaging/paging + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + + + ++ jms + +netty-connector +500 +true +true +2 ++ + + ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server2/hornetq-users.xml b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server2/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server2/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + + ++ true + +1000 + + +1.0 + + +-1 + ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server2/jndi.properties b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server2/jndi.properties new file mode 100644 index 0000000000..629072e931 --- /dev/null +++ b/examples/jms/clustered-static-oneway/src/main/resources/hornetq/server2/jndi.properties @@ -0,0 +1,15 @@ +# +# Copyright 2009 Red Hat, Inc. +# Red Hat licenses this file to you under the Apache License, version +# 2.0 (the "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# http://www.apache.org/licenses/LICENSE-2.0 +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or +# implied. See the License for the specific language governing +# permissions and limitations under the License. +# + +java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory +java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces \ No newline at end of file diff --git a/examples/jms/clustered-topic/pom.xml b/examples/jms/clustered-topic/pom.xml new file mode 100644 index 0000000000..d5e71a7e8e --- /dev/null +++ b/examples/jms/clustered-topic/pom.xml @@ -0,0 +1,167 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/clustered-topic/readme.html b/examples/jms/clustered-topic/readme.html new file mode 100644 index 0000000000..38c652140c --- /dev/null +++ b/examples/jms/clustered-topic/readme.html @@ -0,0 +1,174 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-clustered-topic-example +jar +HornetQ JMS Clustered Topic Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start0 ++ +start ++ +${basedir}/target/classes/hornetq/server0 ++ ++ +build.directory +${basedir}/target/ ++ +udp-address +${udp-address} ++ +start1 ++ +start ++ +1199 +1198 +${basedir}/target/classes/hornetq/server1 +true ++ ++ +build.directory +${basedir}/target/ ++ +udp-address +${udp-address} ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.ClusteredTopicExample ++ jnp://localhost:1099 + jnp://localhost:1199 + ++ ++ +exampleConfigDir +${basedir}/target/classes/hornetq ++ +stop0 ++ +stop ++ +${basedir}/target/classes/hornetq/server0 ++ +stop1 ++ +stop ++ +${basedir}/target/classes/hornetq/server1 ++ ++ +org.hornetq.examples.jms +hornetq-jms-clustered-topic-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false ++ ++ +build.directory +${basedir}/target/ +HornetQ JMS Clustered Topic Example + + + + + +JMS Clustered Topic Example
+ +This example demonstrates a JMS Topic deployed on two different nodes. The two nodes are configured to form a cluster.
+We then create a subscriber on the topic on each node, and we create a producer on only one of the nodes.
+We then send some messages via the producer, and we verify that both subscribers receive all the + sent messages.
+A JMS Topic is an example of publish-subscribe messaging where all subscribers receive all the + messages sent to the topic (assuming they have no message selectors).
+This example uses JNDI to lookup the JMS Queue and ConnectionFactory objects. If you prefer not to use + JNDI, these could be instantiated directly. +
Here's the relevant snippet from the server configuration, which tells the server to form a cluster between the two nodes + and to load balance the messages between the nodes.
++
+<cluster-connection name="my-cluster"> + <address>jms</address> + <retry-interval>500</retry-interval> + <use-duplicate-detection>true</use-duplicate-detection> + <forward-when-no-consumers>true</forward-when-no-consumers> + <max-hops>1</max-hops> + <discovery-group-ref discovery-group-name="my-discovery-group"/> + </cluster-connection> ++For more information on HornetQ load balancing, and clustering in general, please see the clustering + section of the user manual.
+Example step-by-step
+To run the example, simply type
+ +mvn verifyfrom this directory-
+
- Get an initial context for looking up JNDI from server 0. +
- Look-up the JMS Topic object from JNDI +
- Look-up a JMS Connection Factory object from JNDI on server 0 +
- Get an initial context for looking up JNDI from server 1. +
- Look-up a JMS Connection Factory object from JNDI on server 1 +
- We create a JMS Connection connection0 which is a connection to server 0 +
- We create a JMS Connection connection1 which is a connection to server 1 +
- We create a JMS Session on server 0 +
- We create a JMS Session on server 1 +
- We start the connections to ensure delivery occurs on them +
- We create JMS MessageConsumer (Topic subscriber) objects on server 0 and server 1 +
- We create a JMS MessageProducer object on server 0. +
- We send some messages to server 0. +
-
+ We now consume those messages on both server 0 and server 1.
+ We note that all messages have been consumed by both consumers.
+ JMS Topics implement publish-subscribe messaging where all consumers get a copy of all messages.
+
+
+ ++ for (int i = 0; i < numMessages; i ++) + { + TextMessage message0 = (TextMessage)consumer0.receive(5000); + + System.out.println("Got message: " + message0.getText() + " from node 0"); + + TextMessage message1 = (TextMessage)consumer1.receive(5000); + + System.out.println("Got message: " + message1.getText() + " from node 1"); + } ++ - And finally (no pun intended), always remember to close your JMS resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+
+ ++ ic0 = getContext(0); +++
+ +Topic topic = (Topic)ic0.lookup("/topic/exampleTopic");++
+ +ConnectionFactory cf0 = (ConnectionFactory)ic0.lookup("/ConnectionFactory");++
+ +ic1 = getContext(1);++
+ +ConnectionFactory cf1 = (ConnectionFactory)ic1.lookup("/ConnectionFactory"); +++
+ ++ connection0 = cf0.createConnection(); +++
+ ++ connection1 = cf1.createConnection(); +++
+ ++ Session session0 = connection0.createSession(false, Session.AUTO_ACKNOWLEDGE); +++
+ ++ Session session1 = connection1.createSession(false, Session.AUTO_ACKNOWLEDGE); +++
+ ++ connection0.start(); + + connection1.start(); +++
+ ++ MessageConsumer consumer0 = session0.createConsumer(topic); + + MessageConsumer consumer1 = session1.createConsumer(topic); +++
+ ++ MessageProducer producer = session0.createProducer(topic);++
+ ++ final int numMessages = 10; + + for (int i = 0; i < numMessages; i++) + { + TextMessage message = session0.createTextMessage("This is text message " + i); + + producer.send(message); + + System.out.println("Sent message: " + message.getText()); + } +++
+ ++ finally + { + if (connection0 != null) + { + connection0.close(); + } + + if (connection1 != null) + { + connection1.close(); + } + } ++${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + ++ +${udp-address:231.7.7.7} +9876 +100 +netty-connector ++ + ++ +${udp-address:231.7.7.7} +9876 +10000 ++ + + + ++ jms + +netty-connector +500 +true +true +1 ++ + + + + diff --git a/examples/jms/clustered-topic/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/clustered-topic/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..f89d475dd9 --- /dev/null +++ b/examples/jms/clustered-topic/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,19 @@ ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/clustered-topic/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/clustered-topic/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/clustered-topic/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/clustered-topic/src/main/resources/hornetq/server1/hornetq-configuration.xml b/examples/jms/clustered-topic/src/main/resources/hornetq/server1/hornetq-configuration.xml new file mode 100644 index 0000000000..7941ee44b5 --- /dev/null +++ b/examples/jms/clustered-topic/src/main/resources/hornetq/server1/hornetq-configuration.xml @@ -0,0 +1,74 @@ ++ ++ + + + \ No newline at end of file diff --git a/examples/jms/clustered-topic/src/main/resources/hornetq/server1/hornetq-jms.xml b/examples/jms/clustered-topic/src/main/resources/hornetq/server1/hornetq-jms.xml new file mode 100644 index 0000000000..f89d475dd9 --- /dev/null +++ b/examples/jms/clustered-topic/src/main/resources/hornetq/server1/hornetq-jms.xml @@ -0,0 +1,19 @@ +${build.directory}/server1/data/messaging/bindings + +${build.directory}/server1/data/messaging/journal + +${build.directory}/server1/data/messaging/largemessages + +${build.directory}/server1/data/messaging/paging + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + ++ +${udp-address:231.7.7.7} +9876 +100 +netty-connector ++ + ++ +${udp-address:231.7.7.7} +9876 +10000 ++ + + + ++ jms + +netty-connector +500 +true +true +1 ++ + + + ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/clustered-topic/src/main/resources/hornetq/server1/hornetq-users.xml b/examples/jms/clustered-topic/src/main/resources/hornetq/server1/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/clustered-topic/src/main/resources/hornetq/server1/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/colocated-failover-scale-down/pom.xml b/examples/jms/colocated-failover-scale-down/pom.xml new file mode 100644 index 0000000000..5faf069630 --- /dev/null +++ b/examples/jms/colocated-failover-scale-down/pom.xml @@ -0,0 +1,153 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/colocated-failover-scale-down/readme.html b/examples/jms/colocated-failover-scale-down/readme.html new file mode 100644 index 0000000000..f5e3909206 --- /dev/null +++ b/examples/jms/colocated-failover-scale-down/readme.html @@ -0,0 +1,160 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +colocated-failover-scale-down +jar +HornetQ JMS Colocated Failover Recover Only Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start0 ++ +start ++ +${basedir}/target/classes/hornetq/server0 ++ ++ +udp-address +${udp-address} ++ +start1 ++ +start ++ +1199 +1198 +${basedir}/target/classes/hornetq/server1 +true ++ ++ +udp-address +${udp-address} ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.ColocatedFailoverScaleDownExample ++ jnp://localhost:1099 + jnp://localhost:1199 + ++ ++ +exampleConfigDir +${basedir}/target/classes/hornetq ++ +stop0 ++ +stop ++ +${basedir}/target/classes/hornetq/server0 ++ +stop1 ++ +stop ++ +${basedir}/target/classes/hornetq/server1 ++ ++ +org.hornetq.examples.jms +colocated-failover-recover-only +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +HornetQ JMS Colocated Failover Scale Down Example + + + + + +JMS Colocated Failover Recover Only Example
+ +This example demonstrates how you can colocate live and backup servers in the same VM. We do this by creating an + HA Policy that is colocated. colocated means that backup servers can be created and maintained by live servers on behalf + of other requesting live servers. In this example we create a colocated shared store server that will scale down. + That is it will not become live but scale down the journal to the colocated live server. +
This example starts 2 live servers each with a backup server that backs up the other live server.
+The first live server will be killed and the backup in the second will recover the journal and recreate its state + in the live server it shares its VM with.
+The following shows how to configure the backup, the backup strategy is set to SCALE_DOWN which means + that the backup server will not fully start on fail over, instead it will just recover the journal and write it + to its parent live server. Also notice we have over ridden some of the configuration since we want it to use the same + journal as server1 since it is using shared store.
++
+<ha-policy template="COLOCATED_SHARED_STORE"/> ++note that for this HA policy we use a template that will use some sensibe settings, in this case this includes + setting scale down to true. Also note that since we dont specify a scale down connector it will use most appropriate + from the list of available connectors which in this case is the first INVM connector
+One other thing to notice is that the cluster connection has its reconnect attempts set to 5, this is so it will + disconnect instead of trying to reconnect to a backup that doesn't exist.
+Example step-by-step
+To run the example, simply type
+ +mvn verifyfrom this directory-
+
- Get an initial context for looking up JNDI for both servers +
- Look up the JMS resources from JNDI +
- Create a JMS Connections +
- Create a *non-transacted* JMS Session with client acknowledgement +
- Create a JMS MessageProducer +
- Send some messages to both servers +
- Crash server #0, the live server +
- start the connection ready to receive messages +
- create a consumer +
- Receive and acknowledge all of the sent messages, notice that they will be out of order, this is + because they were initially round robined to both nodes then when the server failed were reloaded into the + live server. +
- And finally (no pun intended), always remember to close your JMS resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+
+ ++ initialContext1 = getContext(1); + initialContext = getContext(0); +++
+ ++ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue"); + ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory"); + ConnectionFactory connectionFactory1 = (ConnectionFactory)initialContext1.lookup("/ConnectionFactory"); +++
+ ++ connection = connectionFactory.createConnection(); + connection1 = connectionFactory1.createConnection(); +++
+ ++ Session session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE); + Session session1 = connection1.createSession(false, Session.CLIENT_ACKNOWLEDGE); +++
+ ++ MessageProducer producer = session.createProducer(queue); + MessageProducer producer1 = session1.createProducer(queue); +++
+ ++ for (int i = 0; i < numMessages; i++) + { + TextMessage message = session.createTextMessage("This is text message " + i); + producer.send(message); + System.out.println("Sent message: " + message.getText()); + message = session1.createTextMessage("This is another text message " + i); + producer1.send(message); + System.out.println("Sent message: " + message.getText()); + } +++
+ ++ killServer(0); +++
+ ++ connection1.start(); +++
+ ++ MessageConsumer consumer = session1.createConsumer(queue); +++
+ + + + ++ TextMessage message0 = null; + for (int i = 0; i < numMessages * 2; i++) + { + message0 = (TextMessage)consumer.receive(5000); + System.out.println("Got message: " + message0.getText()); + } + message0.acknowledge(); +++
+ ++ finally + { + if (connection != null) + { + connection.close(); + } + + if (initialContext != null) + { + initialContext.close(); + } + if (connection1 != null) + { + connection1.close(); + } + + if (initialContext1 != null) + { + initialContext1.close(); + } + } ++target/server0/data/messaging/bindings + +target/server0/data/messaging/journal + +target/server0/data/messaging/largemessages + +target/server0/data/messaging/paging + + ++ + + ++ +org.hornetq.core.remoting.impl.invm.InVMConnectorFactory ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.invm.InVMAcceptorFactory ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + ++ +${udp-address:231.7.7.7} +9876 +100 +netty-connector ++ + ++ +${udp-address:231.7.7.7} +9876 +10000 ++ + + ++ jms + +netty-connector +500 + +5 +true +true +1 ++ + + + + + + + + \ No newline at end of file diff --git a/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..46e62b4f0a --- /dev/null +++ b/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,30 @@ ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ true + +1000 + + +1.0 + + +-1 ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server1/hornetq-configuration.xml b/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server1/hornetq-configuration.xml new file mode 100644 index 0000000000..2da9ca868f --- /dev/null +++ b/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server1/hornetq-configuration.xml @@ -0,0 +1,86 @@ ++ ++ + + + + diff --git a/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server1/hornetq-jms.xml b/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server1/hornetq-jms.xml new file mode 100644 index 0000000000..46e62b4f0a --- /dev/null +++ b/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server1/hornetq-jms.xml @@ -0,0 +1,30 @@ +target/server1/data/messaging/bindings + +target/server1/data/messaging/journal + +target/server1/data/messaging/largemessages + +target/server1/data/messaging/paging + + ++ + + ++ +org.hornetq.core.remoting.impl.invm.InVMConnectorFactory ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.invm.InVMAcceptorFactory ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + ++ +${udp-address:231.7.7.7} +9876 +100 +netty-connector ++ + ++ +${udp-address:231.7.7.7} +9876 +10000 ++ + + ++ jms + +netty-connector +500 + +5 +true +true +1 ++ + + + + + + + ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server1/hornetq-users.xml b/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server1/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/colocated-failover-scale-down/src/main/resources/hornetq/server1/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ true + +1000 + + +1.0 + + +-1 ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/colocated-failover/pom.xml b/examples/jms/colocated-failover/pom.xml new file mode 100644 index 0000000000..867b9b983b --- /dev/null +++ b/examples/jms/colocated-failover/pom.xml @@ -0,0 +1,153 @@ ++ ++ + diff --git a/examples/jms/colocated-failover/readme.html b/examples/jms/colocated-failover/readme.html new file mode 100644 index 0000000000..ac680f6261 --- /dev/null +++ b/examples/jms/colocated-failover/readme.html @@ -0,0 +1,164 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +colocated-failover +jar +HornetQ JMS Colocated Failover Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start0 ++ +start ++ +${basedir}/target/classes/hornetq/server0 ++ ++ +udp-address +${udp-address} ++ +start1 ++ +start ++ +1199 +1198 +${basedir}/target/classes/hornetq/server1 +true ++ ++ +udp-address +${udp-address} ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.ColocatedFailoverExample ++ jnp://localhost:1099 + jnp://localhost:1199 + ++ ++ +exampleConfigDir +${basedir}/target/classes/hornetq ++ +stop0 ++ +stop ++ +${basedir}/target/classes/hornetq/server0 ++ +stop1 ++ +stop ++ +${basedir}/target/classes/hornetq/server1 ++ ++ +org.hornetq.examples.jms +colocated-failover +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +HornetQ JMS Colocated Failover Example + + + + + +JMS Colocated Failover Shared Store Example
+ +This example demonstrates how you can colocate live and backup servers in the same VM. We do this by creating an + HA Policy that is colocated. colocated means that backup servers can be created and maintained by live servers on behalf + of other requesting live servers. In this example we create a colocated shared store server. +
This example starts 2 live servers each with a backup server that backs up the other live server.
+The first live server will be killed and the backup in the second will become live
+The following shows how to configure the live servers to request and allow backups to be deployed
++
+<ha-policy template="COLOCATED_SHARED_STORE"> + <backup-strategy>FULL</backup-strategy> + </ha-policy> ++notice that we have used a template to set some sensible defaults but overridden the backup strategy so back ups + are full servers
+Example step-by-step
+To run the example, simply type
+ +mvn verifyfrom this directory-
+
- Get an initial context for looking up JNDI for both servers +
- Look up the JMS resources from JNDI +
- Create a JMS Connections +
- Create a *non-transacted* JMS Session with client acknowledgement +
- Create a JMS MessageProducer +
- Send some messages to both servers +
- Crash server #0, the live server +
- start the connection ready to receive messages +
- create a consumer +
- Receive and acknowledge all of the sent messages, the backup server that is colocated with server 1 + will have become live and is now handling messages for server 0. +
- Receive and acknowledge the rest of the sent messages from server 1. +
- And finally (no pun intended), always remember to close your JMS resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+
+ ++ initialContext1 = getContext(1); + initialContext = getContext(0); +++
+ ++ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue"); + ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory"); + ConnectionFactory connectionFactory1 = (ConnectionFactory)initialContext1.lookup("/ConnectionFactory"); +++
+ ++ connection = connectionFactory.createConnection(); + connection1 = connectionFactory1.createConnection(); +++
+ ++ Session session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE); + Session session1 = connection1.createSession(false, Session.CLIENT_ACKNOWLEDGE); +++
+ ++ MessageProducer producer = session.createProducer(queue); + MessageProducer producer1 = session1.createProducer(queue); +++
+ ++ for (int i = 0; i < numMessages; i++) + { + TextMessage message = session.createTextMessage("This is text message " + i); + producer.send(message); + System.out.println("Sent message: " + message.getText()); + message = session1.createTextMessage("This is another text message " + i); + producer1.send(message); + System.out.println("Sent message: " + message.getText()); + } +++
+ ++ killServer(0); +++
+ ++ connection1.start(); +++
+ ++ MessageConsumer consumer = session1.createConsumer(queue); +++
+ ++ TextMessage message0 = null; + for (int i = 0; i < numMessages; i++) + { + message0 = (TextMessage)consumer.receive(5000); + System.out.println("Got message: " + message0.getText()); + } + message0.acknowledge(); +++
+ + + ++ for (int i = 0; i < numMessages; i++) + { + message0 = (TextMessage)consumer1.receive(5000); + System.out.println("Got message: " + message0.getText()); + } + message0.acknowledge(); +++
+ ++ finally + { + if (connection != null) + { + connection.close(); + } + + if (initialContext != null) + { + initialContext.close(); + } + if (connection1 != null) + { + connection1.close(); + } + + if (initialContext1 != null) + { + initialContext1.close(); + } + } +++ + + \ No newline at end of file diff --git a/examples/jms/colocated-failover/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/colocated-failover/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..46e62b4f0a --- /dev/null +++ b/examples/jms/colocated-failover/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,30 @@ +target/server0/data/messaging/bindings + +target/server0/data/messaging/journal + +target/server0/data/messaging/largemessages + +target/server0/data/messaging/paging + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + ++ +${udp-address:231.7.7.7} +9876 +100 +netty-connector ++ + ++ +${udp-address:231.7.7.7} +9876 +10000 ++ + + ++ jms + +netty-connector +500 +true +true +1 ++ + + + + +FULL ++ + + + ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/colocated-failover/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/colocated-failover/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/colocated-failover/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ true + +1000 + + +1.0 + + +-1 ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/colocated-failover/src/main/resources/hornetq/server1/hornetq-configuration.xml b/examples/jms/colocated-failover/src/main/resources/hornetq/server1/hornetq-configuration.xml new file mode 100644 index 0000000000..c301c46d86 --- /dev/null +++ b/examples/jms/colocated-failover/src/main/resources/hornetq/server1/hornetq-configuration.xml @@ -0,0 +1,80 @@ ++ ++ + + + + diff --git a/examples/jms/colocated-failover/src/main/resources/hornetq/server1/hornetq-jms.xml b/examples/jms/colocated-failover/src/main/resources/hornetq/server1/hornetq-jms.xml new file mode 100644 index 0000000000..46e62b4f0a --- /dev/null +++ b/examples/jms/colocated-failover/src/main/resources/hornetq/server1/hornetq-jms.xml @@ -0,0 +1,30 @@ +target/server1/data/messaging/bindings + +target/server1/data/messaging/journal + +target/server1/data/messaging/largemessages + +target/server1/data/messaging/paging + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + ++ +${udp-address:231.7.7.7} +9876 +100 +netty-connector ++ + ++ +${udp-address:231.7.7.7} +9876 +10000 ++ + + ++ jms + +netty-connector +500 +true +true +1 ++ + + + + +FULL ++ + + ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/colocated-failover/src/main/resources/hornetq/server1/hornetq-users.xml b/examples/jms/colocated-failover/src/main/resources/hornetq/server1/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/colocated-failover/src/main/resources/hornetq/server1/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ true + +1000 + + +1.0 + + +-1 ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/consumer-rate-limit/pom.xml b/examples/jms/consumer-rate-limit/pom.xml new file mode 100644 index 0000000000..80b0784029 --- /dev/null +++ b/examples/jms/consumer-rate-limit/pom.xml @@ -0,0 +1,116 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/consumer-rate-limit/readme.html b/examples/jms/consumer-rate-limit/readme.html new file mode 100644 index 0000000000..3b454df1d0 --- /dev/null +++ b/examples/jms/consumer-rate-limit/readme.html @@ -0,0 +1,163 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-consumer-rate-limit-example +jar +HornetQ JMS Consumer Rate Limit Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start ++ +start ++ ++ ++ +build.directory +${basedir}/target/ ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.ConsumerRateLimitExample ++ jnp://localhost:1099 + ++ +stop ++ +stop ++ ++ +org.hornetq.examples.jms +hornetq-jms-consumer-rate-limit-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +${basedir}/target/classes/hornetq/server0 +HornetQ JMS Message Consumer Rate Limiting + + + + + +JMS Message Consumer Rate Limiting
+ +With HornetQ you can specify a maximum consume rate at which a JMS MessageConsumer will consume messages. + This can be specified when creating or deploying the connection factory. See
+hornetq-jms.xmlIf this value is specified then HornetQ will ensure that messages are never consumed at a rate higher than + the specified rate. This is a form of consumer throttling.
+Example step-by-step
+In this example we specify a
+consumer-max-rateof10messages per second in thehornetq-jms.xml+ file when deploying the connection factory:+
++ <connection-factory name="ConnectionFactory"> + <connector-ref connector-name="netty-connector"/> + <entries> + <entry name="ConnectionFactory"/> + </entries> + + <!-- We limit consumers created on this connection factory to consume messages at a maximum rate + of 10 messages per sec --> + <consumer-max-rate>50</producer-max-rate> + + </connection-factory> ++We then simply consume as many messages as we can in 10 seconds and note how many messages are actually consumed.
+We note that the number of messages consumed per second never exceeds the specified value of
+ +10messages per second.To run the example, simply type
+ +mvn verifyfrom this directory-
+
- Create an initial context to perform the JNDI lookup. +
- Perfom a lookup on the queue +
- Perform a lookup on the Connection Factory +
- Create a JMS Connection +
- Create a JMS Session +
- Create a JMS MessageProducer +
- Create a JMS MessageConsumer +
- Start the connection + +
- Send a bunch of messages +
- Consume as many messages as we can in 10 seconds + +
- This should produce output something like: + +
- Be sure to close our resources! + +
+
+ +initialContext = getContext(0);++
+ +Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");++
+ +ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");++
+ +connection = cf.createConnection();++
+ +Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);++
+ +MessageProducer producer = session.createProducer(queue);++
+ +MessageConsumer consumer = session.createConsumer(queue);++
+ + ++ connection.start(); +++
+ ++ final int numMessages = 150; + + for (int i = 0; i < numMessages; i++) + { + TextMessage message = session.createTextMessage("This is text message: " + i); + + producer.send(message); + } +++
+ ++ final long duration = 10000; + + int i = 0; + + long start = System.currentTimeMillis(); + + while (System.currentTimeMillis() - start <= duration) + { + TextMessage message = (TextMessage)consumer.receive(2000); + + if (message == null) + { + return false; + } + + i++; + } + + long end = System.currentTimeMillis(); + + double rate = 1000 * (double)i / (end - start); + + System.out.println("We consumed " + i + " messages in " + (end - start) + " milliseconds"); + + System.out.println("Actual consume rate was " + rate + " messages per second"); +++
+ ++ [java] Sent messages + [java] Will now try and consume as many as we can in 10 seconds ... + [java] We consumed 100 messages in 10001 milliseconds + [java] Actual consume rate was 9.99900009999 messages per second + +++
+ + + ++ finally + { + if (initialContext != null) + { + initialContext.close(); + } + + if (connection != null) + { + connection.close(); + } + }++ + diff --git a/examples/jms/consumer-rate-limit/src/main/resources/hornetq/server0/hornetq-configuration.xml b/examples/jms/consumer-rate-limit/src/main/resources/hornetq/server0/hornetq-configuration.xml new file mode 100644 index 0000000000..6307c0e930 --- /dev/null +++ b/examples/jms/consumer-rate-limit/src/main/resources/hornetq/server0/hornetq-configuration.xml @@ -0,0 +1,42 @@ ++ + + + + + ++ ++ 1099 +localhost +1098 +localhost ++ + + ++ + + + + + + ++ + + + + ++ ++ ++ + ++ + ++ + + + + ++ ++ ++ + + diff --git a/examples/jms/consumer-rate-limit/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/consumer-rate-limit/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..a841d0b369 --- /dev/null +++ b/examples/jms/consumer-rate-limit/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,24 @@ +${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory ++ + + ++ ++ + + + + + + + diff --git a/examples/jms/consumer-rate-limit/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/consumer-rate-limit/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/consumer-rate-limit/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + + + ++ 10 + ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/dead-letter/pom.xml b/examples/jms/dead-letter/pom.xml new file mode 100644 index 0000000000..348199ea59 --- /dev/null +++ b/examples/jms/dead-letter/pom.xml @@ -0,0 +1,116 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/dead-letter/readme.html b/examples/jms/dead-letter/readme.html new file mode 100644 index 0000000000..5856c58eb5 --- /dev/null +++ b/examples/jms/dead-letter/readme.html @@ -0,0 +1,207 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-dead-letter-example +jar +HornetQ JMS Dead Letter Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start ++ +start ++ ++ ++ +build.directory +${basedir}/target/ ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.DeadLetterExample ++ jnp://localhost:1099 + ++ +stop ++ +stop ++ ++ +org.hornetq.examples.jms +hornetq-jms-dead-letter-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +${basedir}/target/classes/hornetq/server0 +HornetQ Dead Letter Example + + + + + +Dead Letter Example
+ +This example shows you how to define and deal with dead letter messages.
+Messages can be delivered unsuccessfully (e.g. if the transacted session used to consume them is rolled back). + Such a message goes back to the JMS destination ready to be redelivered. + However, this means it is possible for a message to be delivered again and again without any success and remain in the destination, clogging the system.
+To prevent this, messaging systems define dead letter messages: after a specified unsuccessful delivery attempts, the message is removed from the destination + and instead routed to a dead letter address where they can be consumed for further investigation. +
+ The example will show how to configure HornetQ to route a message to a dead letter address after 3 unsuccessful delivery attempts.
+
+ The example will send 1 message to a queue. We will deliver the message 3 times and rollback the session every time.
+ On the 4th attempt, there won't be any message to consume: it will have been moved to a dead letter address.
+ We will then consume this dead letter message. +Example setup
+Dead letter addresses and maximum delivery attempts are defined in the configuration file hornetq-configuration.xml:
++
+<address-setting match="jms.queue.exampleQueue"> + <dead-letter-address>jms.queue.deadLetterQueue</dead-letter-address> + <max-delivery-attempts>3</max-delivery-attempts> + </address-setting> ++This configuration will moved dead letter messages from
+exampleQueueto thedeadLetterQueue.HornetQ allows to specify either a
+Queueby prefixing thedead-letter-addresswithjms.queue.+ or aTopicby prefixing withjms.topic..
+ In this example, we will use aQueueto hold the dead letter messages.The maximum attempts of delivery is
3. Once this figure is reached, a message is considered a dead letter message and is moved to + thedeadLetterQueue. +Since we want to consume messages from this deadLetterQueue, we also need to add a JNDI binding to perform a lookup. + This is configured in hornetq-jms.xml
++
+ +<queue name="deadLetterQueue"> + <entry name="/queue/deadLetterQueue"/> + </queue>+Example step-by-step
+To run the example, simply type
+mvn verifyfrom this directory-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS transacted session
+
+
+ +Session session = connection.createSession(true, 0);+ - We create a JMS message producer on the session. This will be used to send the messages +
- We create a text messages +
- We send the message to the queue +
- We commit the session to effectively send the message to the queue +
- We create a JMS message consumer on the queue +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- We receive the message a 1st time +
- We roll back the session. The message we received is undelivered and goes back to the queue +
- We receive a message and roll back the session a 2nd time
+
+
+ +messageReceived = (TextMessage)messageConsumer.receive(5000); + System.out.println("2nd delivery from " + queue.getQueueName() + ": " + messageReceived.getText()); + session.rollback();+ - We do it againt a 3rd time
+
+
+ +messageReceived = (TextMessage)messageConsumer.receive(5000); + System.out.println("3rd delivery from " + queue.getQueueName() + ": " + messageReceived.getText()); + session.rollback();+Since the queue was configured to move messages to the
+ +deadLetterQueueafter3unsuccessful delivery attempts, + the message won't be in thequeueanymore - We try to receive a message from the queue for a 4th. Since there is none, the call will timeout after 5000ms and
messageReceivedwill benull++
+ +messageReceived = (TextMessage)messageConsumer.receive(5000); + System.out.println("4th delivery from " + queue.getQueueName() + ": " + messageReceived);+We have configured HornetQ to send any dead letter messages to the
+ +deadLetterQueue. + We will now consume messages from this queue and receives the dead letter messages. - We look up the JMS dead letter queue object from JNDI +
- We create a JMS message consumer on the dead letter queue +
- We consume a message from the dead letter queue: +
- The message consumed from the dead letter queue has the same content than the message which was sent to the queue
+
+
+ +System.out.println("Received message from " + deadLetterQueue.getQueueName() + ": " + messageReceived.getText());+JMS does not specify the notion of dead letter destinations and messages. From JMS point of view, the message received from the dead letter queue + is a different message than the message removed from the queue after the unsuccessful delivery attempts: + the messages have the same content (properties and body) but their JMS headers differ.
+ +
+ HornetQ defines additional properties for messages received from a dead letter destination - The message's destination is the dead letter queue +
- The origin destination is stored in the
_HQ_ORIG_ADDRESSproperty ++
+ +System.out.println("*Origin destination* of the message: " + messageReceived.getStringProperty("_HQ_ORIG_ADDRESS"));+ - We do not forget to commit the session to acknowledge that we have received the message from the dead letter queue +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+
+ +InitialContext initialContext = getContext();++
+ +Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");++
+ +ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");++
+ +connection = cf.createConnection();++
+ +MessageProducer messageProducer = session.createProducer(topic);++
+ +TextMessage message = session.createTextMessage("this is a text message");++
+ +producer.send(message);++
+ +session.commit();+We will now consume the message from the queue 3 times and roll back the session every time
+ ++
+ +MessageConsumer messageConsumer = session.createConsumer(queue);++
+ +connection.start();++
+ +TextMessage messageReceived = (TextMessage)messageConsumer.receive(5000); + System.out.println("1st delivery from " + queue.getQueueName() + ": " + messageReceived.getText());++
+ +session.rollback();++
+ +Queue deadLetterQueue = (Queue)initialContext.lookup("/queue/deadLetterQueue");++
+ +MessageConsumer deadLetterConsumer = session.createConsumer(expiryQueue);++
+ +messageReceived = (TextMessage)deadLetterConsumer.receive(5000);++
+ +System.out.println("Destination of the message: " + ((Queue)messageReceived.getJMSDestination()).getQueueName());++
+ + +session.commit();++
+finally + { + if (initialContext != null) + { + initialContext.close(); + } + if (connection != null) + { + connection.close(); + } + }+More information
+ +-
+
- User Manual's Undelivered Messages chapter +
+ + diff --git a/examples/jms/dead-letter/src/main/resources/hornetq/server0/hornetq-configuration.xml b/examples/jms/dead-letter/src/main/resources/hornetq/server0/hornetq-configuration.xml new file mode 100644 index 0000000000..b7df0a1da8 --- /dev/null +++ b/examples/jms/dead-letter/src/main/resources/hornetq/server0/hornetq-configuration.xml @@ -0,0 +1,50 @@ ++ + + + + + ++ ++ 1099 +localhost +1098 +localhost ++ + + ++ + + + + + + ++ + + + + ++ ++ ++ + ++ + ++ + + + + + ++ ++ ++ + + diff --git a/examples/jms/dead-letter/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/dead-letter/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..48c28dfa99 --- /dev/null +++ b/examples/jms/dead-letter/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,24 @@ +${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory ++ + + ++ ++ + + + + + + + + ++ +jms.queue.deadLetterQueue +3 ++ + \ No newline at end of file diff --git a/examples/jms/dead-letter/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/dead-letter/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/dead-letter/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ + + + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/delayed-redelivery/pom.xml b/examples/jms/delayed-redelivery/pom.xml new file mode 100644 index 0000000000..05a2853f30 --- /dev/null +++ b/examples/jms/delayed-redelivery/pom.xml @@ -0,0 +1,114 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/delayed-redelivery/readme.html b/examples/jms/delayed-redelivery/readme.html new file mode 100644 index 0000000000..0a2f44d4b6 --- /dev/null +++ b/examples/jms/delayed-redelivery/readme.html @@ -0,0 +1,168 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-delayed-redelivery-example +jar +HornetQ JMS Delayed Redelivery Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start ++ +start ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.DelayedRedeliveryExample ++ jnp://localhost:1099 + ++ +stop ++ +stop ++ ++ +org.hornetq.examples.jms +hornetq-jms-delayed-redelivery-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +${basedir}/target/classes/hornetq/server0 ++ ++ +build.directory +${basedir}/target/ +HornetQ Delayed Redelivery Example + + + + + +Delayed Redelivery Example
+ +This example demonstrates how HornetQ can be configured to provide a delayed redelivery in the case + where a message needs to be redelivered.
+Delaying redelivery can often be useful in the case that clients regularly fail or roll-back. Without a delayed + redelivery, the system can get into a "thrashing" state, with delivery being attempted, the client rolling back, and + delivery being re-attempted ad infinitum in quick succession, using up valuable CPU and network resources.
+Re-delivery occurs when the session is closed with unacknowledged messages. The unacknowledged messages will + be redelivered.
+By providing a redelivery delay, it can be specified that a delay of, say, 10 seconds is implemented between rollback + and redelivery. The specific delay is configurable on both a global and per destination level, by using wild-card + matching on the address settings.
+ +Example setup
+Redelivery delay is specified in the configuration file hornetq-configuration.xml:
+In this example we set the redelivery delay to 5 seconds for the specific example queue. We could set redelivery delay on + on multiple queues by specifying a wild-card in the match, e.g.
+match="jms.#"would apply the settings + to all JMS queues and topics.We then consume a message in a transacted session, and rollback, and note that the message is not redelivered until + after 5 seconds.
++
+<address-setting match="jms.queue.exampleQueue"> + <redelivery-delay>5000</redelivery-delay> + </address-setting> ++To run the example, simply type
+mvn verifyfrom this directory-
+
- Create an initial context to perform the JNDI lookup. +
- Perform a lookup on the queue +
- Perform a lookup on the Connection Factory +
- Create a JMS Connection +
- Create a transacted JMS Session
+
+
+ +Session session = connection.createSession(true, 0);+ - Create a JMS Message Producer +
- Create a Text Message +
- Send the Message +
- We commit the session to effectively send the message to the queue +
- We create a JMS message consumer on the queue +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- We receive the message... +
- ...but we roll back the session. the message returns to the queue, but only after a + 5 second delay +
- We try to receive the message but it's being delayed +
- We try and receive the message again, this time we should get it +
- We rollback the session again to cause another redelivery, and we time how long this one takes
+
+
+ ++ long start = System.currentTimeMillis(); + + session.rollback(); + + messageReceived = (TextMessage)messageConsumer.receive(8000); + + long end = System.currentTimeMillis(); + + System.out.println("3nd delivery from " + queue.getQueueName() + ": " + messageReceived.getText() + + " after " + (end - start) + " milliseconds."); ++ - And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+
+ +initialContext = getContext(0);++
+ +Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");++
+ +ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");++
+ +connection = cf.createConnection();++
+ +MessageProducer producer = session.createProducer(queue);++
+ +TextMessage message = session.createTextMessage("this is a text message");++
+ +producer.send(message);++
+ +session.commit();++
+ +MessageConsumer messageConsumer = session.createConsumer(queue);++
+ +connection.start();++
+ +TextMessage messageReceived = (TextMessage)messageConsumer.receive(5000); + System.out.println("1st delivery from " + queue.getQueueName() + ": " + messageReceived.getText());++
+ +session.rollback();++
+ ++ messageReceived = (TextMessage)messageConsumer.receive(3000); + + if (messageReceived != null) + { + return false; + } + + System.out.println("Redelivery has been delayed so received message is " + messageReceived); + +++
+ ++ messageReceived = (TextMessage)messageConsumer.receive(3000); + + System.out.println("2nd delivery from " + queue.getQueueName() + ": " + messageReceived.getText()); +++
+finally + { + if (initialContext != null) + { + initialContext.close(); + } + if (connection != null) + { + connection.close(); + } + }+More information
+ +-
+
- User Manual's Undelivered Messages chapter +
+ + diff --git a/examples/jms/delayed-redelivery/src/main/resources/hornetq/server0/hornetq-configuration.xml b/examples/jms/delayed-redelivery/src/main/resources/hornetq/server0/hornetq-configuration.xml new file mode 100644 index 0000000000..7251b55b42 --- /dev/null +++ b/examples/jms/delayed-redelivery/src/main/resources/hornetq/server0/hornetq-configuration.xml @@ -0,0 +1,49 @@ ++ + + + + + ++ ++ 1099 +localhost +1098 +localhost ++ + + ++ + + + + + + ++ + + + + ++ ++ ++ + ++ + ++ + + + + + ++ ++ ++ + + diff --git a/examples/jms/delayed-redelivery/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/delayed-redelivery/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..48c28dfa99 --- /dev/null +++ b/examples/jms/delayed-redelivery/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,24 @@ +${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory ++ + + ++ ++ + + + + + + + + ++ +5000 ++ + \ No newline at end of file diff --git a/examples/jms/delayed-redelivery/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/delayed-redelivery/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/delayed-redelivery/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ + + + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/divert/pom.xml b/examples/jms/divert/pom.xml new file mode 100644 index 0000000000..646ffce1c1 --- /dev/null +++ b/examples/jms/divert/pom.xml @@ -0,0 +1,152 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/divert/readme.html b/examples/jms/divert/readme.html new file mode 100644 index 0000000000..bd7d839e65 --- /dev/null +++ b/examples/jms/divert/readme.html @@ -0,0 +1,419 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-divert-example +jar +HornetQ JMS Divert Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start0 ++ +start ++ +${basedir}/target/classes/hornetq/server0 ++ +start1 ++ +start ++ +1199 +1198 +${basedir}/target/classes/hornetq/server1 +true ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.DivertExample ++ jnp://localhost:1099 + jnp://localhost:1199 + ++ ++ +exampleConfigDir +${basedir}/target/classes/hornetq ++ +stop0 ++ +stop ++ +${basedir}/target/classes/hornetq/server0 ++ +stop1 ++ +stop ++ +${basedir}/target/classes/hornetq/server1 ++ ++ +org.hornetq.examples.jms +hornetq-jms-divert-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false ++ ++ +build.directory +${basedir}/target/ +HornetQ Divert Example + + + + + +Divert Example
+ +HornetQ diverts allow messages to be transparently "diverted" from one address to another + with just some simple configuration defined on the server side.
+Diverts can be defined to be exclusive or non-exclusive.
+With an exclusive divert the message is intercepted and does not get sent to the queues originally + bound to that address - it only gets diverted.
+With a non-exclusive divert the message continues to go to the queues bound to the address, + but also a copy of the message gets sent to the address specified in the divert. Consequently non-exclusive + diverts can be used to "snoop" on another address
+Diverts can also be configured to have an optional filter. If specified then only matching messages + will be diverted.
+Diverts can be configured to apply a Transformer. If specified, all diverted messages will have the + opportunity of being transformed by the Transformer.
+Diverts are a very sophisticated concept, which when combined with bridges can be used to create + interesting and complex routings. The set of diverts can be thought of as a type of routing table + for messages.
+ +Example step-by-step
+In this example we will imagine a fictitious company which has two offices; one in London and another in New York.
+The company accepts orders for it's products only at it's London office, and also generates price-updates + for it's products, also only from it's London office. However only the New York office is interested in receiving + price updates for New York products. Any prices for New York products need to be forwarded to the New York office.
+There is an unreliable WAN linking the London and New York offices.
+The company also requires a copy of any order received to be available to be inspected by management.
+In order to achieve this, we will create a queue
+orderQueueon the London server in to which orders arrive.We will create a topic,
+spyTopicon the London server, and there will be two subscribers both in London.We will create a non-exclusive divert on the London server which will siphon off a copy of each order + received to the topic
+spyTopic.Here's the xml config for that divert, from
+hornetq-configuration.xml+
++ <divert name="order-divert"> + <address>jms.queue.orders</address> + <forwarding-address>jms.topic.spyTopic</forwarding-address> + <exclusive>false</exclusive> + </divert> ++For the prices we will create a topic on the London server,
+priceUpdatesto which all price updates + are sent. We will create another topic on the New York servernewYorkPriceUpdatesto which all New York + price updates need to be forwarded.Diverts can only be used to divert messages from one local address to another local address + so we cannot divert directly to an address on another server.
+Instead we divert to a local store and forward queue they we define in the configuration. This is just a normal queue + that we use for storing messages before forwarding to another node.
+Here's the configuration for it:
++
++ <queues> + <queue name="jms.queue.priceForwarding"> + <address>jms.queue.priceForwarding</address> + </queue> + </queues> ++Here's the configuration for the divert:
++
++ <divert name="prices-divert"> + <address>jms.topic.priceUpdates</address> + <forwarding-address>jms.queue.priceForwarding</forwarding-address> + <filter string="office='New York'"/> + <transformer-class-name>org.hornetq.jms.example.AddForwardingTimeTransformer</transformer-class-name> + <exclusive>true</exclusive> + </divert> ++Note we specify a filter in the divert, so only New York prices get diverted. We also specify a Transformer class + since we are going to insert a header in the message at divert time, recording the time the diversion happened.
+And finally we define a bridge that moves messages from the local queue to the address on the New York server. + Bridges move messages from queues to remote addresses and are ideal to use when the target server may be stopped and + started independently, and/or the network might be unreliable. Bridges guarantee once and only once delivery + of messages from their source queues to their target addresses.
+Here is the bridge configuration:
++
+ ++ <bridges> + <bridge name="price-forward-bridge"> + <queue-name>jms.queue.priceForwarding</queue-name> + <forwarding-address>jms.topic.newYorkPriceUpdates</forwarding-address> + <reconnect-attempts>-1</reconnect-attempts> + <static-connectors> + <connector-ref>newyork-connector</connector-ref> + </static-connectors> + </bridge> + </bridges> ++To run the example, simply type
+ +mvn verifyfrom this directory-
+
- Create an initial context to perform the JNDI lookup on the London server +
- Look-up the queue orderQueue on the London server - this is the queue any orders are sent to +
- Look-up the topic priceUpdates on the London server- this is the topic that any price updates are sent to +
- Look-up the spy topic on the London server- this is what we will use to snoop on any orders +
- Create an initial context to perform the JNDI lookup on the New York server. +
- Look-up the topic newYorkPriceUpdates on the New York server - any price updates sent to priceUpdates on the London server will + be diverted to the queue priceForward on the London server, and a bridge will consume from that queue and forward + them to the address newYorkPriceUpdates on the New York server where they will be distributed to the topic subscribers on + the New York server. + +
- Perform a lookup on the Connection Factory on the London server +
- Perform a lookup on the Connection Factory on the New York server. +
- Create a JMS Connection on the London server +
- Create a JMS Connection on the New York server +
- Create a JMS Session on the London server. +
- Create a JMS Session on the New York server. +
- Create a JMS MessageProducer orderProducer that sends to the queue orderQueue on the London server. +
- Create a JMS MessageProducer priceProducer that sends to the topic priceUpdates on the London server. +
- Create a JMS subscriber which subscribes to the spyTopic on the London server +
- Create another JMS subscriber which also subscribes to the spyTopic on the London server +
- Create a JMS MessageConsumer which consumes orders from the order queue on the London server +
- Create a JMS subscriber which subscribes to the priceUpdates topic on the London server +
- Create a JMS subscriber which subscribes to the newYorkPriceUpdates topic on the New York server +
- Create another JMS subscriber which also subscribes to the newYorkPriceUpdates topic on the New York server +
- Start the connections +
- Create an order message +
- Send the order message to the order queue on the London server +
- The order message is consumed by the orderConsumer on the London server +
- A copy of the order is also received by the spyTopic subscribers on the London server +
- Create and send a price update message, destined for London +
- The price update *should* be received by the local subscriber since we only divert messages + where office = New York +
- The price update *should not* be received in New York +
- Create a price update message, destined for New York +
- Send the price update message to the priceUpdates topic on the London server +
- The price update *should not* be received by the local subscriber to the priceUpdates topic + since it has been *exclusively* diverted to the priceForward queue, because it has a header saying + it is destined for the New York office +
- The remote subscribers on server 1 *should* receive a copy of the price update since + it has been diverted to a local priceForward queue which has a bridge consuming from it and which + forwards it to the same address on server 1. + We notice how the forwarded messages have had a special header added by our custom transformer that + we told the divert to use +
- And finally, always remember to close your resources after use, in a
finallyblock.
+
+
+
+ ++ initialContext0 = getContext(0); +++
+ ++ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue"); +++
+ ++ Topic priceUpdates = (Topic)initialContextLondon.lookup("/topic/priceUpdates"); +++
+ ++ Topic spyTopic = (Topic)initialContextLondon.lookup("/topic/spyTopic"); +++
+ ++ initialContextNewYork = getContext(1); +++
+ ++ Topic newYorkPriceUpdates = (Topic)initialContextNewYork.lookup("/topic/newYorkPriceUpdates"); +++
+ ++ ConnectionFactory cfLondon = (ConnectionFactory)initialContextLondon.lookup("/ConnectionFactory"); +++
+ ++ ConnectionFactory cfNewYork = (ConnectionFactory)initialContextNewYork.lookup("/ConnectionFactory"); +++
+ ++ connectionLondon = cfLondon.createConnection(); +++
+ ++ connectionNewYork = cfNewYork.createConnection(); +++
+ ++ Session sessionLondon = connectionLondon.createSession(false, Session.AUTO_ACKNOWLEDGE); +++
+ ++ Session sessionNewYork = connectionNewYork.createSession(false, Session.AUTO_ACKNOWLEDGE); +++
+ ++ MessageProducer orderProducer = sessionLondon.createProducer(orderQueue); + /code> ++
+ ++ MessageProducer priceProducer = sessionLondon.createProducer(priceUpdates); + /code> ++
+ ++ MessageConsumer spySubscriberA = sessionLondon.createConsumer(spyTopic); +++
+ ++ MessageConsumer spySubscriberB = sessionLondon.createConsumer(spyTopic); +++
+ ++ MessageConsumer orderConsumer = sessionLondon.createConsumer(orderQueue); +++
+ ++ MessageConsumer priceUpdatesSubscriberLondon = sessionLondon.createConsumer(priceUpdates); +++
+ ++ MessageConsumer newYorkPriceUpdatesSubscriberA = sessionNewYork.createConsumer(newYorkPriceUpdates); +++
+ ++ MessageConsumer newYorkPriceUpdatesSubscriberB = sessionNewYork.createConsumer(newYorkPriceUpdates); +++
+ ++ connectionLondon.start(); + + connectionNewYork.start(); +++
+ ++ TextMessage orderMessage = sessionLondon.createTextMessage("This is an order"); +++
+ ++ orderProducer.send(orderMessage); + + System.out.println("Sent message: " + orderMessage.getText()); +++
+ ++ TextMessage receivedOrder = (TextMessage)orderConsumer.receive(5000); + + System.out.println("Received order: " + receivedOrder.getText()); +++
+ ++ TextMessage spiedOrder1 = (TextMessage)spySubscriberA.receive(5000); + + System.out.println("Snooped on order: " + spiedOrder1.getText()); + + TextMessage spiedOrder2 = (TextMessage)spySubscriberB.receive(5000); + + System.out.println("Snooped on order: " + spiedOrder2.getText()); +++
+ ++ TextMessage priceUpdateMessageLondon = sessionLondon.createTextMessage("This is a price update for London"); + + priceUpdateMessageLondon.setStringProperty("office", "London"); + + priceProducer.send(priceUpdateMessageLondon); +++
+ ++ TextMessage receivedUpdate = (TextMessage)priceUpdatesSubscriberLondon.receive(2000); + + System.out.println("Received price update locally: " + receivedUpdate.getText()); +++
+ ++ TextMessage priceUpdate1 = (TextMessage)newYorkPriceUpdatesSubscriberA.receive(1000); + + if (priceUpdate1 != null) + { + return false; + } + + System.out.println("Did not received price update in New York, look it's: " + priceUpdate1); + + TextMessage priceUpdate2 = (TextMessage)newYorkPriceUpdatesSubscriberB.receive(1000); + + if (priceUpdate2 != null) + { + return false; + } + + System.out.println("Did not received price update in New York, look it's: " + priceUpdate2); +++
+ ++ TextMessage priceUpdateMessageNewYork = sessionLondon.createTextMessage("This is a price update for New York"); + + priceUpdateMessageNewYork.setStringProperty("office", "New York"); +++
+ ++ priceProducer.send(priceUpdateMessageNewYork); +++
+ ++ Message message = priceUpdatesSubscriberLondon.receive(1000); + + if (message != null) + { + return false; + } + + System.out.println("Didn't receive local price update, look, it's: " + message); +++
+ + ++ priceUpdate1 = (TextMessage)newYorkPriceUpdatesSubscriberA.receive(5000); + + System.out.println("Received forwarded price update on server 1: " + priceUpdate1.getText()); + System.out.println("Time of forward: " + priceUpdate1.getLongProperty("time_of_forward")); + + priceUpdate2 = (TextMessage)newYorkPriceUpdatesSubscriberB.receive(5000); + + System.out.println("Received forwarded price update on server 2: " + priceUpdate2.getText()); + System.out.println("Time of forward: " + priceUpdate2.getLongProperty("time_of_forward")); +++
+ + + ++ finally + { + if (initialContextLondon != null) + { + initialContextLondon.close(); + } + if (initialContextNewYork != null) + { + initialContextNewYork.close(); + } + if (connectionLondon != null) + { + connectionLondon.close(); + } + if (connectionNewYork != null) + { + connectionNewYork.close(); + } + } +++ + + + + diff --git a/examples/jms/divert/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/divert/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..0694025f65 --- /dev/null +++ b/examples/jms/divert/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,38 @@ +${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + + ++ + + + ++ + + + +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + ++ jms.queue.priceForwarding + ++ + + + ++ + +order-divert + jms.queue.orders +jms.topic.spyTopic +false ++ +prices-divert + jms.topic.priceUpdates +jms.queue.priceForwarding ++ org.hornetq.jms.example.AddForwardingTimeTransformer +true ++ + + + ++ +jms.queue.priceForwarding +jms.topic.newYorkPriceUpdates +-1 ++ +newyork-connector ++ + + ++ ++ + + + + + + + + + \ No newline at end of file diff --git a/examples/jms/divert/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/divert/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/divert/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + + + ++ ++ + ++ + + + ++ + + + ++ + + + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/divert/src/main/resources/hornetq/server1/hornetq-configuration.xml b/examples/jms/divert/src/main/resources/hornetq/server1/hornetq-configuration.xml new file mode 100644 index 0000000000..cb7f15a706 --- /dev/null +++ b/examples/jms/divert/src/main/resources/hornetq/server1/hornetq-configuration.xml @@ -0,0 +1,45 @@ ++ ++ + + diff --git a/examples/jms/divert/src/main/resources/hornetq/server1/hornetq-jms.xml b/examples/jms/divert/src/main/resources/hornetq/server1/hornetq-jms.xml new file mode 100644 index 0000000000..9b1bf55e2e --- /dev/null +++ b/examples/jms/divert/src/main/resources/hornetq/server1/hornetq-jms.xml @@ -0,0 +1,24 @@ +${build.directory}/server1/data/messaging/bindings + +${build.directory}/server1/data/messaging/journal + +${build.directory}/server1/data/messaging/largemessages + +${build.directory}/server1/data/messaging/paging + + + ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + + ++ ++ + + + + + + + + + \ No newline at end of file diff --git a/examples/jms/divert/src/main/resources/hornetq/server1/hornetq-users.xml b/examples/jms/divert/src/main/resources/hornetq/server1/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/divert/src/main/resources/hornetq/server1/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + + + + ++ ++ + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/durable-subscription/pom.xml b/examples/jms/durable-subscription/pom.xml new file mode 100644 index 0000000000..e4305c1369 --- /dev/null +++ b/examples/jms/durable-subscription/pom.xml @@ -0,0 +1,116 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/durable-subscription/readme.html b/examples/jms/durable-subscription/readme.html new file mode 100644 index 0000000000..01747346f2 --- /dev/null +++ b/examples/jms/durable-subscription/readme.html @@ -0,0 +1,140 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-durable-subscription-example +jar +HornetQ JMS Durable Subscription Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start ++ +start ++ ++ ++ +build.directory +${basedir}/target/ ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.DurableSubscriptionExample ++ jnp://localhost:1099 + ++ +stop ++ +stop ++ ++ +org.hornetq.examples.jms +hornetq-jms-durable-subscription-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +${basedir}/target/classes/hornetq/server0 +HornetQ JMS Durable Subscription Example + + + + + +JMS Durable Subscription Example
+ +This example demonstrates how to use a durable subscription with HornetQ.
+Durable subscriptions are a standard part of JMS, please consult the JMS 1.1 specification for full details.
+Unlike non durable subscriptions, the key function of durable subscriptions is that the messages contained in them + persist longer than the lifetime of the subscriber - i.e. they will accumulate messages sent to the topic even + if the subscriber is not currently connected. They will also survive server restarts. Note that for the messages to + be persisted, the messages sent to them must be marked as persistent messages.
+ +Example step-by-step
+To run the example, simply type
+ +mvn verifyfrom this directory-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS topic object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We set the client-id on the connection. This must be the first operation performed on the connection object. + The combination of client-id and durable subscription name uniquely identifies the durable subscription. Maybe different durable subscritions can have the same name if they belong to different client-id values +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create the durable subscriber on the topic, specifying it's name. Since this is the first time the subscriber is created and a subscription with that name and for this client-id does not already exist, then the underlying durable subscription will be created, and a subscriber will be created and returned for that subscription. +
- We create a JMS text message, message 1, that we are going to send. Note that it must be a persistent message in order to survive server restart. +
- We send message 1 to the topic +
- The message arrives in the subscription, and we consume the message from the subscription. +
- We create and send another text message, message 2, to the same topic +
- Now we close the subscriber. Since the subscription is durable it will continue to survive even though there is no subscriber attached to it. At this point you could even stop and restart the server and the subscription would survive! + +
- We now create another durable subscriber, with the same name and same client-id on the same topic. Since the durable subscrition already exists, it will simply return a new subscriber consuming from the same durable subscription instance as before + +
- We consume message 2 which was sent before the first subscriber was closed. + +
- We close the second subscriber. + +
- Now we delete the underlying durable subscription. This will delete any remaining unacknowledged messages in the subscription and a new subscriber will not be able to access them + +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+
+ +initialContext = getContext();++
+ +Topic topic = (Topic) initialContext.lookup("/topic/exampleTopic");++
+ +ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");++
+ +connection = cf.createConnection();++
+ +connection.setClientID("durable-client");++
+ +connection.start();++
+ +Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);++
+ +MessageProducer messageProducer = session.createProducer(topic);++
+ +TopicSubscriber subscriber = session.createDurableSubscriber(topic, "subscriber-1");++
+ +TextMessage message1 = session.createTextMessage("This is a text message 1");++
+ +messageProducer.send(message1);++
+ +TextMessage messageReceived = (TextMessage)subscriber.receive();++
+ +TextMessage message2 = session.createTextMessage("This is a text message 2"); + + messageProducer.send(message2);++
+ +subscriber.close();++
+ +subscriber = session.createDurableSubscriber(topic, "subscriber-1");++
+ +messageReceived = (TextMessage)subscriber.receive();++
+ +subscriber.close();++
+ +session.unsubscribe("subscriber-1");++
+ + + +finally + { + if (initialContext != null) + { + initialContext.close(); + } + if (connection != null) + { + connection.close(); + } + }++ + diff --git a/examples/jms/durable-subscription/src/main/resources/hornetq/server0/hornetq-configuration.xml b/examples/jms/durable-subscription/src/main/resources/hornetq/server0/hornetq-configuration.xml new file mode 100644 index 0000000000..575eba5315 --- /dev/null +++ b/examples/jms/durable-subscription/src/main/resources/hornetq/server0/hornetq-configuration.xml @@ -0,0 +1,44 @@ ++ + + + + + ++ ++ 1099 +localhost +1098 +localhost ++ + + ++ + + + + + + ++ + + + + ++ ++ ++ + ++ + ++ + + + + + ++ ++ ++ + + diff --git a/examples/jms/durable-subscription/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/durable-subscription/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..f89d475dd9 --- /dev/null +++ b/examples/jms/durable-subscription/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,19 @@ +${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + + ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + + ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/durable-subscription/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/durable-subscription/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/durable-subscription/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/embedded-simple/pom.xml b/examples/jms/embedded-simple/pom.xml new file mode 100644 index 0000000000..8784f9c4ea --- /dev/null +++ b/examples/jms/embedded-simple/pom.xml @@ -0,0 +1,113 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/embedded-simple/readme.html b/examples/jms/embedded-simple/readme.html new file mode 100644 index 0000000000..9ee98d3ea7 --- /dev/null +++ b/examples/jms/embedded-simple/readme.html @@ -0,0 +1,52 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-embedded-simple-example +jar +HornetQ JMS Simple Embedded Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.EmbeddedExample ++ jnp://localhost:1099 + jnp://localhost:1199 + ++ ++ +exampleConfigDir +${basedir}/target/classes/hornetq ++ ++ +org.hornetq.examples.jms +hornetq-jms-embedded-simple-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +${basedir}/target/classes/hornetq/server0 +HornetQ Embedded JMS Server Example + + + + + +Embedded JMS Server Example
+ +This examples shows how to setup and run an embedded JMS server using HornetQ along with HornetQ configuration files.
+ +Example step-by-step
+To run the example, simply type
+ +mvn verifyfrom this directory-
+
- Create HornetQ core configuration files and make sure they are within your classpath. By default, HornetQ + expects the classnames to be "hornetq-configuration.xml", "hornetq-jms.xml", and "hornetq-users.xml". +
- Create and start HornetQ JMS server +
- Lookup JMS resources defined in the configuration +
- Send and receive a message using JMS API +
- Stop the JMS server +
- Stop the JNDI server +
+
+ +EmbeddedJMS jmsServer = new EmbeddedJMS(); + jmsServer.start();+At this point the JMS server is started and any JMS clients can look up JMS resources from the JNDI to send/receive + messages from the server. To keep the example simple, we will send and receive a JMS message from the same JVM + used to run the JMS server.
+ ++
+ +ConnectionFactory cf = (ConnectionFactory)context.lookup("/cf"); + Queue queue = (Queue)context.lookup("/queue/queue1");+See the Queue Example for detailed steps to send and receive a JMS message
+ +Finally, we stop the JMS server and its associated resources.
+ ++
+ +jmsServer.stop();++
+naming.stop(); + jndiServer.stop();++ + diff --git a/examples/jms/embedded-simple/src/main/resources/hornetq-jms.xml b/examples/jms/embedded-simple/src/main/resources/hornetq-jms.xml new file mode 100644 index 0000000000..bc4af35e80 --- /dev/null +++ b/examples/jms/embedded-simple/src/main/resources/hornetq-jms.xml @@ -0,0 +1,19 @@ +false + + ++ + ++ +org.hornetq.core.remoting.impl.invm.InVMConnectorFactory ++ + + + ++ +org.hornetq.core.remoting.impl.invm.InVMAcceptorFactory ++ + + ++ ++ + + + + + + + diff --git a/examples/jms/embedded-simple/src/main/resources/hornetq-users.xml b/examples/jms/embedded-simple/src/main/resources/hornetq-users.xml new file mode 100644 index 0000000000..880a9667e7 --- /dev/null +++ b/examples/jms/embedded-simple/src/main/resources/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/embedded/pom.xml b/examples/jms/embedded/pom.xml new file mode 100644 index 0000000000..4a2c253e22 --- /dev/null +++ b/examples/jms/embedded/pom.xml @@ -0,0 +1,113 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/embedded/readme.html b/examples/jms/embedded/readme.html new file mode 100644 index 0000000000..b40b827719 --- /dev/null +++ b/examples/jms/embedded/readme.html @@ -0,0 +1,109 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-embedded-example +jar +HornetQ JMS Embedded Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.EmbeddedExample ++ jnp://localhost:1099 + jnp://localhost:1199 + ++ ++ +exampleConfigDir +${basedir}/target/classes/hornetq ++ +build.directory +${basedir}/target/ ++ ++ +org.hornetq.examples.jms +hornetq-jms-embedded-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA +HornetQ Embedded JMS Server Example + + + + + +Embedded JMS Server Example
+ +This examples shows how to setup and run an embedded JMS server using HornetQ.
+HornetQ was designed using POJOs (Plain Old Java Objects) which means embedding HornetQ in your own application + is as simple as instantiating a few objects.
+This example does not use any configuration files. The server is configured using POJOs and can be easily ported to any dependency injection framework.
+ +
+ We will setup and run a full-fledged JMS server which binds its JMS resources to JNDI and can be accessed by remote clients.Example step-by-step
+To run the example, simply type
+ +mvn verifyfrom this directory-
+
- Create HornetQ core configuration, and set the properties accordingly +
- Create the HornetQ core server +
- Create and start the JNDI server (using JBoss JNDI implementation) +
- Create the JMS configuration +
- Configure context used to bind the JMS resources to JNDI +
- Configure the JMS ConnectionFactory +
- Configure the JMS Queue +
- Start the JMS Server using the HornetQ core server and the JMS configuration +
- Lookup JMS resources defined in the configuration +
- Send and receive a message using JMS API +
- Stop the JMS server +
- Stop the JNDI server +
+
+ +Configuration configuration = new ConfigurationImpl(); + configuration.setPersistenceEnabled(false); + configuration.setSecurityEnabled(false); + configuration.getAcceptorConfigurations().add(new TransportConfiguration(NettyAcceptorFactory.class.getName()));+ Configuration configuration = new ConfigurationImpl();+
+ +HornetQServer hornetqServer = HornetQ.newHornetQServer(configuration);++
+ +System.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory"); + NamingBeanImpl naming = new NamingBeanImpl(); + naming.start(); + Main jndiServer = new Main(); + jndiServer.setNamingInfo(naming); + jndiServer.setPort(1099); + jndiServer.setBindAddress("localhost"); + jndiServer.setRmiPort(1098); + jndiServer.setRmiBindAddress("localhost"); + jndiServer.start();++
+ +JMSConfiguration jmsConfig = new JMSConfigurationImpl();++
+ +Hashtable<String, String> env = new Hashtable<String, String>(); + env.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory"); + env.put("java.naming.provider.url", "jnp://localhost:1099"); + env.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); + Context context = new InitialContext(env); + jmsConfig.setContext(context);++
+ +TransportConfiguration connectorConfig = new TransportConfiguration(NettyConnectorFactory.class.getName()); + ConnectionFactoryConfiguration cfConfig = new ConnectionFactoryConfigurationImpl("cf", connectorConfig, "/cf"); + jmsConfig.getConnectionFactoryConfigurations().add(cfConfig);++
+ +QueueConfiguration queueConfig = new QueueConfigurationImpl("queue1", null, false, "/queue/queue1"); + jmsConfig.getQueueConfigurations().add(queueConfig);++
+ +JMSServerManager jmsServer = new JMSServerManagerImpl(hornetqServer, jmsConfig); + jmsServer.start();+At this point the JMS server is started and any JMS clients can look up JMS resources from JNDI to send/receive + messages from the server. To keep the example simple, we will send and receive a JMS message from the same JVM + used to run the JMS server.
+ ++
+ +ConnectionFactory cf = (ConnectionFactory)context.lookup("/cf"); + Queue queue = (Queue)context.lookup("/queue/queue1");+See the Queue Example for detailed steps to send and receive a JMS message
+ +Finally, we stop the JMS server and its associated resources.
+ ++
+ +jmsServer.stop();++
+naming.stop(); + jndiServer.stop();+connectorNames = new ArrayList (); + connectorNames.add("connector"); + ConnectionFactoryConfiguration cfConfig = new ConnectionFactoryConfigurationImpl("cf", false, connectorNames, "/cf"); + jmsConfig.getConnectionFactoryConfigurations().add(cfConfig); + + // Step 4. Configure the JMS Queue + JMSQueueConfiguration queueConfig = new JMSQueueConfigurationImpl("queue1", null, false, "/queue/queue1"); + jmsConfig.getQueueConfigurations().add(queueConfig); + + // Step 5. Start the JMS Server using the HornetQ core server and the JMS configuration + EmbeddedJMS jmsServer = new EmbeddedJMS(); + jmsServer.setConfiguration(configuration); + jmsServer.setJmsConfiguration(jmsConfig); + jmsServer.start(); + System.out.println("Started Embedded JMS Server"); + + // Step 6. Lookup JMS resources defined in the configuration + ConnectionFactory cf = (ConnectionFactory)jmsServer.lookup("/cf"); + Queue queue = (Queue)jmsServer.lookup("/queue/queue1"); + + // Step 7. Send and receive a message using JMS API + Connection connection = null; + try + { + connection = cf.createConnection(); + Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); + MessageProducer producer = session.createProducer(queue); + TextMessage message = session.createTextMessage("Hello sent at " + new Date()); + System.out.println("Sending message: " + message.getText()); + producer.send(message); + MessageConsumer messageConsumer = session.createConsumer(queue); + connection.start(); + TextMessage messageReceived = (TextMessage)messageConsumer.receive(1000); + System.out.println("Received message:" + messageReceived.getText()); + } + finally + { + if (connection != null) + { + connection.close(); + } + + // Step 11. Stop the JMS server + jmsServer.stop(); + System.out.println("Stopped the JMS Server"); + } + } + catch (Exception e) + { + e.printStackTrace(); + return false; + } + return true; + } +} diff --git a/examples/jms/expiry/pom.xml b/examples/jms/expiry/pom.xml new file mode 100644 index 0000000000..de4467def5 --- /dev/null +++ b/examples/jms/expiry/pom.xml @@ -0,0 +1,116 @@ + + \ No newline at end of file diff --git a/examples/jms/expiry/readme.html b/examples/jms/expiry/readme.html new file mode 100644 index 0000000000..df2f2faa2b --- /dev/null +++ b/examples/jms/expiry/readme.html @@ -0,0 +1,187 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-expiry-example +jar +HornetQ JMS Expiry Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start ++ +start ++ ++ ++ +build.directory +${basedir}/target/ ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.ExpiryExample ++ jnp://localhost:1099 + ++ +stop ++ +stop ++ ++ +org.hornetq.examples.jms +hornetq-jms-expiry-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +${basedir}/target/classes/hornetq/server0 +HornetQ Message Expiration Example + + + + + +JMS Expiration Example
+ +This example shows you how to configure HornetQ so messages are expipired after a certain time..
+Messages can be retained in the messaging system for a limited period of time before being removed. + JMS specification states that clients should not receive messages that have been expired (but it does not guarantee this will not happen).
+HornetQ can assign a expiry address to a given queue so that when messages are expired, they are removed from the queue and + routed to an this address. These "expired" messages can later be consumed for further inspection. +
+ The example will send 1 message with a short time-to-live to a queue. We will wait for the message to expire and checks that the message + is no longer in the queue it was sent to. + We will instead consume it from an expiry queue where it was moved when it expired. +
+Example setup
+Expiry destinations are defined in the configuration file hornetq-configuration.xml:
++
+<address-setting match="jms.queue.exampleQueue"> + <expiry-address>jms.queue.expiryQueue</expiry-address> + </address-setting> ++This configuration will moved expired messages from the
+exampleQueueto theexpiryQueueHornetQ allows to specify either a
+Queueby prefixing theexpiry-addresswithjms.queue.+ or aTopicby prefixing withjms.topic..
+ In this example, we will use aQueueto hold the expired messages.Since we want to consume messages from this expiryQueue, we also need to add a JNDI binding to perform a lookup. + This is configured in hornetq-jms.xml
++
+ +<queue name="expiryQueue"> + <entry name="/queue/expiryQueue"/> + </queue>+Example step-by-step
+To run the example, simply type
+mvn verifyfrom this directory-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages +
- We create a JMS message producer on the session. This will be used to send the messages +
- Messages sent by this producer will be retained for 1s (1000ms) before expiration +
- We create a text messages +
- We send the message to the queue +
- We sleep a little bit to let the message expire +
- We create a JMS message consumer on the queue +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- We try to receive a message from the queue. Since there is none, the call will timeout after 5000ms and
messageReceivedwill benull++
+ +TextMessage messageReceived = (TextMessage) messageConsumer.receive(5000); + System.out.println("Received message from " + queue.getQueueName() + ": " + messageReceived);+However, we have configured HornetQ to send any expired messages to the
+ +expiryQueue. + We will now consume messages from this expiry queue and receives the expired message. - We look up the JMS expiry queue object from JNDI +
- We create a JMS message consumer on the expiry queue +
- We consume a message from the expiry queue: +
- The message consumed from the expiry queue has the same content than the message which was sent to the queue
+
+
+ +System.out.println("Received message from " + expiryQueue.getQueueName() + ": " + messageReceived.getText());+JMS does not specify the notion of expiry queue. From JMS point of view, the message received from the expiry queue + is a different message than the message expired from the queue: the two messages have the same content (properties and body) but + their JMS headers differ.
+ +
+ HornetQ defines additional properties to correlate the message received from the expiry queue with the + message expired from the queue - The expired message's destination is the expiry queue +
- The expired message has its own expiration time (its time to live in the expiry queue) +
- The origin destination is stored in the
_HORNETQ_ORIG_DESTINATIONproperty ++
+ +System.out.println("*Origin destination* of the expired message: " + messageReceived.getStringProperty("_HORNETQ_ORIG_DESTINATION"));+ - The actual expiration time (when the message was expired from the queue) is stored in the
_HORNETQ_ACTUAL_EXPIRYproperty ++
+ + +System.out.println("*Actual expiration time* of the expired message: " + messageReceived.getLongProperty("_HORNETQ_ACTUAL_EXPIRY"));+ - And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+
+ +InitialContext initialContext = getContext();++
+ +Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");++
+ +ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");++
+ +connection = cf.createConnection();++
+ +Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);++
+ +MessageProducer messageProducer = session.createProducer(topic);++
+ +producer.setTimeToLive(1000);++
+ +TextMessage message = session.createTextMessage("this is a text message");++
+ +producer.send(message);++
+ +Thread.sleep(5000);+We will now try to consume the message from the queue but it won't be there since it has expired
+ ++
+ +MessageConsumer messageConsumer = session.createConsumer(queue);++
+ +connection.start();++
+ +Queue expiryQueue = (Queue)initialContext.lookup("/queue/expiryQueue");++
+ +MessageConsumer expiryConsumer = session.createConsumer(expiryQueue);++
+ +messageReceived = (TextMessage)expiryConsumer.receive(5000);++
+ +System.out.println("Destination of the expired message: " + ((Queue)messageReceived.getJMSDestination()).getQueueName());++
+ +System.out.println("Expiration time of the expired message (relative to the expiry queue): " + messageReceived.getJMSExpiration());+As we have not defined a time-to-live for the expiry queue, messages sent to the expiry queue will be kept forever (their JMS Expiration value is 0)
+ ++
+finally + { + if (initialContext != null) + { + initialContext.close(); + } + if (connection != null) + { + connection.close(); + } + }+More information
+ +-
+
- User Manual's Message Expiry chapter +
+ + diff --git a/examples/jms/expiry/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/expiry/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..417a5a2649 --- /dev/null +++ b/examples/jms/expiry/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,24 @@ +${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory ++ + + ++ ++ + + + + + + + + ++ +jms.queue.expiryQueue ++ + \ No newline at end of file diff --git a/examples/jms/expiry/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/expiry/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/expiry/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ + + + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/ha-policy-autobackup/pom.xml b/examples/jms/ha-policy-autobackup/pom.xml new file mode 100644 index 0000000000..f9f61ce3cc --- /dev/null +++ b/examples/jms/ha-policy-autobackup/pom.xml @@ -0,0 +1,153 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/ha-policy-autobackup/src/main/java/org/hornetq/jms/example/HAPolicyAutoBackupExample.java b/examples/jms/ha-policy-autobackup/src/main/java/org/hornetq/jms/example/HAPolicyAutoBackupExample.java new file mode 100644 index 0000000000..1931956c8e --- /dev/null +++ b/examples/jms/ha-policy-autobackup/src/main/java/org/hornetq/jms/example/HAPolicyAutoBackupExample.java @@ -0,0 +1,173 @@ +/* + * Copyright 2005-2014 Red Hat, Inc. + * Red Hat licenses this file to you under the Apache License, version + * 2.0 (the "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * http://www.apache.org/licenses/LICENSE-2.0 + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + * implied. See the License for the specific language governing + * permissions and limitations under the License. + */ +package org.hornetq.jms.example; + +import javax.jms.Connection; +import javax.jms.ConnectionFactory; +import javax.jms.MessageConsumer; +import javax.jms.MessageProducer; +import javax.jms.Queue; +import javax.jms.Session; +import javax.jms.TextMessage; +import javax.naming.InitialContext; + +import org.hornetq.api.core.TransportConfiguration; +import org.hornetq.api.core.client.ClusterTopologyListener; +import org.hornetq.api.core.client.TopologyMember; +import org.hornetq.common.example.HornetQExample; +import org.hornetq.jms.client.HornetQConnection; +import org.hornetq.jms.client.HornetQConnectionFactory; + +import java.util.ArrayList; +import java.util.List; +import java.util.concurrent.CountDownLatch; +import java.util.concurrent.TimeUnit; + +/** + * A simple example that demonstrates server side load-balancing of messages between the queue instances on different + * nodes of the cluster. + * + */ +public class HAPolicyAutoBackupExample extends HornetQExample +{ + public static void main(final String[] args) + { + new HAPolicyAutoBackupExample().run(args); + } + + @Override + public boolean runExample() throws Exception + { + Connection connection0 = null; + + Connection connection1 = null; + + InitialContext ic0 = null; + + InitialContext ic1 = null; + + try + { + // Step 1. Get an initial context for looking up JNDI from server 0 and 1 + ic0 = getContext(0); + ic1 = getContext(1); + + // Step 2. Look-up the JMS Queue object from JNDI + Queue queue = (Queue) ic0.lookup("/queue/exampleQueue"); + + // Step 3. Look-up a JMS Connection Factory object from JNDI on server 0 and 1 + ConnectionFactory cf0 = (ConnectionFactory) ic0.lookup("/ConnectionFactory"); + ConnectionFactory cf1 = (ConnectionFactory) ic1.lookup("/ConnectionFactory"); + + // Step 6. We create JMS Connections to server 0 and 1 + connection0 = cf0.createConnection(); + connection1 = cf1.createConnection(); + + // step 7. wait for the backups to start replication + waitForBackups(cf0, 2); + + // Step 8. We create JMS Sessions on server 0 and 1 + Session session0 = connection0.createSession(false, Session.AUTO_ACKNOWLEDGE); + Session session1 = connection1.createSession(false, Session.AUTO_ACKNOWLEDGE); + + // Step 9. We start the connections to ensure delivery occurs on them + connection0.start(); + connection1.start(); + + // Step 10. We create JMS MessageConsumer objects on server 0 and server 1 + MessageConsumer consumer0 = session0.createConsumer(queue); + MessageConsumer consumer1 = session1.createConsumer(queue); + + + // Step 11. We create a JMS MessageProducer object on server 0 + MessageProducer producer = session0.createProducer(queue); + + // Step 12. We send some messages to server 0 + + final int numMessages = 10; + + for (int i = 0; i < numMessages; i++) + { + TextMessage message = session0.createTextMessage("This is text message " + i); + + producer.send(message); + + System.out.println("Sent message: " + message.getText()); + } + + // Step 13. We now consume half the messages on consumer0 + // note that the other half of the messages will have been sent to server1 for consumer1 + for (int i = 0; i < numMessages / 2; i++) + { + TextMessage message0 = (TextMessage) consumer0.receive(5000); + + System.out.println("Got message: " + message0.getText() + " from node 0"); + } + + // Step 14.now kill server1, messages will be scaled down to server0 + killServer(1); + + // Step 15.close the consumer so it doesnt get any messages + consumer1.close(); + + // Step 16. we now receive the messages that were on server1 but were scaled down to server0 + for (int i = 0; i < numMessages / 2; i++) + { + TextMessage message0 = (TextMessage) consumer0.receive(5000); + + System.out.println("Got message: " + message0.getText() + " from node 1"); + } + + return true; + } + finally + { + // Step 17. Be sure to close our resources! + + if (connection0 != null) + { + connection0.close(); + } + + if (connection1 != null) + { + connection1.close(); + } + } + } + + private void waitForBackups(ConnectionFactory cf0, int backups) throws InterruptedException + { + final CountDownLatch latch = new CountDownLatch(backups); + ((HornetQConnectionFactory) cf0).getServerLocator().addClusterTopologyListener(new ClusterTopologyListener() + { + List4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +ha-policy-autobackup +jar +HornetQ JMS HA Policy Auto backup example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start0 ++ +start ++ +${basedir}/target/classes/hornetq/server0 ++ ++ +udp-address +${udp-address} ++ +start1 ++ +start ++ +1199 +1198 +${basedir}/target/classes/hornetq/server1 +true ++ ++ +udp-address +${udp-address} ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.HAPolicyAutoBackupExample ++ jnp://localhost:1099 + jnp://localhost:1199 + ++ ++ +exampleConfigDir +${basedir}/target/classes/hornetq ++ +stop0 ++ +stop ++ +${basedir}/target/classes/hornetq/server0 ++ +stop1 ++ +stop ++ +${basedir}/target/classes/hornetq/server1 ++ ++ +org.hornetq.examples.jms +ha-policy-autobackup +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +backups = new ArrayList (); + @Override + public void nodeUP(TopologyMember member, boolean last) + { + if (member.getBackup() != null && !backups.contains(member.getBackup())) + { + backups.add(member.getBackup()); + latch.countDown(); + } + } + + @Override + public void nodeDown(long eventUID, String nodeID) + { + } + }); + latch.await(30000, TimeUnit.MILLISECONDS); + } + +} diff --git a/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server0/hornetq-configuration.xml b/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server0/hornetq-configuration.xml new file mode 100644 index 0000000000..6c90184e7e --- /dev/null +++ b/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server0/hornetq-configuration.xml @@ -0,0 +1,82 @@ + + + \ No newline at end of file diff --git a/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..50eb1365d2 --- /dev/null +++ b/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,30 @@ +target/server0/data/messaging/bindings + +target/server0/data/messaging/journal + +target/server0/data/messaging/largemessages + +target/server0/data/messaging/paging + + ++ + + ++ +org.hornetq.core.remoting.impl.invm.InVMConnectorFactory ++ + +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.invm.InVMAcceptorFactory ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + +1 ++ +invm-connector ++ +invm-connector +server1-connector +netty-connector ++ + + + ++ jms + +netty-connector +500 +true +true +1 ++ +server1-connector ++ + + ++ ++ + + + + + + + + \ No newline at end of file diff --git a/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ true + +1000 + + +1.0 + + +-1 ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server1/hornetq-configuration.xml b/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server1/hornetq-configuration.xml new file mode 100644 index 0000000000..36b3d9d55c --- /dev/null +++ b/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server1/hornetq-configuration.xml @@ -0,0 +1,82 @@ ++ ++ + + diff --git a/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server1/hornetq-jms.xml b/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server1/hornetq-jms.xml new file mode 100644 index 0000000000..50eb1365d2 --- /dev/null +++ b/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server1/hornetq-jms.xml @@ -0,0 +1,30 @@ +target/server1/data/messaging/bindings + +target/server1/data/messaging/journal + +target/server1/data/messaging/largemessages + +target/server1/data/messaging/paging + + ++ + + ++ +org.hornetq.core.remoting.impl.invm.InVMConnectorFactory ++ + +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + ++ +org.hornetq.core.remoting.impl.invm.InVMAcceptorFactory ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + +1 ++ +invm-connector ++ +invm-connector +server0-connector +netty-connector ++ + + + ++ jms + +netty-connector +500 +true +true +1 ++ +server0-connector ++ + + ++ ++ + + + + + + + + \ No newline at end of file diff --git a/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server1/hornetq-users.xml b/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server1/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/ha-policy-autobackup/src/main/resources/hornetq/server1/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ true + +1000 + + +1.0 + + +-1 ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/hornetq-jms-examples-common/common.css b/examples/jms/hornetq-jms-examples-common/common.css new file mode 100644 index 0000000000..333ea01bfd --- /dev/null +++ b/examples/jms/hornetq-jms-examples-common/common.css @@ -0,0 +1,29 @@ +body { + background: url(images/hornetQ-banner_final.png) top left no-repeat; +} + +h1 { + margin-top: 110px; + font-size: 250%; +} + +code { + background-color: lightgrey; + color:#333; +} + +pre { + background-color: lightgrey; + display:block; + overflow:auto; + border: dotted grey 1px; +} + +abbr { + border-bottom: 1px dotted #333; cursor: help; +} + +.missing-doc { + background-color: red; + border: dotted black 1px; +} diff --git a/examples/jms/hornetq-jms-examples-common/config/hornetq-example-beans.xml b/examples/jms/hornetq-jms-examples-common/config/hornetq-example-beans.xml new file mode 100644 index 0000000000..e70555a435 --- /dev/null +++ b/examples/jms/hornetq-jms-examples-common/config/hornetq-example-beans.xml @@ -0,0 +1,165 @@ + + ++ ++ + + \ No newline at end of file diff --git a/examples/jms/hornetq-jms-examples-common/config/logging.properties b/examples/jms/hornetq-jms-examples-common/config/logging.properties new file mode 100644 index 0000000000..85e6088f42 --- /dev/null +++ b/examples/jms/hornetq-jms-examples-common/config/logging.properties @@ -0,0 +1,35 @@ +############################################################ +# Default Logging Configuration File +# +# You can use a different file by specifying a filename +# with the java.util.logging.config.file system property. +# For example java -Djava.util.logging.config.file=myfile +############################################################ + +############################################################ +# Global properties +############################################################ + +# "handlers" specifies a comma separated list of log Handler +# classes. These handlers will be installed during VM startup. +# Note that these classes must be on the system classpath. +# By default we only configure a ConsoleHandler, which will only +# show messages at the INFO and above levels. +handlers=java.util.logging.ConsoleHandler +#handlers=java.util.logging.ConsoleHandler,java.util.logging.FileHandler +java.util.logging.ConsoleHandler.formatter=org.hornetq.integration.logging.HornetQLoggerFormatter +java.util.logging.FileHandler.level=INFO +java.util.logging.FileHandler.formatter=org.hornetq.integration.logging.HornetQLoggerFormatter +java.util.logging.FileHandler.pattern=logs/hornetq.log +# Default global logging level. +# This specifies which kinds of events are logged across +# all loggers. For any given facility this global level +# can be overriden by a facility specific level +# Note that the ConsoleHandler also has a separate level +# setting to limit messages printed to the console. +.level= INFO + +############################################################ +# Handler specific properties. +# Describes specific configuration info for Handlers. +############################################################ diff --git a/examples/jms/hornetq-jms-examples-common/config/server.properties b/examples/jms/hornetq-jms-examples-common/config/server.properties new file mode 100644 index 0000000000..0388e87151 --- /dev/null +++ b/examples/jms/hornetq-jms-examples-common/config/server.properties @@ -0,0 +1 @@ +server.args=-XX:+UseParallelGC -Xms256M -Xmx256M -XX:+AggressiveOpts -XX:+UseFastAccessorMethods -Dcom.sun.management.jmxremote -Djava.util.logging.config.file=${imported.basedir}/config/logging.properties -Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory -Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces \ No newline at end of file diff --git a/examples/jms/hornetq-jms-examples-common/images/hornetQ-banner_final.png b/examples/jms/hornetq-jms-examples-common/images/hornetQ-banner_final.png new file mode 100644 index 0000000000..6388dff1f5 Binary files /dev/null and b/examples/jms/hornetq-jms-examples-common/images/hornetQ-banner_final.png differ diff --git a/examples/jms/hornetq-jms-examples-common/pom.xml b/examples/jms/hornetq-jms-examples-common/pom.xml new file mode 100644 index 0000000000..90e28a3e9c --- /dev/null +++ b/examples/jms/hornetq-jms-examples-common/pom.xml @@ -0,0 +1,37 @@ ++ + + + + ++ ++ 1099 +localhost +1098 +localhost ++ + ++ + +5000 ++ + + + + + ++ + ++ ++ ++ + ++ + + +AddressSettingsDeployer +QueueDeployer + ++ ++ + ++ + ++ + ++ + ++ + + ++ ++ ++ + + ++ ++ ++ + ++ + + ++ ++ ++ + ++ + + ++ ++ ++ + ++ + ++ + + ++ ++ ++ + ++ + + ++ ++ ++ + ++ + + ++ ++ ++ + ++ + + ++ ++ ++ + ++ + + ++ ++ ++ + + ++ + \ No newline at end of file diff --git a/examples/jms/hornetq-jms-examples-common/prettify.css b/examples/jms/hornetq-jms-examples-common/prettify.css new file mode 100755 index 0000000000..0f1ed75995 --- /dev/null +++ b/examples/jms/hornetq-jms-examples-common/prettify.css @@ -0,0 +1 @@ +.str{color:#080}.kwd{color:#008}.com{color:#800}.typ{color:#606}.lit{color:#066}.pun{color:#660}.pln{color:#000}.tag{color:#008}.atn{color:#606}.atv{color:#080}.dec{color:#606}pre.prettyprint{padding:2px;border:1px solid #888}@media print{.str{color:#060}.kwd{color:#006;font-weight:bold}.com{color:#600;font-style:italic}.typ{color:#404;font-weight:bold}.lit{color:#044}.pun{color:#440}.pln{color:#000}.tag{color:#006;font-weight:bold}.atn{color:#404}.atv{color:#060}} \ No newline at end of file diff --git a/examples/jms/hornetq-jms-examples-common/prettify.js b/examples/jms/hornetq-jms-examples-common/prettify.js new file mode 100755 index 0000000000..8fc4c93393 --- /dev/null +++ b/examples/jms/hornetq-jms-examples-common/prettify.js @@ -0,0 +1,23 @@ +function H(){var x=navigator&&navigator.userAgent&&/\bMSIE 6\./.test(navigator.userAgent);H=function(){return x};return x}(function(){function x(b){b=b.split(/ /g);var a={};for(var c=b.length;--c>=0;){var d=b[c];if(d)a[d]=null}return a}var y="break continue do else for if return while ",U=y+"auto case char const default double enum extern float goto int long register short signed sizeof static struct switch typedef union unsigned void volatile ",D=U+"catch class delete false import new operator private protected public this throw true try ", +I=D+"alignof align_union asm axiom bool concept concept_map const_cast constexpr decltype dynamic_cast explicit export friend inline late_check mutable namespace nullptr reinterpret_cast static_assert static_cast template typeid typename typeof using virtual wchar_t where ",J=D+"boolean byte extends final finally implements import instanceof null native package strictfp super synchronized throws transient ",V=J+"as base by checked decimal delegate descending event fixed foreach from group implicit in interface internal into is lock object out override orderby params readonly ref sbyte sealed stackalloc string select uint ulong unchecked unsafe ushort var ", +K=D+"debugger eval export function get null set undefined var with Infinity NaN ",L="caller delete die do dump elsif eval exit foreach for goto if import last local my next no our print package redo require sub undef unless until use wantarray while BEGIN END ",M=y+"and as assert class def del elif except exec finally from global import in is lambda nonlocal not or pass print raise try with yield False True None ",N=y+"alias and begin case class def defined elsif end ensure false in module next nil not or redo rescue retry self super then true undef unless until when yield BEGIN END ", +O=y+"case done elif esac eval fi function in local set then until ",W=I+V+K+L+M+N+O;function X(b){return b>="a"&&b<="z"||b>="A"&&b<="Z"}function u(b,a,c,d){b.unshift(c,d||0);try{a.splice.apply(a,b)}finally{b.splice(0,2)}}var Y=(function(){var b=["!","!=","!==","#","%","%=","&","&&","&&=","&=","(","*","*=","+=",",","-=","->","/","/=",":","::",";","<","<<","<<=","<=","=","==","===",">",">=",">>",">>=",">>>",">>>=","?","@","[","^","^=","^^","^^=","{","|","|=","||","||=","~","break","case","continue", +"delete","do","else","finally","instanceof","return","throw","try","typeof"],a="(?:(?:(?:^|[^0-9.])\\.{1,3})|(?:(?:^|[^\\+])\\+)|(?:(?:^|[^\\-])-)";for(var c=0;c4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-examples-common +jar +HornetQ Examples common + ++ + ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ +org.hornetq +hornetq-commons +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} +'));F=!/=0;i-=" ".length)d.push(" ".substring(0,i));g=e+1;break; +case "\n":a=0;break;default:++a}}if(!d)return c;d.push(c.substring(g));return d.join("")}}var ja=/(?:[^<]+| + + + + diff --git a/examples/jms/http-transport/pom.xml b/examples/jms/http-transport/pom.xml new file mode 100644 index 0000000000..b8a500b999 --- /dev/null +++ b/examples/jms/http-transport/pom.xml @@ -0,0 +1,122 @@ +HornetQ 2.0 Resource Adapter +HornetQ 2.0 Resource Adapter + +Red Hat Middleware LLC +JMS 1.1 Server +1.0 + ++ + ++Copyright 2009 Red Hat, Inc. + Red Hat licenses this file to you under the Apache License, version + 2.0 (the "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + http://www.apache.org/licenses/LICENSE-2.0 + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied. See the License for the specific language governing + permissions and limitations under the License. + +true ++ +org.hornetq.ra.HornetQResourceAdapter ++ ++ The transport type. Multiple connectors can be configured by using a comma separated list, + i.e. org.hornetq.core.remoting.impl.invm.InVMConnectorFactory,org.hornetq.core.remoting.impl.invm.InVMConnectorFactory. + +ConnectorClassName +java.lang.String +org.hornetq.core.remoting.impl.invm.InVMConnectorFactory ++ + + +The transport configuration. These values must be in the form of key=val;key=val;, + if multiple connectors are used then each set must be separated by a comma i.e. host=host1;port=5445,host=host2;port=5446. + Each set of params maps to the connector classname specified. + +ConnectionParameters +java.lang.String +server-id=0 ++ + ++ +org.hornetq.ra.HornetQRAManagedConnectionFactory + ++ +The default session type +SessionDefaultType +java.lang.String +javax.jms.Queue ++ + +Try to obtain a lock within specified number of seconds; less than or equal to 0 disable this functionality +UseTryLock +java.lang.Integer +0 +org.hornetq.ra.HornetQRAConnectionFactory +org.hornetq.ra.HornetQRAConnectionFactoryImpl +javax.jms.Session +org.hornetq.ra.HornetQRASession +XATransaction ++ +BasicPassword +javax.resource.spi.security.PasswordCredential +false ++ + ++ ++ +javax.jms.MessageListener ++ +org.hornetq.ra.inflow.HornetQActivationSpec ++ +destination ++ \ No newline at end of file diff --git a/examples/jms/http-transport/readme.html b/examples/jms/http-transport/readme.html new file mode 100644 index 0000000000..a71937c57e --- /dev/null +++ b/examples/jms/http-transport/readme.html @@ -0,0 +1,115 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-http-transport-example +jar +HornetQ JMS Http Transport Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start ++ +start ++ ++ ++ +build.directory +${basedir}/target/ ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.HttpTransportExample ++ jnp://localhost:1099 + ++ +stop ++ +stop ++ ++ +org.hornetq.examples.jms +hornetq-jms-http-transport-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +${basedir}/target/classes/hornetq/server0 ++ ++ +build.directory +${basedir}/target/ +HornetQ JMS HTTP Transport Example + + + + + +JMS HTTP Example
+ +This example shows you how to configure HornetQ to use the HTTP protocol as its transport layer.
+ +HornetQ supports a variety of network protocols to be its underlying transport without any specific code change.
+ +This example is taken from the queue example without any code change. By changing the configuration file, one can get HornetQ working with HTTP transport.
+All you need to do is open the server0/hornetq-configuration.xml and enable HTTP like the following
+ + ++
+ ++ <connector name="netty-connector"> + <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class> + <param key="hornetq.remoting.netty.http-enabled" value="true" type="Boolean"/> + <param key="hornetq.remoting.netty.port" value="8080" type="Integer"/> + </connector> + + <!-- Acceptors --> + + <acceptor name="netty-acceptor"> + <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class> + <param key="hornetq.remoting.netty.port" value="8080" type="Integer"/> + </acceptor> ++Example step-by-step
+To run the example, simply type
+ +mvn verifyfrom this directory-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text message that we are going to send. +
- We send message to the queue +
- We create a JMS Message Consumer to receive the message. +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- The message arrives at the consumer. In this case we use a timeout of 5000 milliseconds but we could use a blocking 'receive()' +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+
+ +InitialContext initialContext = getContext();++
+ +Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");++
+ +ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");++
+ +connection = cf.createConnection();++
+ +Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);++
+ +MessageProducer messageProducer = session.createProducer(topic);++
+ +TextMessage message = session.createTextMessage("This is a text message");++
+ +messageProducer.send(message);++
+ +MessageConsumer messageConsumer = session.createConsumer(queue);++
+ +connection.start();++
+ +TextMessage messageReceived = (TextMessage) messageConsumer.receive(5000);++
+ + + +finally + { + if (initialContext != null) + { + initialContext.close(); + } + if (connection != null) + { + connection.close(); + } + }++ + diff --git a/examples/jms/http-transport/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/http-transport/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..678e7f5214 --- /dev/null +++ b/examples/jms/http-transport/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,19 @@ +${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + + ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + + ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + + ++ ++ + + + + + + + \ No newline at end of file diff --git a/examples/jms/http-transport/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/http-transport/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/http-transport/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/instantiate-connection-factory/pom.xml b/examples/jms/instantiate-connection-factory/pom.xml new file mode 100644 index 0000000000..5c078db72b --- /dev/null +++ b/examples/jms/instantiate-connection-factory/pom.xml @@ -0,0 +1,126 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/instantiate-connection-factory/readme.html b/examples/jms/instantiate-connection-factory/readme.html new file mode 100644 index 0000000000..59f63dbda7 --- /dev/null +++ b/examples/jms/instantiate-connection-factory/readme.html @@ -0,0 +1,118 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-instantiate-connection-factory-example +jar +HornetQ JMS Instantiate Connection Factory Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start ++ +start ++ ++ ++ +build.directory +${basedir}/target/ ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.InstantiateConnectionFactoryExample ++ jnp://localhost:1099 + ++ +stop ++ +stop ++ ++ +org.hornetq.examples.jms +hornetq-jms-instantiate-connection-factory-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +${basedir}/target/classes/hornetq/server0 +HornetQ JMS Instantiate Connection Factory Example + + + + + +JMS Instantiate Connection Factory Example
+ +Usually, JMS Objects such as ConnectionFactories, Queue and Topic instances are looked up from JNDI + before being used by the client code. This objects are called "administered objects" in JMS specification + terminology.
+However, in some cases a JNDI server may not be available or desired. To come to the rescue HornetQ + also supports the direct instantiation of these administered objects on the client side.
+This allows the full set of JMS functionality to be available without requiring a JNDI server!
+This example is very simple and based on the simple Queue example, however in this example we + instantiate the JMS Queue and ConnectionFactory objects directly.
+A wide variety of methods are available for instantiating ConnectionFactory objects. In this example + we use a simple method which just takes the server connection details so it knows where to make the + connection to.
+Other methods are available so all the connection factory parameters can be specified + including specifying UDP discovery so the client does not need hard-wired knowledge of where the servers + are that it wishes to connect to, or for specifying live-backup pairs of servers for failover.
+For more information on instantiating ConnectionFactories directly please consult the user manual and + javadoc.
+ +Example step-by-step
+To run the example, simply type
+ +mvn verifyfrom this directory-
+
- Instead of looking it up from JNDI we directly instantiate the JMS Queue object. We + pass in the name of the JMS Queue in the constructor. The actual JMS Queue must already be deployed on + the server. +
- Instantiate the TransportConfiguration object. The TransportConfiguration instance encapsulates + the connection details of the server we're connecting to. In this case we're using Netty as a transport, and + we're specifying to connect on port 5446. +
- Directly instantiate the JMS ConnectionFactory object using that TransportConfiguration. +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text message that we are going to send. +
- We send message to the queue +
- We create a JMS Message Consumer to receive the message. +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- The message arrives at the consumer. In this case we use a timeout of 5000 milliseconds but we could use a blocking 'receive()' +
- And finally, always remember to close your resources after use, in a
finallyblock.
+
+
+
+ ++ Queue queue = new HornetQQueue("exampleQueue");++
+ ++ Map++
+ ++ ConnectionFactory cf = HornetQJMSClient.createConnectionFactoryWithoutHA(transportConfiguration); +++
+ +connection = cf.createConnection();++
+ +Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);++
+ +MessageProducer messageProducer = session.createProducer(topic);++
+ +TextMessage message = session.createTextMessage("This is a text message");++
+ +messageProducer.send(message);++
+ +MessageConsumer messageConsumer = session.createConsumer(queue);++
+ +connection.start();++
+ +TextMessage messageReceived = (TextMessage) messageConsumer.receive(5000);++
+ + + +finally + { + if (connection != null) + { + connection.close(); + } + }++ + diff --git a/examples/jms/instantiate-connection-factory/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/instantiate-connection-factory/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..1802d08442 --- /dev/null +++ b/examples/jms/instantiate-connection-factory/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,10 @@ +${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory + ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory + ++ + + ++ ++ + + + + + + + + diff --git a/examples/jms/instantiate-connection-factory/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/instantiate-connection-factory/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/instantiate-connection-factory/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + ++ + + \ No newline at end of file diff --git a/examples/jms/interceptor/pom.xml b/examples/jms/interceptor/pom.xml new file mode 100644 index 0000000000..e8a2546ab4 --- /dev/null +++ b/examples/jms/interceptor/pom.xml @@ -0,0 +1,121 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/interceptor/readme.html b/examples/jms/interceptor/readme.html new file mode 100644 index 0000000000..f85e2872c1 --- /dev/null +++ b/examples/jms/interceptor/readme.html @@ -0,0 +1,157 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-interceptor-example +jar +HornetQ JMS Interceptor Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start ++ +start ++ ++ ++ +build.directory +${basedir}/target/ ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.InterceptorExample ++ jnp://localhost:1099 + ++ +stop ++ +stop ++ ++ +org.hornetq.examples.jms +hornetq-jms-interceptor-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +${basedir}/target/classes/hornetq/server0 +HornetQ JMS Interceptor Example + + + + + +JMS Interceptor Example
+ +This example shows you how to implement and configure a simple incoming, server-side interceptor with HornetQ.
+ +HornetQ allows an application to use an interceptor to hook into the messaging system. All that needs to do is to implement the + Interceptor interface, as defined below:
++
++ public interface Interceptor + { + boolean intercept(Packet packet, RemotingConnection connection) throws HornetQException; + } ++Once you have your own interceptor class, add it to the hornetq-configuration.xml, as follows:
++
+ ++ <configuration> + ... + <remoting-incoming-interceptors> + <class-name>org.hornetq.jms.example.SimpleInterceptor</class-name> + </remoting-incoming-interceptors> + ... + </configuration> ++With interceptor, you can handle various events in message processing. In this example, a simple interceptor, SimpleInterceptor, is implemented and configured. + When the example is running, the interceptor will print out each events that are passed in the interceptor. And it will add a string property to the message being + delivered. You can see that after the message is received, there will be a new string property appears in the received message.
+ +With our interceptor we always return
+ +truefrom theinterceptmethod. If we were + to returnfalsethat signifies that no more interceptors are to run or the target + is not to be called. Returnfalseto abort processing of the packet.Example step-by-step
+To run the example, simply type
+ +mvn verifyfrom this directory-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text message that we are going to send. +
- We send message to the queue +
- We create a JMS Message Consumer to receive the message. +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- The message arrives at the consumer. In this case we use a timeout of 5000 milliseconds but we could use a blocking 'receive()' +
- We print out the message and the new property that has been added by the interceptor +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+
+ +InitialContext initialContext = getContext(0);++
+ +Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");++
+ +ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");++
+ +connection = cf.createConnection();++
+ +Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);++
+ +MessageProducer messageProducer = session.createProducer(topic);++
+ +TextMessage message = session.createTextMessage("This is a text message");++
+ +messageProducer.send(message);++
+ +MessageConsumer messageConsumer = session.createConsumer(queue);++
+ +connection.start();++
+ +TextMessage messageReceived = (TextMessage) messageConsumer.receive(5000);++
+ +System.out.println("Received message [" + messageReceived.getText() + "] with String property: " + messageReceived.getStringProperty("newproperty"));++
++ finally + { + if (initialContext != null) + { + initialContext.close(); + } + if (connection != null) + { + connection.close(); + } + } ++-
+
- The SimpleInterceptor: +
+
++ public class SimpleInterceptor implements Interceptor + { + public boolean intercept(Packet packet, RemotingConnection connection) throws HornetQException + { + System.out.println("SimpleInterceptor gets called!"); + System.out.println("Packet: " + packet.getClass().getName()); + System.out.println("RemotingConnection: " + connection.getRemoteAddress()); + + if (packet instanceof SessionSendMessage) + { + SessionSendMessage realPacket = (SessionSendMessage)packet; + Message msg = realPacket.getServerMessage(); + msg.putStringProperty(new SimpleString("newproperty"), new SimpleString("Hello from interceptor!")); + } + return true; + } + } +++ + diff --git a/examples/jms/interceptor/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/interceptor/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..71b83dd96f --- /dev/null +++ b/examples/jms/interceptor/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,19 @@ +${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + ++ + + + +org.hornetq.jms.example.SimpleInterceptor ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory ++ + + ++ ++ + + + + + + + diff --git a/examples/jms/interceptor/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/interceptor/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/interceptor/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/jaas/pom.xml b/examples/jms/jaas/pom.xml new file mode 100644 index 0000000000..a8093974b1 --- /dev/null +++ b/examples/jms/jaas/pom.xml @@ -0,0 +1,139 @@ ++ ++ + \ No newline at end of file diff --git a/examples/jms/jaas/readme.html b/examples/jms/jaas/readme.html new file mode 100644 index 0000000000..0fef5c55fa --- /dev/null +++ b/examples/jms/jaas/readme.html @@ -0,0 +1,98 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-jaas-example +jar +HornetQ JMS "JAAS" Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin +1.1.0 ++ ++ +start ++ +start ++ ++ +org.hornetq.jms.example.ExampleLoginModule ++ + +org.hornetq.jms.example.ExampleLoginModule ++ +jboss +redhat +guest ++ ++ +build.directory +${basedir}/target/ ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.JAASExample ++ jnp://localhost:1099 + ++ +stop ++ +stop ++ ++ +org.hornetq.examples.jms +hornetq-jms-jaas-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +${basedir}/target/classes/hornetq/server0 +HornetQ JAAS Example + + + + + +JAAS Example
+ +This example shows you how to configure HornetQ to use JAAS for security.
+HornetQ can leverage JAAS to delegate user authentication and authorization to existing security infrastructure.
+ ++ The example will show how to configure HornetQ with JAAS in hornetq-beans.xml + (You would use
+hornetq-jboss-beans.xml if you are running inside JBoss Application + Server). + It will use a simpleLoginModulewithout any user interaction. + The example will create a connection and authenticate the user with this JAAS LoginModule, send a message + to a queue and receive it (see the Queue example for a complete description + of the application code) +Note than the example actually sets the security manager via the maven pom.xml, however for we will discuss as if + the hornetq-beans.xml is being configured, the example beans file can be found under the
+src/main/resources+ directoryExample setup
+HornetQ can use a JAAS security manager by specifying it in hornetq-beans.xml:
++ <!-- The security manager using JAAS --> + <bean name="HornetQSecurityManager" class="org.hornetq.integration.jboss.security.JAASSecurityManager"> + <property name="configurationName">org.hornetq.jms.example.ExampleLoginModule</property> + <property name="configuration"> + <inject bean="ExampleConfiguration"/> + </property> + <property name="callbackHandler"> + <inject bean="ExampleCallbackHandler" /> + </property> + </bean> + + <!-- JAAS uses a simple LoginModule where the user credentials and roles are + specified as options in the constructor --> + <bean name="ExampleConfiguration" class="org.hornetq.jms.example.ExampleConfiguration"> + <constructor> + <parameter>org.hornetq.jms.example.ExampleLoginModule</parameter> + <parameter> + <map class="java.util.HashMap" keyClass="java.lang.String" + valueClass="java.lang.String"> + <entry> + <key>user</key> + <value>jboss</value> + </entry> + <entry> + <key>pass</key> + <value>redhat</value> + </entry> + <entry> + <key>role</key> + <value>guest</value> + </entry> + </map> + </parameter> + </constructor> + </bean> + + <!-- the CallbackHandler does nothing as we don't have any user interaction --> + <bean name="ExampleCallbackHandler" class="org.hornetq.jms.example.ExampleCallbackHandler" + /> +
+ +-
+
- the HornetQSecurityManager's
configurationNamemust be the name of the Java class implementingLoginModule
+ - the
callbackHandlerproperty must be an implementation ofCallbackHandler. In this example, the ExampleCallbackHandler + does nothing since the authentication requires no user interaction
+ - the
configurationproperty must be an implementation ofConfiguration. For simplicity, we pass directly the + user credentials as options to theExampleConfigurationconstructor. These options will be passed to an instance + of ExampleLoginModule which will check that the only valid user is "jboss" with the password "redhat" + and it has the role "guest".
+
Example step-by-step
+To run the example, simply type
+mvn verifyfrom this directoryThe only relevant step with regard to JAAS configuration is step 4 (all the other + steps are identical to the Queue example). +
-
+
- We create a JMS Connection with user "jboss" and password "redhat". Any other + combination of name and password won't be valid for the ExampleLoginModule +
+
+connection = cf.createConnection("jboss", "redhat");+More information
+ +-
+
- User Manual's Security chapter +
iterator2 = subject.getPrincipals().iterator(); + System.out.println("subject = " + subject); + String user = iterator2.next().getName(); + + boolean authenticated = user.equals(options.get("user")) && password.equals(options.get("pass")); + + if (authenticated) + { + Group roles = new SimpleGroup("Roles"); + roles.addMember(new JAASSecurityManager.SimplePrincipal((String)options.get("role"))); + subject.getPrincipals().add(roles); + } + System.out.format("JAAS authentication >>> user=%s, password=%s\n", user, password); + System.out.println("authenticated = " + authenticated); + return authenticated; + + } + + public Subject getSubject() + { + return subject; + } + + public boolean logout() throws LoginException + { + return true; + } + + public class SimpleGroup implements Group + { + private final String name; + + private final Set members = new HashSet (); + + public SimpleGroup(final String name) + { + this.name = name; + } + + public boolean addMember(final Principal principal) + { + return members.add(principal); + } + + public boolean isMember(final Principal principal) + { + return members.contains(principal); + } + + public Enumeration members() + { + return Collections.enumeration(members); + } + + public boolean removeMember(final Principal principal) + { + return members.remove(principal); + } + + public String getName() + { + return name; + } + } + +} diff --git a/examples/jms/jaas/src/main/java/org/hornetq/jms/example/JAASExample.java b/examples/jms/jaas/src/main/java/org/hornetq/jms/example/JAASExample.java new file mode 100644 index 0000000000..56d2e126df --- /dev/null +++ b/examples/jms/jaas/src/main/java/org/hornetq/jms/example/JAASExample.java @@ -0,0 +1,99 @@ +/* + * Copyright 2005-2014 Red Hat, Inc. + * Red Hat licenses this file to you under the Apache License, version + * 2.0 (the "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * http://www.apache.org/licenses/LICENSE-2.0 + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + * implied. See the License for the specific language governing + * permissions and limitations under the License. + */ +package org.hornetq.jms.example; + +import javax.jms.Connection; +import javax.jms.ConnectionFactory; +import javax.jms.MessageConsumer; +import javax.jms.MessageProducer; +import javax.jms.Queue; +import javax.jms.Session; +import javax.jms.TextMessage; +import javax.naming.InitialContext; + +import org.hornetq.common.example.HornetQExample; + +/** + * A simple JMS Queue example that creates a producer and consumer on a queue and sends then receives a message. + * The HornetQ server is configured to use JAAS. + * + * @author Jeff Mesnil + */ +public class JAASExample extends HornetQExample +{ + public static void main(final String[] args) + { + new JAASExample().run(args); + } + + @Override + public boolean runExample() throws Exception + { + Connection connection = null; + InitialContext initialContext = null; + try + { + // Step 1. Create an initial context to perform the JNDI lookup. + initialContext = getContext(0); + + // Step 2. Perfom a lookup on the queue + Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue"); + + // Step 3. Perform a lookup on the Connection Factory + ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory"); + + // Step 4.Create a JMS Connection with user "jboss" and password "redhat" + connection = cf.createConnection("jboss", "redhat"); + + // Step 5. Create a JMS Session + Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); + + // Step 6. Create a JMS Message Producer + MessageProducer producer = session.createProducer(queue); + + // Step 7. Create a Text Message + TextMessage message = session.createTextMessage("This is a text message"); + + System.out.println("Sent message: " + message.getText()); + + // Step 8. Send the Message + producer.send(message); + + // Step 9. Create a JMS Message Consumer + MessageConsumer messageConsumer = session.createConsumer(queue); + + // Step 10. Start the Connection + connection.start(); + + // Step 11. Receive the message + TextMessage messageReceived = (TextMessage)messageConsumer.receive(5000); + + System.out.println("Received message: " + messageReceived.getText()); + + return true; + } + finally + { + // Step 12. Be sure to close our JMS resources! + if (initialContext != null) + { + initialContext.close(); + } + if (connection != null) + { + connection.close(); + } + } + } + +} diff --git a/examples/jms/jaas/src/main/resources/hornetq/server0/hornetq-configuration.xml b/examples/jms/jaas/src/main/resources/hornetq/server0/hornetq-configuration.xml new file mode 100644 index 0000000000..b71c85fcaa --- /dev/null +++ b/examples/jms/jaas/src/main/resources/hornetq/server0/hornetq-configuration.xml @@ -0,0 +1,43 @@ + + + diff --git a/examples/jms/jaas/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/jaas/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..71b83dd96f --- /dev/null +++ b/examples/jms/jaas/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,19 @@ +${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory ++ + + ++ ++ + + + + + + + diff --git a/examples/jms/jms-auto-closeable/pom.xml b/examples/jms/jms-auto-closeable/pom.xml new file mode 100644 index 0000000000..2d24528eb3 --- /dev/null +++ b/examples/jms/jms-auto-closeable/pom.xml @@ -0,0 +1,116 @@ ++ + + ++ ++ + ++ + + ++ + \ No newline at end of file diff --git a/examples/jms/jms-auto-closeable/readme.html b/examples/jms/jms-auto-closeable/readme.html new file mode 100644 index 0000000000..cc92549e4a --- /dev/null +++ b/examples/jms/jms-auto-closeable/readme.html @@ -0,0 +1,76 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-auto-closeable-example +jar +HornetQ JMS Auto Closable Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start ++ +start ++ ++ ++ +build.directory +${basedir}/target/ ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.JMSAutoCloseableExample ++ jnp://localhost:1099 + ++ +stop ++ +stop ++ ++ +org.hornetq.examples.jms +hornetq-jms-auto-closeable-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false +${basedir}/target/classes/hornetq/server0 +HornetQ JMS Auto Closable Example + + + + + +JMS Auto Closable Example
+ +This example shows you how JMS resources, such as connections, sessions and consumers, in JMS 2 can be automatically closed on error.
+In this instance we auto close a connection after a subsequent call to a JMS producer send fails
+ +Example step-by-step
+To run the example, simply type
+ +mvn verifyfrom this directory-
+
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS context but we do it inside the try-with-resources statement like so: +
- Inside the following try block we first create the producer +
- We then try to send a message. It is this call that throws an exception as the producer doesn't have the privileges + to send a message +
- We catch the exception from the send message and can do what we want, however the JMSContext will have been closed + prior to entering the catch block. +
- And finally, we close the Initial Context, note we no longer have to worry about clearing up the JMSContext. + +
+
+ +InitialContext initialContext = getContext();++
+ +Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");++
+ +ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");++
+ ++ try + ( + JMSContext jmsContext = cf.createContext() + ) +++
+ +JMSProducer jmsProducer = jmsContext.createProducer();++
+ +jmsProducer.send(queue, "this message will fail security!");++
+ +System.out.println("expected exception from jmsProducer.send: " + e.getMessage());++
+ + + +finally + { + if (initialContext != null) + { + initialContext.close(); + } + }++ + diff --git a/examples/jms/jms-auto-closeable/src/main/resources/hornetq/server0/hornetq-jms.xml b/examples/jms/jms-auto-closeable/src/main/resources/hornetq/server0/hornetq-jms.xml new file mode 100644 index 0000000000..71b83dd96f --- /dev/null +++ b/examples/jms/jms-auto-closeable/src/main/resources/hornetq/server0/hornetq-jms.xml @@ -0,0 +1,19 @@ +${build.directory}/server0/data/messaging/bindings + +${build.directory}/server0/data/messaging/journal + +${build.directory}/server0/data/messaging/largemessages + +${build.directory}/server0/data/messaging/paging + + + + ++ + + ++ +org.hornetq.core.remoting.impl.netty.NettyConnectorFactory ++ + + + ++ +org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory ++ + + ++ ++ + + + + + + diff --git a/examples/jms/jms-auto-closeable/src/main/resources/hornetq/server0/hornetq-users.xml b/examples/jms/jms-auto-closeable/src/main/resources/hornetq/server0/hornetq-users.xml new file mode 100644 index 0000000000..934306c4b5 --- /dev/null +++ b/examples/jms/jms-auto-closeable/src/main/resources/hornetq/server0/hornetq-users.xml @@ -0,0 +1,7 @@ ++ + + ++ ++ + ++ + + ++ + + \ No newline at end of file diff --git a/examples/jms/jms-bridge/jms-bridge.png b/examples/jms/jms-bridge/jms-bridge.png new file mode 100644 index 0000000000..d671bf34b0 Binary files /dev/null and b/examples/jms/jms-bridge/jms-bridge.png differ diff --git a/examples/jms/jms-bridge/pom.xml b/examples/jms/jms-bridge/pom.xml new file mode 100644 index 0000000000..50f695b9d7 --- /dev/null +++ b/examples/jms/jms-bridge/pom.xml @@ -0,0 +1,165 @@ ++ ++ + diff --git a/examples/jms/jms-bridge/readme.html b/examples/jms/jms-bridge/readme.html new file mode 100644 index 0000000000..2d6b8b196b --- /dev/null +++ b/examples/jms/jms-bridge/readme.html @@ -0,0 +1,220 @@ + + +4.0.0 + ++ + +org.hornetq.examples.jms +jms-examples +2.5.0-SNAPSHOT +hornetq-jms-jms-bridge-example +jar +HornetQ JMS Bridge Example + ++ + ++ +org.hornetq.examples.jms +hornetq-jms-examples-common +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +org.hornetq +hornetq-jboss-as-integration +${project.version} ++ +org.jboss +jboss-transaction-spi ++ +org.jboss.jbossts.jts +jbossjts-jacorb ++ +org.jboss.spec.javax.jms +jboss-jms-api_2.0_spec ++ + ++ ++ +org.hornetq +hornetq-maven-plugin ++ ++ +start0 ++ +start ++ +${basedir}/target/classes/hornetq/server0 ++ +start1 ++ +start ++ +1199 +1198 +${basedir}/target/classes/hornetq/server1 +true ++ +runClient ++ +runClient ++ +org.hornetq.jms.example.JMSBridgeExample ++ jnp://localhost:1099 + jnp://localhost:1199 + ++ ++ +exampleConfigDir +${basedir}/target/classes/hornetq ++ +stop0 ++ +stop ++ +${basedir}/target/classes/hornetq/server0 ++ +stop1 ++ +stop ++ +${basedir}/target/classes/hornetq/server1 ++ ++ +org.hornetq.examples.jms +hornetq-jms-jms-bridge-example +${project.version} ++ +org.hornetq +hornetq-core-client +${project.version} ++ +org.hornetq +hornetq-server +${project.version} ++ +org.hornetq +hornetq-jms-client +${project.version} ++ +org.hornetq +hornetq-jms-server +${project.version} ++ +io.netty +netty-all +${netty.version} ++ +org.jboss.javaee +jboss-jms-api +1.1.0.GA ++ +org.jboss.naming +jnpserver +5.0.3.GA ++ +false ++ ++ +build.directory +${basedir}/target/ +HornetQ JMS Bridge Example + + + + + +JMS Bridge Example
+This example shows you how to create a JMS Bridge between two HornetQ servers.
+
+ The example will use two HornetQ servers:
+-
+
- Server #0 – the Source server. It will be configured with a JMS Topic bound to JNDI under
/source/topic+ - Server #1 – the Target server. It will be configured with a JMS Queue bound to JNDI under
/target/queue
+
Both HornetQ server will run their own JNDI server used by the JMS Bridge and the JMS Client to lookup JMS + resources (ConnectionFactory and Destination).
+The JMS Bridge will be started in the example code and be configured to bridge messages from the source destination + (the topic hosted on server #0) and the target destination (the queue hosted on server #1)
+The client will check the bridge works by:
+-
+
- sending a message to the source topic +
- receive a message from the target queue +
- check that both messages correspond to the same content. +
JMS Bridge Configuration
+The JMS Bridge is a POJO that we configure with both source and target + JNDI configurations. In the actual example we are programatically creating the Bridge, however the following section + describes how you would do this if you wanted to deploy with an actual HornetQ server via the hornetq-beans.xml. + +
Configuring the Bridge with the JBoss Microcontainer
++ in which we inject JNDI configurations + so that it looks up its source and target JMS resources. + The JMS Bridge is defined a bean and setup by JBoss Microntainer in the same VM than Server #1, the target server.
+ + The JMS Bridge sample configuration can be found inresources/hornetq-beans.xml, firstly we define the + Bridge itself: ++ <!-- The JMS Bridge --> + <bean name="JMSBridge" class="org.hornetq.jms.bridge.impl.JMSBridgeImpl"> + ... + </bean> +
+the
+JMSBridgeImplconstructor is used to inject all the properties required to run the JMS Bridge.Its first four arguments defines how the bridge will lookup:
+-
+
- its source JMS ConnectionFactory +
- its source JMS Destination +
- its target JMS ConnectionFactory +
- its target JMS Destination +
Using other POJOs, the JMS Bridge is configured to retrieve:
+-
+
- its source JMS ConnectionFactory by looking up
/source/ConnectionFactoryusing + theSourceJNDIconfiguration
+ - its source JMS Destination by looking up
/source/topicusing + theSourceJNDIconfiguration
+ - its target JMS ConnectionFactory by looking up
/target/ConnectionFactoryusing + theTargetJNDIconfiguration
+ - its target JMS ConnectionFactory by looking up
/target/queueusing + theTargetJNDIconfiguration
+
In turn,
+SourceJNDIandTargetJNDIare POJOs defining how to connect to JNDI server. + SourceJNDI URL must point to your source server, while LocalJNDI must point to your target server:+ <bean name="SourceJNDI" class="java.util.Hashtable"> + ... + <entry> + <key>java.naming.provider.url</key> + <!-- **************************************** --> + <!-- Replace with the *source* server address --> + <!-- **************************************** --> + <value>jnp://192.168.0.10:1099</value> + ... + </bean> + <bean name="TargetJNDI" class="java.util.Hashtable"> + ... + <ntry> + <key>java.naming.provider.url</key> + <!-- **************************************** --> + <!-- Replace with the *target* server address --> + <!-- **************************************** --> + <value>jnp://1192.168.0.11:1099</value> + </entry> + ... + </bean> +
+Example step-by-step
+To run the example after having setup both HornetQ servers and the JMS bridge:
+-
+
- To run the example simply run
mvn verify
+
Let's look at the Client code (in
+JMSBridgeExampleclass):-
+
- First we need to get an initial context so we can look-up the JMS resources +
- We then create a JMS Bridge and start it, Note, the Bridge needs a transaction manager, in this instance we will use the JBoss TM +
- We look up the JMS resources from the Source server +
- We create JMS objects to send a message to the source destination +
- We send a message to the source destination +
- We close the connection to the source server +
- We look up the JMS resources from the target server +
- We create JMS objects to receive a message from the target destination +
- We start the target connection to start receiving messages
+
+ targetConnection.start(); +
+ + - We receive the message and print it. Its content is the same than the message + the client sent to the source topic +
- We display the message ID and its "bridged" message ID +
- And finally, we stop the Bridge and always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+
+ InitialContext sourceContext = createContext(sourceServer); + InitialContext targetContext = createContext(targetServer); +
++ JMSBridge jmsBridge = new JMSBridgeImpl( + new JNDIConnectionFactoryFactory(sourceJndiParams, "/source/ConnectionFactory"), + new JNDIConnectionFactoryFactory(targetJndiParams, "/target/ConnectionFactory"), + new JNDIDestinationFactory(sourceJndiParams, "/source/topic"), + new JNDIDestinationFactory(targetJndiParams, "/target/queue"), + null, + null, + null, + null, + null, + 5000, + 10, + QualityOfServiceMode.ONCE_AND_ONLY_ONCE, + 1, + -1, + null, + null, + true); + jmsBridge.setTransactionManager(new TransactionManagerImple()); + .... + jmsBridge.start(); +
++ ConnectionFactory sourceConnectionFactory = (ConnectionFactory)sourceContext.lookup("/source/ConnectionFactory"); + Topic sourceTopic = (Topic)sourceContext.lookup("/source/topic"); ++ ++ sourceConnection = sourceConnectionFactory.createConnection(); + Session sourceSession = sourceConnection.createSession(false, Session.AUTO_ACKNOWLEDGE); + MessageProducer sourceProducer = sourceSession.createProducer(sourceTopic); +
+ ++ TextMessage message = sourceSession.createTextMessage("this is a text message sent at " + System.currentTimeMillis()); + sourceProducer.send(message); ++ ++ sourceConnection.close(); +
+ +At this point, the JMS Bridge will consume the message from the source topic and + sends it to the target queue. + The client will check the bridge works by consuming a message from the target queue.
+ ++ ConnectionFactory targetConnectionFactory = (ConnectionFactory)targetContext.lookup("/target/ConnectionFactory"); + Queue targetQueue = (Queue)targetContext.lookup("/target/queue"); ++ ++ targetConnection = targetConnectionFactory.createConnection(); + Session targetSession = targetConnection.createSession(false, Session.AUTO_ACKNOWLEDGE); + MessageConsumer targetConsumer = targetSession.createConsumer(targetQueue); +
+ ++ TextMessage messageReceived = (TextMessage)targetConsumer.receive(5000); +
+ ++ System.out.format("Message ID : %s\n", messageReceived.getJMSMessageID()); + System.out.format("Bridged Message ID : %s\n", messageReceived.getStringProperty("HQ_BRIDGE_MSG_ID_LIST")); ++ +Note that the message received from the target queue is not the same message sent to the source topic + (their message IDs are different) but they have the same content. + +
+
+ + + +finally + { + if (jmsBridge != null) + { + jmsBridge.stop(); + } + if (initialContext != null) + { + initialContext.close(); + } + if (connection != null) + { + connection.close(); + } + }+More information
+ +-
+
- User Manual's JMS Bridge chapter +
- The Java EE JMS Bridge example shows how to configure a JMS Bridge + inside JBoss Application Server to bridge destinations from the same server.
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS context +
- We create a JMS Producer. +
- We set a CompletionListener on the Producer +
- We send a message +
- and then wait for the Completion Listener to be called +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS context +
- We create a JMS Producer, set the delivery mode and send a message all in one line. Note that we don't pass + a message to the send method but just a String. +
- We create a JMS message consumer and receive the payload of the message directly +
- We create a JMS text message that we are going to send. +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS topic object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS context +
- We create a JMS Producer. +
- We create a shared consumer using the subscription name
sc1
+ - We then create a second JMS context for a second shared consumer +
- we then create the second shared consumer using the same subscription name +
- we then send 2 messages +
- we then receive the 2 messages using both shared consumers +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get its properties from client-jndi.properties +
- We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text message that we are going to send. +
- We send message to the queue +
- We retrieve the
ObjectNamecorresponding to the queue using a helper classObjectNameBuilder
+ - We create a JMX Connector to connect to the server's MBeanServer using the standard JMX service URL +
- We retrieve a
MBeanServerConnectionfrom the JMX connector
+ - We create a
JMSQueueControlproxy to manage the queue on the server
+ - We use this mbean proxy to retrieve the number of messages in the queue using the
getMessageCountmethod
+ - We will now remove the message sent at step 8 using the
removeMessagemethod with the JMS Message ID of the message
+ - We use again the mbean proxy to retrieve the number of messages. This time, it will display
0messages
+ - Now we have finish the management operations, we close the JMX connector +
- We create a JMS message consumer on the queue +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- We try to receive a message from the queue. Since there is none, the call will timeout after 5000ms and messageReceived will be null + +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - User Manual's Using Management Via JMX chapter +
- Java 5 Management guide +
- Create an initial context to perform the JNDI lookup. +
- Perfom a lookup on the queue. +
- Perform a lookup on the Connection Factory. This ConnectionFactory has a special attribute set on it. hornetq-jms.xml) + Messages with more than 10K are considered large. +
- Create the JMS objects for sending the message. +
- Create a huge file - this will form the body of the message we will send. +
- Create a BytesMessage +
- We set the InputStream on the message. When sending the message will read the InputStream + until it gets EOF. In this case we point the InputStream at a file on disk, and it will suck up the entire + file, however we could use any InputStream not just a FileInputStream. +
- Send the Message. +
- We send message to the queue. After the send completion the message file will be located at ./build/data/largeMessages +
- + To demonstrate that that we're not simply streaming the message from sending to consumer, we stop + the server and restart it before consuming the message. This demonstrates that the large message gets persisted, like a + normal persistent message, on the server. If you look at ./build/data/largeMessages you will see the largeMessage + stored on disk the server. + +
- Now the server is restarted we can recreate the JMS Objects, and start the new connection. +
- Receive the message. When we receive the large message we initially just receive the message with + an empty body. +
- We set an OutputStream on the message. This causes the message body to be written to the + OutputStream until there are no more bytes to be written. + You don't have to use a FileOutputStream, you can use any OutputStream. + You may choose to use the regular BytesMessage or + StreamMessage interface but this method is much faster for large messages. +
- This will save the stream and wait until the entire message is written before continuing. +
- Be sure to close our resources! + +
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the client-jndi.properties +
- We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection, a session and a producer for the queue +
- We will create and send a text message with the Last-Value property set to
STOCK_NAME
+ - We will create and send a second text message with the Last-Value property set to
STOCK_NAME
+ - We will create and send a third text message with the Last-Value property set to
STOCK_NAME
+ - We will browse the queue. There will be a single message displayed: the 3rd message +
- We create a JMS message consumer on the queue +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- We try to receive a message from the queue. It will be the 3rd message +
- We will try to receive another message but there is no other on the queue. The
receivemethod will timeout after 5 seconds
+ - And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+ - User Manual's Last-Value Queues chapter +
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get its properties from client-jndi.properties +
- We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection, a session and a message producer for the example queue +
- We look up the JMS Topic used to receive the notifications from JNDI +
- We create a MessageConsumer for the notification queue and set its MessageListener. When a notification is received, we will simply display all the message properties +
- We start the connection to receive messages +
- We create a JMS message consumer on the example queue +
- We close this consumer +
- As a last example, we will create a connection with invalid user credentials +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - User Manual's Management Notifications chapter +
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get its properties from client-jndi.properties +
- We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text message that we are going to send. +
- We send message to the queue +
- We create the JMS management queue. This is a special queue which is not looked up from JNDI but instantiated directly +
- We create a
QueueRequestorto send messages to the management queue and receive replies (see queue-requestor example)
+ - We start the connection to receive replies on the requestor +
- We create a JMS message which will be used as a management message +
- a management message has well-defined properties that HornetQ server needs to know to perform management operations.
+ We use a helper classJMSManagementHelperto fill these properties: +-
+
- The name of the resource to manage
jms.queue.exampleQueue+ (i.e.jms.queuefollowed by the name of the queue as defined in hornetq-jms.xml)
+ - In our case, the name of the attribute to retrieve
MessageCount
+
+ - The name of the resource to manage
- We send the management message using the requestor and wait for a reply +
- We use a helper class
JMSManagementHelperto retrieve the result from the reply message: ++
+ +int messageCount = (Integer)JMSManagementHelper.getResult(reply); + System.out.println(queue.getQueueName() + " contains " + messageCount + " messages");+ - We create another JMS message to use as a management message +
- This time, we fill the management message with properties to invoke a management operation on the queue
+
-
+
- the name of the resource
jms.queue.exampleQueue
+ - the name of the management operation
removeMessage
+ - any parameters required to invoke the management operations (in our case, the JMS Message ID of the message sent in step 8) +
+ - the name of the resource
- Again, we use the requestor to send the management message and wait for a reply +
- We use the helper class to check that the operation was successfully invoked on the server +
- We use a helper class
JMSManagementHelperto retrieve the result from the reply message: + (in our case, theremoveMessagemethod returns a boolean)
+ - We create a JMS message consumer on the queue +
- We try to receive a message from the queue. Since there is none, the call will timeout after 5000ms and messageReceived will be null + +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - User Manual's Using Management Via JMS chapter +
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look up the JMS queue object from JNDI +
- We look up the JMS connection factory object from JNDI +
- We create a JMS connection, session and producer for the queue +
- We create and send a JMS text message +
- We will now sleep a little bit to be sure the queue is sample. Since we have configure the sample period to be 2 seconds, + we will sleep for 3 seconds to be sure that a sample is taken +
- We retrieve the JMX MBean used to manage the JMS queue +
- We retrieve the message counter and display them. MessageCounters are retrieved as
JSON Stringsfor portability reason (whether + JMX is used for management or JMS messages). To make it simpler to use them in the code, there is aMessageCounterInfodata structure.
+ - We display the message counters +
- We sleep again to have the queue sampled +
- We list the message counters again +
- We create a consumer for the queue +
- We start the connection to receive messages on the consumer +
- We receive a message from the queue +
- We sleep one last time to have the queue sampled +
- We list the message counters a final time (this time with no message in the queue) +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - User Manual's Message Counters chapter +
- MessageCounterInfo is a helper class used + to create a MessageCounterInfo object from the JSON String which represents message counters + + diff --git a/examples/jms/message-counters/src/main/java/org/hornetq/jms/example/MessageCounterExample.java b/examples/jms/message-counters/src/main/java/org/hornetq/jms/example/MessageCounterExample.java new file mode 100644 index 0000000000..36fed5ac18 --- /dev/null +++ b/examples/jms/message-counters/src/main/java/org/hornetq/jms/example/MessageCounterExample.java @@ -0,0 +1,156 @@ +/* + * Copyright 2005-2014 Red Hat, Inc. + * Red Hat licenses this file to you under the Apache License, version + * 2.0 (the "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * http://www.apache.org/licenses/LICENSE-2.0 + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + * implied. See the License for the specific language governing + * permissions and limitations under the License. + */ +package org.hornetq.jms.example; + +import java.util.HashMap; + +import javax.jms.MessageConsumer; +import javax.jms.MessageProducer; +import javax.jms.Queue; +import javax.jms.QueueConnection; +import javax.jms.QueueConnectionFactory; +import javax.jms.QueueSession; +import javax.jms.Session; +import javax.jms.TextMessage; +import javax.management.MBeanServerConnection; +import javax.management.MBeanServerInvocationHandler; +import javax.management.ObjectName; +import javax.management.remote.JMXConnector; +import javax.management.remote.JMXConnectorFactory; +import javax.management.remote.JMXServiceURL; +import javax.naming.InitialContext; + +import org.hornetq.api.core.management.MessageCounterInfo; +import org.hornetq.api.core.management.ObjectNameBuilder; +import org.hornetq.api.jms.management.JMSQueueControl; +import org.hornetq.common.example.HornetQExample; + +/** + * An example showing how to use message counters to have information on a queue. + * + * @author Jeff Mesnil + * + */ +public class MessageCounterExample extends HornetQExample +{ + private static final String JMX_URL = "service:jmx:rmi:///jndi/rmi://localhost:3001/jmxrmi"; + + public static void main(final String[] args) + { + new MessageCounterExample().run(args); + } + + @Override + public boolean runExample() throws Exception + { + QueueConnection connection = null; + InitialContext initialContext = null; + try + { + // Step 1. Create an initial context to perform the JNDI lookup. + initialContext = getContext(0); + + // Step 2. Perfom a lookup on the queue + Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue"); + + // Step 3. Perform a lookup on the Connection Factory + QueueConnectionFactory cf = (QueueConnectionFactory)initialContext.lookup("/ConnectionFactory"); + + // Step 4.Create a JMS Connection, session and a producer for the queue + connection = cf.createQueueConnection(); + QueueSession session = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); + MessageProducer producer = session.createProducer(queue); + + // Step 5. Create and send a Text Message + TextMessage message = session.createTextMessage("This is a text message"); + producer.send(message); + System.out.println("Sent message: " + message.getText()); + + // Step 6. Sleep a little bit so that the queue is sampled + System.out.println("Sleep a little bit to have the queue sampled..."); + Thread.sleep(3000); + + // Step 7. Use JMX to retrieve the message counters using the JMSQueueControl + ObjectName on = ObjectNameBuilder.DEFAULT.getJMSQueueObjectName(queue.getQueueName()); + JMXConnector connector = + JMXConnectorFactory.connect(new JMXServiceURL(JMX_URL), new HashMap
- Messages in a message group share the same group id, i.e. they have same JMSXGroupID string property values. +
- Messages in a message group will be all delivered to no more than one of the queue's consumers. The consumer that receives the + first message of a group will receive all the messages that belong to the group. + +
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create two consumers. +
- We create and send 10 text messages with group id 'Group-0' +
- We start the connection. +
- We check the group messages are received by only one consumer +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - User Manual's Message Grouping chapter +
- Messages in a message group share the same group id, i.e. they have same JMSXGroupID string property values. +
- Messages in a message group will be all delivered to no more than one of the queue's consumers. The consumer that receives the + first message of a group will receive all the messages that belongs to the group. + +
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create 2 JMS message producers on the session. This will be used to send the messages. +
- We create two consumers. +
- We create and send 10 text messages using each producer +
- We start the connection. +
- We check the group messages are received by only one consumer +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - User Manual's Message Grouping chapter +
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We Create a JMS Message Consumer. +
- We Create three messages. +
- Send the Messages, each has a different priority. +
- We start the connection now. +
- We wait for message delivery completion +
- We wait for message delivery completion +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - Create an initial context to perform the JNDI lookup. +
- Perfom a lookup on the queue +
- Perform a lookup on the Connection Factory +
- Create a JMS Connection +
- Create a JMS Session +
- Create a JMS MessageProducer +
- Create a JMS MessageConsumer +
- Start the connection + +
- Send 10 messages to the queue +
- Create another JMS MessageConsumer on the same queue. +
- Consume three messages from consumer2 + +
- Consume five messages from consumer1 + +
- Consume two more messages from consumer2 + +
- Be sure to close our resources! + +
- User Manual's Consumer Window-Based Flow Control chapter +
- Get an initial context for looking up JNDI from server #1. +
- Look up the JMS resources from JNDI on server #1. +
- Create a JMS Connection +
- Create a JMS non-transacted Session with client acknowledgement +
- Start the connection to ensure delivery occurs +
- Create a JMS MessageProducer and MessageConsumer +
- Send some messages to server #1 +
- Receive and acknowledge half of the sent messages +
- Receive the second half of the sent messages but do not acknowledge them yet +
- Crash server #1, the live server, and wait a little while to make sure it has really crashed. +
- Acknowledging the second half of the sent messages will fail as failover to the backup server has occurred +
- Consume again the second half of the messages againg. Note that they are not considered as redelivered +
- And finally, always remember to close your resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS connection factory object from JNDI +
- We look-up the JMS queue object from JNDI. pagingQueue is configured to hold a very limited number of bytes in memory +
- We look-up the JMS queue object from JNDI. +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted. We will use client acknowledgement on this example. +
- Create a JMS Message Producer for pageQueueAddress +
- We don't need persistent messages in order to use paging. (This step is optional) +
- Create a Binary Bytes Message with 10K arbitrary bytes +
- Send only 20 messages to the Queue. This will be already enough for pagingQueue. Look at ./paging/config/hornetq-queues.xml for the config. +
- Create a JMS Message Producer +
- We don't need persistent messages in order to use paging. (This step is optional) +
- Send the message for about 30K, which should be over the memory limit imposed by the server +
- if you pause the example here, you will several files under ./build/data/paging + +
- Create a JMS Message Consumer +
- Start the JMS Connection. This step will activate the subscribers to receive messages. +
- Receive the messages. It's important to ACK for messages as HornetQ will not read messages from paging until messages are ACKed + +
- Receive the messages from the Queue names pageQueue. Create the proper consumer for that. +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - Create an initial context to perform the JNDI lookup. +
- Perform the look-ups +
- Create a the JMS objects. +
- Create and send a message. +
- Print out the message count of the queue. The queue contains one message as expected + delivery has not yet started on the queue. +
- Start the Connection, delivery will now start. Give a little time for delivery to occur. +
- Print out the message count of the queue. It should now be zero, since the message has + already been acknowledged even before the consumer has received it. +
- Finally, receive the message. +
- Be sure to close our resources! +
- User Manual's Pre-acknowledgement Mode chapter +
- Create an initial context to perform the JNDI lookup. +
- Perfom a lookup on the queue +
- Perform a lookup on the Connection Factory +
- Create a JMS Connection +
- Create a JMS Session +
- Create a JMS Message Producer +
- Send as many messages as we can in 10 seconds +
- We note that the sending rate doesn't exceed 50 messages per second. Here's some example output from a real + run + +
- For good measure we consumer the messages we produced. +
- Be sure to close our resources! + +
- Create an amqp qpid 1.0 connection. +
- Create a session +
- Create a sender +
- send a simple message +
- create a moving receiver, this means the message will be removed from the queue +
- set some credit so we can receive +
- receive the simple message +
- acknowledge the message +
- close the connection +
- Get an initial context for looking up JNDI from server 0 +
- Look-up the JMS Queue object from JNDI +
- Look-up a JMS Connection Factory object from JNDI on server 0 +
- Get an initial context for looking up JNDI from server 1. +
- Look-up a JMS Connection Factory object from JNDI on server 1 +
- We create a JMS Connection connection0 which is a connection to server 0 +
- We create a JMS Connection connection1 which is a connection to server 1 +
- We create a JMS Session on server 0, note the session is CLIENT_ACKNOWLEDGE +
- We create a JMS Session on server 1, note the session is CLIENT_ACKNOWLEDGE +
- We start the connections to ensure delivery occurs on them +
- We create JMS MessageConsumer objects on server 0 and server 1 +
- We create a JMS MessageProducer object on server 0. +
- We send some messages to server 0. +
- We now consume those messages on *both* server 0 and server 1. + We note the messages have been distributed between servers in a round robin fashion. + HornetQ has load balanced the messages between the available consumers on the different nodes. + HornetQ can be configured to always load balance messages to all nodes, or to only balance messages + to nodes which have consumers with no or matching selectors. See the user manual for more details. + JMS Queues implement point-to-point message where each message is only ever consumed by a + maximum of one consumer. +
- We acknowledge the messages consumed on node 0. The sessions are CLIENT_ACKNOWLEDGE so + messages will not get acknowledged until they are explicitly acknowledged. + Note that we do not acknowledge the message consumed on node 1 yet. +
- We now close the session and consumer on node 1. (Closing the session automatically closes the consumer) + +
- Since there is no more consumer on node 1, the messages on node 1 are now stranded (no local consumers) + so HornetQ will redistribute them to node 0 so they can be consumed. We consume them from + node 0. +
- We ack the redistributed messages. +
- And finally (no pun intended), always remember to close your resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ TextReverserService
+ - A JMS MessageListener which consumes text messages and sends replies containing the reversed text +
QueueRequestorExample
+ - A JMS Client which uses a QueueRequestor to send text requests to a queue and receive replies with the reversed text in a synchronous fashion +
- First we need to get an initial context so we can look-up the JMS connection factory from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look up the JMS queue from JNDI +
- We look up JMS queue connection factory from JNDI +
- We create the TextReverserService which will consume messages from the queue +
- We Create a JMS queue connection +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- We create a JMS queue session. The session is created as non transacted and will auto acknowledge messages (this is mandatory to use it to create a QueueRequestor) +
- We create a JMS QueueRequestor using the session and the queue +
- We create a JMS text message to send as a request +
We use the queue requestor to send the request and block until a reply is received.
+
+ Using the queue requestor simplify request/reply use case by abstracting boilerplate JMS code + (creating a temporary queue, a consumer and a producer, setting the JMS ReplyTo header on the request, + sending the request with the producer, consuming the message from the consumer). + All this code is replaced by a single call toQueueRequestor.request()method.
+ - The reply's text contains the reverse of the request's text +
- We close the queue requestor to release all the JMS resources it created to provide request/reply mechanism +
- We do the same for the text reverser service +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We start the connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create two selectors. +
- We Create a JMS Message Consumer that receives 'red' messages. +
- We Create a second JMS Message Consumer that receives 'green' messages. +
- We Create another JMS Message Consumer that receives all messages. Please not that the order + of consumers on a queue is of significance. If the anyConsumer is created before the above two, the + result will be totally different. +
- We Create three messages, each has a different color property. +
- We send the messages to the topic +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text message that we are going to send. +
- We send message to the queue +
- We create a JMS Message Consumer to receive the message. +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- The message arrives at the consumer. In this case we use a timeout of 5000 milliseconds but we could use a blocking 'receive()' +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - Create an initial context to perform the JNDI lookup. +
- Perform a lookup on the queue +
- Perform a lookup on the Connection Factory +
- We create a JMS connection +
- We create a JMS session. +
- We create a JMS message producer. +
- We create a JMS text message that we are going to send. +
- We send message to the queue +
- We create a JMS Message Consumer to receive the message. +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- To simulate a temporary problem on the network, we stop the remoting acceptor on the + server which will cause all client connections to fail. +
- We wait 10 seconds, before restarting the acceptor. During this period the client will be retrying + to connect. When the acceptor is restarted it will be successful in reconnecting. + +
- We receive the message after reattachment! Note that no exceptions were received by the client. + +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - Get an initial context for looking up JNDI from server #0. +
- Look up the JMS resources from JNDI on server #0. +
- Create a JMS Connection +
- Create a client acknowledged Session +
- Start the connection to ensure delivery occurs +
- Create a JMS MessageProducer +
- Create a JMS MessageConsumer +
- Send some messages to server #0, the live server +
- Receive and acknowledge a third of the sent messages +
- Acknowledging the 2nd third of the sent messages will fail as failover to the backup server has occurred +
- Consume again the 2nd third of the messages again. Note that they are not considered as redelivered. +
- Acknowledging the 3rd third of the sent messages will fail as failover to the backup server has occurred +
- Consume again the 3rd third of the messages again. Note that they are not considered as redelivered +
- And finally, always remember to close your resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - Get an initial context for looking up JNDI from server #0. +
- Look up the JMS resources from JNDI on server #0. +
- Create a JMS Connection +
- Create a client acknowledged Session +
- Start the connection to ensure delivery occurs +
- Create a JMS MessageProducer +
- Create a JMS MessageConsumer +
- Send some messages to server #0, the live server +
- Receive and acknowledge a third of the sent messages +
- Acknowledging the 2nd third of the sent messages will fail as failover to the backup server has occurred +
- Consume again the 2nd third of the messages again. Note that they are not considered as redelivered. +
- Acknowledging the 3rd third of the sent messages will fail as failover to the backup server has occurred +
- Consume again the 3rd third of the messages again. Note that they are not considered as redelivered +
- And finally, always remember to close your resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - Get an initial context for looking up JNDI from server #0. +
- Look up the JMS resources from JNDI on server #0. +
- Create a JMS Connection +
- Create a client acknowledged Session +
- Start the connection to ensure delivery occurs +
- Create a JMS MessageProducer +
- Create a JMS MessageConsumer +
- Send some messages to server #0, the live server +
- Receive and acknowledge a third of the sent messages +
- Acknowledging the 2nd third of the sent messages will fail as failover to the backup server has occurred +
- Consume again the 2nd third of the messages again. Note that they are not considered as redelivered. +
- Acknowledging the 3rd third of the sent messages will fail as failover to the backup server has occurred +
- Consume again the 3rd third of the messages again. Note that they are not considered as redelivered +
- And finally, always remember to close your resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - if the failover occurs while there is an in-flight transaction, the transaction will be flagged as rollback only. In that case, the JMS client + will need to retry the transaction work. +
- if the failover occurs while there is no in-flight transaction, the failover will be transparent to the user. +
- Get an initial context for looking up JNDI from server #1. +
- Look up the JMS resources from JNDI on server #1. +
- Create a JMS Connection +
- Create a JMS transacted Session +
- Start the connection to ensure delivery occurs +
- Create a JMS MessageProducer +
- Create a JMS MessageConsumer +
- Send half of the messages, kill the live server and send the remaining messages +
- As failover occurred during transaction, the session has been marked for rollback only and commit will fail +
- We resend all the messages +
- We commit the session successfully: the messages will be all delivered to the activated backup server +
- We are now transparently reconnected to server #0, the backup server. + We consume the messages sent before the crash of the live server, commit the session, and check there are no other message on the queue +
- And finally, always remember to close your resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - We start the request server +
- We need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We lookup the queue for sending the request message +
- We lookup for the Connection Factory +
- We create a JMS Connection +
- We start the connection +
- We create a JMS Session +
- We create a JMS Message Producer to send request message +
- We create a temporary queue used to send reply message to and receive reply from +
- We create a consumer to receive reply message +
- We create a request Text Message +
- We set the ReplyTo header so that the request receiver knows where to send the reply. +
- We sent the request message +
- We put the request message to the map. Later we use it to check out which request message a reply message is for. Here we use the MessageID as the correlation id (JMSCorrelationID). You don't have to use it though. You can use some arbitrary string for example. +
- We receive the reply message +
- We check out which request message is this reply message sent for. Here we just have one request message for illustrative purpose. In real world there may be many requests and many replies. +
- We close the consumer and producer on the replyQueue +
- We delete the temporary queue +
- We shutdown the request server +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - Extract the ReplyTo destination +
- Create the reply message +
- Set the CorrelationID +
- Send out the reply message +
- iPhone4 +
- Get an initial context for looking up JNDI for both servers +
- Look up the JMS resources from JNDI +
- Create a JMS Connections +
- Create a *non-transacted* JMS Session with client acknowledgement +
- Create a JMS MessageProducer +
- Send some messages to both servers +
- Crash server #0, the live server +
- start the connection ready to receive messages +
- create a consumer +
- Receive and acknowledge all of the sent messages, you will notice that messages from both servers are received +
- And finally (no pun intended), always remember to close your JMS resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text message that we are going to send. +
- We schedule the delivery time to be 5 sec later. +
- We send message to the queue +
- We create a JMS Message Consumer to receive the message. +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- We use a blocking receive() to consume the message and see when the message arrives. +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - User Manual's Scheduled Messages chapter +
- Only role 'us-user' can create/delete and pulish messages to topics whose names match wild-card pattern 'news.us.#'. +
- Only role 'europe-user' can create/delete and publish messages to topics whose names match wild-card pattern 'news.europe.#'. +
- Only role 'news-user' can subscribe messages to topics whose names match wild-card pattern 'news.us.#' and 'news.europe.#'. +
- For any other topics that don't match any of the above wild-card patterns, permissions are granted to users of role 'user'. + +
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We perform lookup on the topics +
- We perform a lookup on the Connection Factory +
- We try to create a JMS Connection without user/password. It will fail. +
- Bill tries to make a connection using wrong password +
- Bill makes a good connection. +
- Andrew makes a good connection +
- Frank makes a good connection +
- Sam makes a good connection +
- We check every user can publish/subscribe genericTopics +
- We check permissions on news.europe.europeTopic for bill: can't send and can't receive +
- We check permissions on news.europe.europeTopic for andrew: can send but can't receive +
- We check permissions on news.europe.europeTopic for frank: can't send but can receive +
- We check permissions on news.europe.europeTopic for sam: can't send but can receive +
- We check permissions on news.us.usTopic for bill: can't send and can't receive +
- We check permissions on news.us.usTopic for andrew: can't send and can't receive +
- We check permissions on news.us.usTopic for frank: can both send and receive +
- We check permissions on news.us.usTopic for sam: can't send but can receive +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- Define a SendAcknowledgementHandler which will receive asynchronous acknowledgements +
- Create a JMS session +
- Set the handler on the underlying core session +
- Create a JMS Message Producer +
- Send 5000 messages, the handler will get called asynchronously some time later after the messages are sent. +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS text message that we are going to send. +
- We send message to the queue +
- We create a JMS Message Consumer to receive the message. +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- The message arrives at the consumer. In this case we use a timeout of 5000 milliseconds but we could use a blocking 'receive()' +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - The stores were generating using the following commands ↩:
+
-
+
- create the keystore:
keytool -genkey -keystore hornetq.example.keystore -storepass hornetqexample
+ - export the certificate:
keytool -export -keystore hornetq.example.keystore -file hornetq.cer
+ - create the truststore:
keytool -import -file hornetq.cer -keystore hornetq.example.truststore -storepass hornetqexample
+
+ - create the keystore:
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI, this is the queue that has the selector configured with it. +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We start the connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS message consumer that receives 'red' messages. The message listener will + check the 'color' property on each received message. +
- We create five messages with different 'color' properties. +
- We send those messages. +
- Waiting for the message listener to check the received messages. +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI, this is the queue that has filter configured with it. +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We start the connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS message consumer that receives 'red' messages. The message listener will + check the 'color' property on each received message. +
- We reate five messages with different 'color' properties. +
- We send those messages. +
- Waiting for the message listener to check the received messages. +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - We create a TCP socket to connect to the Stomp port
+
+ Socket socket = new Socket("localhost", 61613); ++ + - We send a CONNECT frame to connect to the server +
- We send a SEND frame (a Stomp message) to the destination
jms.queue.exampleQueue+ (which corresponds to the HornetQ address for the JMS QueueexampleQueue) with a text body
+ - We send a DISCONNECT frame to disconnect from the server +
- We close the TCP socket +
- We create an initial context to perform the JNDI lookup. +
- We perform a lookup on the queue and the connection factory +
- We create a JMS Connection, Session and a MessageConsumer on the queue +
- We start the connection +
- We receive the message. Stomp messages are mapped to JMS TextMessage. +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - We create a TCP socket to connect to the Stomp port
+
+ Socket socket = new Socket("localhost", 61613); ++ + - We negotiate a Stomp 1.1 connection to the server +
- We receive a response showing that the connection version +
- We send a SEND frame (a Stomp message) to the destination
jms.queue.exampleQueue+ (which corresponds to the HornetQ address for the JMS QueueexampleQueue) with a text body
+ - We send a DISCONNECT frame to disconnect from the server +
- We close the TCP socket +
- We create an initial context to perform the JNDI lookup. +
- We perform a lookup on the queue and the connection factory +
- We create a JMS Connection, Session and a MessageConsumer on the queue +
- We start the connection +
- We receive the message. Stomp messages are mapped to JMS TextMessage. +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - We create a TCP socket to connect to the Stomp port
+
+ Socket socket = new Socket("localhost", 61613); ++ + - We negotiate a Stomp 1.2 connection to the server +
- We receive a response showing that the connection version +
- We send a SEND frame (a Stomp message) to the destination
jms.queue.exampleQueue+ (which corresponds to the HornetQ address for the JMS QueueexampleQueue) with a text body
+ - We send a DISCONNECT frame to disconnect from the server +
- We close the TCP socket +
- We create an initial context to perform the JNDI lookup. +
- We perform a lookup on the queue and the connection factory +
- We create a JMS Connection, Session and a MessageConsumer on the queue +
- We start the connection +
- We receive the message. Stomp messages are mapped to JMS TextMessage. +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - Get an initial context for looking up JNDI from server #1. +
- Look up the JMS resources from JNDI on server #1. +
- Create a JMS Connection +
- Create a JMS non-transacted Session with client acknowledgement +
- Start the connection to ensure delivery occurs +
- Create a JMS MessageProducer and MessageConsumer +
- Send some messages to server #1 +
- Receive and acknowledge half of the sent messages +
- Receive the second half of the sent messages but do not acknowledge them yet +
- Crash server #1, the live server, and wait a little while to make sure it has really crashed. +
- Acknowledging the second half of the sent messages will fail as failover to the backup server has occurred +
- Consume again the second half of the messages againg. Note that they are not considered as redelivered +
- And finally, always remember to close your resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - We instantiate a connection factory directly, specifying the UDP address and port for discovering + the list of servers in the cluster. + We could use JNDI to look-up a connection factory, but we'd need to know the JNDI server host and port for the + specific server to do that, and that server might not be available at the time. By creating the + connection factory directly we avoid having to worry about a JNDI look-up. + In an app server environment you could use HA-JNDI to lookup from the clustered JNDI servers without + having to know about a specific one. + + +
- Directly instantiate JMS Queue and Topic objects +
- We create six connections, they should be to different nodes of the cluster in a round-robin fashion + and start them. +
- We create a session on each connection. +
- We create a topic subscriber on each server. +
- We create a queue consumer on server 0. +
- We create an anonymous message producer on server 2. +
- We send 500 messages each to the queue and topic. +
- Verify all subscribers and consumer receive the messages. +
- Be sure to close our resources! + +
- First we need to get an initial context so we can look-up the JMS connection factory from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up JMS connection factory from JNDI +
- We Create a JMS connection +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a Temporary Queue +
- We create a JMS message producer to the temporary queue. This will be used to send the messages. +
- We create a JMS text message to send +
- We send the message to the temporary queue +
- We create a message consumer of the temporary queue +
- We receive the message from the temporary queue +
- We close the consumer and producer before destroying the temporary queue +
- We delete the temporary queue +
- We create another temporary queue +
- We close the connection +
- We create a new connection +
- We create a new session +
- We try to access the tempQueue2 outside its lifetime, this will cause exception thrown +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - Create an initial context to perform the JNDI lookup. +
- Perform a lookup on the Connection Factory +
- Create a JMS Connection +
- Create a JMS Session +
- Instantiate a topic representing the wildcard we're going to subscribe to. +
- Create a consumer (topic subscriber) that will consume using that wildcard. + The consumer will receive any messages sent to any topic that starts with news.europe +
- Create an anonymous producer. The sending address is specified at send time. +
- Instantiate some more topic objects corresponding to the individual topics + we're going to send messages to. You could look these up from JNDI if you wanted to. +
- Send a message destined for the usa wrestling topic. +
- Send a message destined for the europe sport topic. +
- Send a message destined for the europe entertainment topic +
- Start the connection +
- We don't receive the usa wrestling message since we subscribed to news.europe.# and + that doesn't match news.usa.wrestling. However we do receive the Europe sport message, and the + europe entertainment message, since these match the wildcard. +
- Be sure to close our resources! + +
- First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS topic object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- Create one non-durable subscriber with a specific filter +
- Create a second non-durable subscriber with a specific filter +
- Create a third non-durable subscriber without any filters, and it should receive the complete set of messages +
- Send 20 messages, 10 with someID=1, 10 with someID=2 +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- Consume the messages from MessageConsumer1, filtering out someID=2 +
- Consume the messages from MessageConsumer2, filtering out someID=1 +
- Consume the messages from MessageConsumer3, receiving the complete set of messages +
- Close the consumers +
- Delete the subscriptions when you're done +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS topic object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We start the connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create two selectors. +
- We Create a JMS Message Consumer that receives 'red' messages. +
- We Create a second JMS Message Consumer that receives 'green' messages. +
- We Create another JMS Message Consumer that receives all messages. +
- We Create three messages, each has a different color property. +
- We send the messages to the topic +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS topic object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We create a JMS session. The session is created as non transacted and will auto acknowledge messages. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a JMS Message Consumer, messageConsumer1, to receive the message. +
- We create a JMS Message Consumer, messageConsumer2, to also receive the message. +
- We create a JMS text message that we are going to send. +
- We send message to the topic +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- The message arrives at the first consumer +
- The message arrives at the second consumer +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - if the failover occurs while there is an in-flight transaction, the transaction will be flagged as rollback only. In that case, the JMS client + will need to retry the transaction work. +
- if the failover occurs while there is no in-flight transaction, the failover will be transparent to the user. +
- Get an initial context for looking up JNDI from server #1. +
- Look up the JMS resources from JNDI on server #1. +
- Create a JMS Connection +
- Create a JMS transacted Session +
- Start the connection to ensure delivery occurs +
- Create a JMS MessageProducer +
- Create a JMS MessageConsumer +
- Send half of the messages, kill the live server and send the remaining messages +
- As failover occurred during transaction, the session has been marked for rollback only and commit will fail +
- We resend all the messages +
- We commit the session successfully: the messages will be all delivered to the activated backup server +
- We are now transparently reconnected to server #0, the backup server. + We consume the messages sent before the crash of the live server, commit the session, and check there are no other message on the queue +
- And finally, always remember to close your resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We look-up the JMS connection factory object from JNDI +
- We create a JMS connection +
- We start the connection. In order for delivery to occur on any consumers or subscribers on a connection, the connection must be started +
- We create a JMS session. The session is created as transacted. +
- We create a JMS message producer on the session. This will be used to send the messages. +
- We create a message consumer +
- We create 2 text messages +
- We send the text messages to the queue +
- We receive the message, it will return null as the transaction is not committed. +
- We commit the session +
- We receive the messages again +
- We roll back the session, this will cause the received message canceled and redelivered again +
- We receive the message again, we will get two messages. Nothing more, nothing less +
- We commit the session +
- We receive the message again. Nothing should be received +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We perform a lookup on the XA Connection Factory +
- We create a JMS XAConnection +
- We Start the connection +
- We create a JMS XASession +
- We create a normal session +
- We create a normal Message Consumer +
- We get the JMS Session +
- We create a message producer +
- We create two Text Messages +
- We create a transaction +
- We get the JMS XAResource +
- We begin the Transaction work +
- We do work, sending hello message. +
- We stop the work for xid1 +
- We prepare xid1 +
- We check the none should be received. +
- We create another transaction +
- We begin the transaction work +
- We send the second message +
- We stop the work for xid2 +
- We prepare xid2 +
- Again, no messages should be received! +
- We create JMX Connector to connect to the server's MBeanServer. +
- We retrieve the MBeanServerConnection +
- We list the prepared transactions +
- We roll back the first transaction +
- We commit the second one +
- We check the result, only the 'world' message received +
- We check the prepared transaction again, should have none. +
- We close the JMX connector. +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We perform a lookup on the XA Connection Factory +
- We create a JMS XAConnection +
- We Start the connection +
- We create a JMS XASession +
- We create a normal session +
- We create a normal Message Producer +
- We get the JMS Session +
- We create a message consumer +
- We create two Text Messages +
- We create a transaction +
- We get the JMS XAResource +
- We begin the Transaction work +
- We send two messages. +
- We receive the messages +
- We stop the work +
- We prepare +
- We roll back the transaction +
- We create another transaction +
- We start the transaction +
- We receive those messages again +
- We stop the work +
- We prepare +
- We commit! +
- We check that no more messages are received. +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We perform a lookup on the XA Connection Factory +
- We create a JMS XAConnection +
- We Start the connection +
- We create a JMS XASession +
- We create a normal session +
- We create a normal Message Consumer +
- We get the JMS Session +
- We create a message producer +
- We create two Text Messages +
- We create a transaction +
- We get the JMS XAResource +
- We begin the Transaction work +
- We do work, sending two messages. +
- We check the result, it should receive none! +
- We stop the work +
- We prepare +
- We roll back the transaction +
- We check no messages should be received! +
- We create another transaction +
- We start the transaction +
- We re-send those messages +
- We stop the work +
- We prepare +
- We check that no messages should be received at this moment +
- We commit! +
- We check that all messages are received. +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the
client-jndi.propertiesfile in the directory../common/config
+ - We look-up the JMS queue object from JNDI +
- We perform a lookup on the XA Connection Factory +
- We create a JMS XAConnection +
- We Start the connection +
- We create a JMS XASession +
- We create a normal session +
- We create a normal Message Producer +
- We get the JMS Session +
- We create a message consumer +
- We create two Text Messages +
- We get the Transaction Manager +
- We start a transaction +
- We get the JMS XAResource +
- We enlist the resources in the Transaction work +
- We send two messages. +
- We receive the messages +
- We roll back the transaction +
- We create another transaction +
- We enlist the resources to start the transaction work +
- We receive those messages again +
- We commit +
- We check that no more messages are received. +
- And finally, always remember to close your JMS connections and resources after use, in a
finallyblock. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects
+
+ - v2.2.2 - Fixed encodeFileToFile and decodeFileToFile to use the + * Base64.InputStream class to encode and decode on the fly which uses + * less memory than encoding/decoding an entire file into memory before writing. + *
- v2.2.1 - Fixed bug using URL_SAFE and ORDERED encodings. Fixed bug + * when using very small files (~< 40 bytes). + *
- v2.2 - Added some helper methods for encoding/decoding directly from
+ * one file to the next. Also added a main() method to support command line
+ * encoding/decoding from one file to the next. Also added these Base64 dialects:
+ *
-
+ *
- The default is RFC3548 format. + *
- Calling Base64.setFormat(Base64.BASE64_FORMAT.URLSAFE_FORMAT) generates + * URL and file name friendly format as described in Section 4 of RFC3548. + * http://www.faqs.org/rfcs/rfc3548.html + *
- Calling Base64.setFormat(Base64.BASE64_FORMAT.ORDERED_FORMAT) generates + * URL and file name friendly format that preserves lexical ordering as described + * in http://www.faqs.org/qa/rfcc-1940.html + *
+ * - v2.1 - Cleaned up javadoc comments and unused variables and methods. Added + * some convenience methods for reading and writing to and from files. + *
- v2.0.2 - Now specifies UTF-8 encoding in places where the code fails on systems + * with other encodings (like EBCDIC). + *
- v2.0.1 - Fixed an error when decoding a single byte, that is, when the + * encoded data was a single byte. + *
- v2.0 - I got rid of methods that used booleans to set options. + * Now everything is more consolidated and cleaner. The code now detects + * when data that's being decoded is gzip-compressed and will decompress it + * automatically. Generally things are cleaner. You'll probably have to + * change some method calls that you were making to support the new + * options format (ints that you "OR" together). + *
- v1.5.1 - Fixed bug when decompressing and decoding to a + * byte[] using decode( String s, boolean gzipCompressed ). + * Added the ability to "suspend" encoding in the Output Stream so + * you can turn on and off the encoding if you need to embed base64 + * data in an otherwise "normal" stream (like an XML file). + *
- v1.5 - Output stream pases on flush() command but doesn't do anything itself. + * This helps when using GZIP streams. + * Added the ability to GZip-compress objects before encoding them. + *
- v1.4 - Added helper methods to read/write files. + *
- v1.3.6 - Fixed OutputStream.flush() so that 'position' is reset. + *
- v1.3.5 - Added flag to turn on and off line breaks. Fixed bug in input stream + * where last buffer being read, if not completely full, was not returned. + *
- v1.3.4 - Fixed when "improperly padded stream" error was thrown at the wrong time. + *
- v1.3.3 - Fixed I/O streams which were totally messed up. + *
+ ic = new InitialContext();
+
+
+
+ TransactionManager tm = (TransactionManager)ic.lookup("java:/TransactionManager");
+
+
+
+ XAConnectionFactory cf = (XAConnectionFactory)ic.lookup("java:/JmsXA");
+
+
+
+ Queue queue = (Queue)ic.lookup("queue/testQueue");
+
+
+
+ xaConnection = xacf.createXAConnection();
+ XASession session = xaConnection.createXASession();
+ MessageProducer messageProducer = session.createProducer(queue);
+
+
+
+ XAResource failingXAResource = new FailingXAResource();
+
+
+
+ tm.begin();
+ Transaction tx = tm.getTransaction();
+
+
+
+ tx.enlistResource(failingXAResource);
+
+
+
+ tx.enlistResource(session.getXAResource());
+
+
+
+ TextMessage message = session.createTextMessage(text);
+ messageProducer.send(message);
+ System.out.format("Sent message: %s (%s)\n", message.getText(), message.getJMSMessageID());
+
+
+
+ tx.delistResource(failingXAResource);
+
+
+
+ tx.delistResource(session.getXAResource());
+
+
+
+ System.out.println("committing the tx");
+ tx.commit();
+
+
+ When the transaction is committed, it will prepare both XAResources and then commit them.
+
The failing resources will crash the server leaving the JMS XA Resource prepared but not committed
+ +When WildFly is restarted, it will automatically trigger a recovery phase. During that phase, HornetQ resources will be + scanned and the prepared transaction will be recovered and committed. It is then possible to consume this message
+ + \ No newline at end of file diff --git a/examples/javaee/xarecovery/server/standalone/configuration/application-roles.properties b/examples/javaee/xarecovery/server/standalone/configuration/application-roles.properties new file mode 100644 index 0000000000..0ade8fb88e --- /dev/null +++ b/examples/javaee/xarecovery/server/standalone/configuration/application-roles.properties @@ -0,0 +1,22 @@ +# +# Properties declaration of users roles for the realm 'ApplicationRealm'. +# +# This includes the following protocols: remote ejb, remote jndi, web, remote jms +# +# Users can be added to this properties file at any time, updates after the server has started +# will be automatically detected. +# +# The format of this file is as follows: - +# username=role1,role2,role3 +# +# A utility script is provided which can be executed from the bin folder to add the users: - +# - Linux +# bin/add-user.sh +# +# - Windows +# bin\add-user.bat +# +# The following illustrates how an admin user could be defined. +# +#admin=PowerUser,BillingAdmin, +guest=guest diff --git a/examples/javaee/xarecovery/server/standalone/configuration/application-users.properties b/examples/javaee/xarecovery/server/standalone/configuration/application-users.properties new file mode 100644 index 0000000000..c52e923158 --- /dev/null +++ b/examples/javaee/xarecovery/server/standalone/configuration/application-users.properties @@ -0,0 +1,24 @@ +# +# Properties declaration of users for the realm 'ApplicationRealm' which is the default realm +# for application services on a new AS 7.1 installation. +# +# This includes the following protocols: remote ejb, remote jndi, web, remote jms +# +# Users can be added to this properties file at any time, updates after the server has started +# will be automatically detected. +# +# The format of this realm is as follows: - +# username=HEX( MD5( username ':' realm ':' password)) +# +# A utility script is provided which can be executed from the bin folder to add the users: - +# - Linux +# bin/add-user.sh +# +# - Windows +# bin\add-user.bat +# +# The following illustrates how an admin user could be defined, this +# is for illustration only and does not correspond to a usable password. +# +#admin=2a0923285184943425d1f53ddd58ec7a +guest=3437456520927d113b17d471d630e0d6 diff --git a/examples/javaee/xarecovery/server/standalone/configuration/logging.properties b/examples/javaee/xarecovery/server/standalone/configuration/logging.properties new file mode 100644 index 0000000000..8a011f0861 --- /dev/null +++ b/examples/javaee/xarecovery/server/standalone/configuration/logging.properties @@ -0,0 +1,52 @@ +# +# JBoss, Home of Professional Open Source. +# Copyright 2010, Red Hat, Inc., and individual contributors +# as indicated by the @author tags. See the copyright.txt file in the +# distribution for a full listing of individual contributors. +# +# This is free software; you can redistribute it and/or modify it +# under the terms of the GNU Lesser General Public License as +# published by the Free Software Foundation; either version 2.1 of +# the License, or (at your option) any later version. +# +# This software is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +# Lesser General Public License for more details. +# +# You should have received a copy of the GNU Lesser General Public +# License along with this software; if not, write to the Free +# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA +# 02110-1301 USA, or see the FSF site: http://www.fsf.org. +# + +# Additional logger names to configure (root logger is always configured) +loggers=org.jboss.as.config + +# Dump system environment at boot by default +logger.org.jboss.as.config.level=DEBUG + +# Root logger level +logger.level=${jboss.boot.server.log.level:INFO} +# Root logger handlers +logger.handlers=FILE,CONSOLE + +# Console handler configuration +handler.CONSOLE=org.jboss.logmanager.handlers.ConsoleHandler +handler.CONSOLE.properties=autoFlush +handler.CONSOLE.level=${jboss.boot.server.log.console.level:INFO} +handler.CONSOLE.autoFlush=true +handler.CONSOLE.formatter=PATTERN + +# File handler configuration +handler.FILE=org.jboss.logmanager.handlers.FileHandler +handler.FILE.level=DEBUG +handler.FILE.properties=autoFlush,fileName +handler.FILE.autoFlush=true +handler.FILE.fileName=${org.jboss.boot.log.file:boot.log} +handler.FILE.formatter=PATTERN + +# Formatter pattern configuration +formatter.PATTERN=org.jboss.logmanager.formatters.PatternFormatter +formatter.PATTERN.properties=pattern +formatter.PATTERN.pattern=%d{HH:mm:ss,SSS} %-5p [%c] %s%E%n diff --git a/examples/javaee/xarecovery/server/standalone/configuration/mgmt-users.properties b/examples/javaee/xarecovery/server/standalone/configuration/mgmt-users.properties new file mode 100644 index 0000000000..349b00434e --- /dev/null +++ b/examples/javaee/xarecovery/server/standalone/configuration/mgmt-users.properties @@ -0,0 +1,24 @@ +# +# Properties declaration of users for the realm 'ManagementRealm' which is the default realm +# for new AS 7.1 installations. Further authentication mechanism can be configured +# as part of theJMS AeroGear Example
+ +This example shows how you can send a message to a mobile device by leveraging AeroGears push technology which + provides support for different push notification technologies like Google Cloud Messaging, Apple's APNs or + Mozilla's SimplePush.
+ +For this example you will need an AeroGear Application running somewhere, a good way to do this is to deploy the
+ Push Application on
Once you have created your AeroGear Push Application you can create a mobile application. Simply log into the application + on the web and create a new mobile application by clicking the 'create' button. Once created you will see an application id + and a master secret, you will need the later to run the example.
+ +lastly you will need to create a variant. For this example we will be using Android so you will need to create a google project, + this article explains how to do this. + Once created click on your app then click 'add' to add a variant. choose 'google cloud messaging', enter your google + API key and the project number from your google project and click create
+ +Now before we run the example we need a mobile application to receive it. Writing a mobile app is beyond the scope + of this example but for testing purposes we have supplied an Android app you can use, simply install on your android phone. + It can be found here. For a more in depth mobile + app example visit the AeroGear site.
+ +Once you have installed the mobile app you will need to configure the following:
+AeroGear Unified Push URL : This is the URL where your aerogear server is running, something like http://myapp-mydomain.rhcloud.com + AeroGear Variant ID : This is the ID of the variant you created in AeroGear + AeroGear Variant Secret : This is the secret for your variant + GCM Sender ID : this is the Google project Number you created on Google + Variant : you can use this to target messages if needed. +
+ +Once you set all these correctly you should get a message saying your mobile app is registered, if you log into + your AeroGear app you should see it registered with the variant.
+ + +Now to run the example simply run the following command + 'mvn -Dendpoint=my aerogear url -Dapplicationid=my application id -Dmastersecret=my master secret -Djsse.enableSNIExtension=false clean verify'. + If you arent using java 7 you can omit the 'jsse.enableSNIExtension=false'
+ +You should see something like this in your HornetQServer
+-
+
+
+ Dec 04, 2013 3:25:39 PM org.jboss.aerogear.unifiedpush.SenderClient submitPayload
+ INFO: HTTP Response code from UnifiedPush Server: 302
+ Dec 04, 2013 3:25:39 PM org.jboss.aerogear.unifiedpush.SenderClient submitPayload
+ INFO: Performing redirect to 'https://myapp-mydomain.rhcloud.com/rest/sender/'
+ Dec 04, 2013 3:25:40 PM org.jboss.aerogear.unifiedpush.SenderClient submitPayload
+ INFO: HTTP Response code from UnifiedPush Server: 200
+
+
+ And on your mobile app you should see a message from HornetQ
+ +Now lets look a bit more closely at the configuration in hornetq-configuration.xml
+-
+
+
+ <queues>
+ <queue name="jms.queue.aerogearQueue">
+ <address>jms.queue.aerogearQueue</address>
+ </queue>
+ </queues>
+
+ <connector-services>
+ <connector-service name="aerogear-connector">
+ <factory-class>org.hornetq.integration.aerogear.AeroGearConnectorServiceFactory</factory-class>
+ <param key="endpoint" value="${endpoint}"/>
+ <param key="queue" value="jms.queue.aerogearQueue"/>
+ <param key="application-id" value="${applicationid}"/>
+ <param key="master-secret" value="${mastersecret}"/>
+ </connector-service>
+ </connector-services>
+
+
+ Firstly you will see that we have to create a core queue so it is available when the connector is started, the following are mandatory parameters:
+-
+
as well as those there are also the following optional parameters
+-
+
More in depth explanations of these can be found in the AeroGear docs.
+Now lets look at a snippet of code we used to send the message for our JMS client
+
+
+ Queue queue = (Queue)initialContext.lookup("/queue/aerogearQueue");
+
+ // Step 3. Perform a lookup on the Connection Factory
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+ // Step 4.Create a JMS Connection
+ connection = cf.createConnection();
+
+ // Step 5. Create a JMS Session
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+ // Step 6. Create a JMS Message Producer
+ MessageProducer producer = session.createProducer(queue);
+
+ // Step 7. Create a Text Message
+ Message message = session.createMessage();
+
+ message.setStringProperty("AEROGEAR_ALERT", "Hello this is a notification from HornetQ");
+
+ producer.send(message);
+
+
+ The most important thing here is string propert we have set on the message, i.e. 'AEROGEAR_ALERT'. This is the + actual alert that is sent via AeroGear
+As well as the alert itself you can override any of the above optional parameters in the same fashionby using the + following propert names: AEROGEAR_SOUND,AEROGEAR_BADGE,AEROGEAR_TTL,AEROGEAR_VARIANTS,AEROGEAR_ALIASES and AEROGEAR_DEVICE_TYPES
+ + \ No newline at end of file diff --git a/examples/jms/aerogear/src/main/java/org/hornetq/jms/example/AerogearExample.java b/examples/jms/aerogear/src/main/java/org/hornetq/jms/example/AerogearExample.java new file mode 100644 index 0000000000..a0d285aed4 --- /dev/null +++ b/examples/jms/aerogear/src/main/java/org/hornetq/jms/example/AerogearExample.java @@ -0,0 +1,92 @@ +/* + * Copyright 2005-2014 Red Hat, Inc. + * Red Hat licenses this file to you under the Apache License, version + * 2.0 (the "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * http://www.apache.org/licenses/LICENSE-2.0 + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + * implied. See the License for the specific language governing + * permissions and limitations under the License. + */ +package org.hornetq.jms.example; + +import javax.jms.Connection; +import javax.jms.ConnectionFactory; +import javax.jms.Message; +import javax.jms.MessageConsumer; +import javax.jms.MessageProducer; +import javax.jms.Queue; +import javax.jms.Session; +import javax.jms.TextMessage; +import javax.naming.InitialContext; + +import org.hornetq.common.example.HornetQExample; + +/** + * A simple JMS Queue example that creates a producer and consumer on a queue and sends then receives a message. + * + * @author Andy Taylor + */ +public class AerogearExample extends HornetQExample +{ + public static void main(final String[] args) + { + new AerogearExample().run(args); + } + + @Override + public boolean runExample() throws Exception + { + Connection connection = null; + InitialContext initialContext = null; + try + { + // Step 1. Create an initial context to perform the JNDI lookup. + initialContext = getContext(0); + + // Step 2. Perfom a lookup on the queue + Queue queue = (Queue)initialContext.lookup("/queue/aerogearQueue"); + + // Step 3. Perform a lookup on the Connection Factory + ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory"); + + // Step 4.Create a JMS Connection + connection = cf.createConnection(); + + // Step 5. Create a JMS Session + Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); + + // Step 6. Create a JMS Message Producer + MessageProducer producer = session.createProducer(queue); + + // Step 7. Create a Text Message + Message message = session.createMessage(); + + message.setStringProperty("AEROGEAR_ALERT", "Hello this is a notification from HornetQ"); + + producer.send(message); + + System.out.println("Sent message"); + + System.out.println("now check your mobile app and press enter"); + + System.in.read(); + + return true; + } + finally + { + // Step 12. Be sure to close our JMS resources! + if (initialContext != null) + { + initialContext.close(); + } + if (connection != null) + { + connection.close(); + } + } + } +} diff --git a/examples/jms/aerogear/src/main/resources/hornetq/server0/hornetq-configuration.xml b/examples/jms/aerogear/src/main/resources/hornetq/server0/hornetq-configuration.xml new file mode 100644 index 0000000000..6100121cd9 --- /dev/null +++ b/examples/jms/aerogear/src/main/resources/hornetq/server0/hornetq-configuration.xml @@ -0,0 +1,61 @@ +HornetQ Applet Example
+ +The Applet will connect to HornetQ server running on localhost and
+ publishes messages on a topic exampleTopic when "Send" is pressed.
The Applet is also a MessageListener and will display messages received from the topic
+ + + + \ No newline at end of file diff --git a/examples/jms/applet/pom.xml b/examples/jms/applet/pom.xml new file mode 100644 index 0000000000..db34e339e8 --- /dev/null +++ b/examples/jms/applet/pom.xml @@ -0,0 +1,129 @@ +Applet Example
+This example shows you how to send and receive JMS messages from an Applet.
+ +Example step-by-step
+ +To run the example, simply type mvn verify from this directory to start
+ the HornetQ server and an HTTP server.
Then, go to http://127.0.0.1:8088/applet.html to load + and use the applet.
+ + + \ No newline at end of file diff --git a/examples/jms/applet/src/main/java/org/hornetq/jms/example/AppletExample.java b/examples/jms/applet/src/main/java/org/hornetq/jms/example/AppletExample.java new file mode 100644 index 0000000000..4d09780a45 --- /dev/null +++ b/examples/jms/applet/src/main/java/org/hornetq/jms/example/AppletExample.java @@ -0,0 +1,290 @@ +/* + * Copyright 2005-2014 Red Hat, Inc. + * Red Hat licenses this file to you under the Apache License, version + * 2.0 (the "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * http://www.apache.org/licenses/LICENSE-2.0 + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + * implied. See the License for the specific language governing + * permissions and limitations under the License. + */ +package org.hornetq.jms.example; + +import java.awt.Color; +import java.awt.GridBagConstraints; +import java.awt.GridBagLayout; +import java.awt.event.ActionEvent; +import java.awt.event.ActionListener; +import java.util.Date; +import java.util.HashMap; +import java.util.Map; + +import javax.jms.Connection; +import javax.jms.ConnectionFactory; +import javax.jms.Destination; +import javax.jms.JMSException; +import javax.jms.Message; +import javax.jms.MessageConsumer; +import javax.jms.MessageListener; +import javax.jms.MessageProducer; +import javax.jms.Session; +import javax.jms.TextMessage; +import javax.swing.BorderFactory; +import javax.swing.JApplet; +import javax.swing.JButton; +import javax.swing.JFrame; +import javax.swing.JLabel; +import javax.swing.JPanel; +import javax.swing.JScrollPane; +import javax.swing.JTextArea; +import javax.swing.SwingConstants; +import javax.swing.SwingUtilities; + +import org.hornetq.api.core.TransportConfiguration; +import org.hornetq.api.jms.HornetQJMSClient; +import org.hornetq.api.jms.JMSFactoryType; +import org.hornetq.core.remoting.impl.netty.NettyConnectorFactory; + +/** + * A AppletExample + * + * @author params = new HashMapApplication-Layer Failover Example
+ +HornetQ implements fully transparent automatic failover of connections from a live node to a backup node which requires + no special coding. This is described in a different example and requires server replication.
+However, HornetQ also supports Application-Layer failover which is useful in the case where replication is not enabled.
+With Application-Layer failover, it's up to the application to register a JMS ExceptionListener with HornetQ. + This listener will then be called by HornetQ in the event that connection failure is detected.
+User code in the ExceptionListener can then recreate any JMS Connection, Session, etc on another node and the application + can continue.
+Application-Layer failover is an alternative approach to High Availabilty (HA).
+Application-Layer failover differs from automatic failover in that some client side coding is required in order + to implement this. Also, with Application-Layer failover, since the old Session object dies and a new is created, any uncommitted + work in the old Session will be lost, and any unacknowledged messages might be redelivered.
+For more information on HornetQ failover and HA, and clustering in general, please see the clustering + section of the user manual.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
In this example, the live server is server 1, which will failover onto server 0.
+The connection will initially be created to server1, server 1 will crash, and the client will carry on + on server 0, the new server. With Application-Layer failover the node that is failed over onto, does not need to + be specially configured as a backup server, it can be any node.
+ +-
+
+ createJMSObjects(1);
+
+
+
+ connection.setExceptionListener(new ExampleListener());
+
+
+
+
+ final int numMessages = 10;
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session.createTextMessage("This is text message " + i);
+
+ producer.send(message);
+
+ System.out.println("Sent message: " + message.getText());
+ }
+
+
+
+
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message0 = (TextMessage)consumer.receive(5000);
+
+ System.out.println("Got message: " + message0.getText());
+ }
+
+
+
+
+ killServer(1);
+
+
+
+
+ private class ExampleListener implements ExceptionListener
+ {
+ public void onException(JMSException exception)
+ {
+ try
+ {
+ // Close the old resources
+
+ closeResources();
+
+ // Create new JMS objects on the backup server
+
+ createJMSObjects(0);
+
+ failoverLatch.countDown();
+ }
+ catch (Exception e)
+ {
+ System.err.println("Failed to handle failover");
+
+ e.printStackTrace();
+ }
+ }
+ }
+
+
+
+
+
+ for (int i = numMessages; i < numMessages * 2; i++)
+ {
+ TextMessage message = session.createTextMessage("This is text message " + i);
+
+ producer.send(message);
+
+ System.out.println("Sent message: " + message.getText());
+ }
+
+
+
+
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message0 = (TextMessage)consumer.receive(5000);
+
+ System.out.println("Got message: " + message0.getText());
+ }
+
+
+
+
+
+
+ finally
+ {
+ closeResources();
+ }
+
+
+
+ Core Bridge Example
+ +This example demonstrates a core bridge deployed on one server, which consumes messages from a + local queue and forwards them to an address on a second server.
+ +Core bridges are used to create message flows between any two HornetQ servers which are remotely separated. + Core bridges are resilient and will cope with temporary connection failure allowing them to be an ideal + choice for forwarding over unreliable connections, e.g. a WAN.
+They can also be configured with an optional filter expression, and will only forward messages that + match that filter.
+Furthermore they can be configured to use an optional Transformer class. A user-defined Transformer class + can be specified which is called at forwarding time. This gives the user the opportunity to transform + the message in some ways, e.g. changing its properties or body
+HornetQ also includes a JMS Bridge. This is similar to a core bridge, but uses the JMS API + and can be used to bridge between any two JMS 1.1 compliant messaging systems. The core bridge is limited to bridging + between HornetQ instances, but may provide better performance than the JMS bridge. The JMS bridge is covered in + a separate example.
+For more information on bridges, please see the HornetQ user manual.
+ +In this example we will demonstrate a simple sausage factory for aardvarks.
+We have a JMS queue on server 0 named sausage-factory, and we have a
+ JMS queue on server 1 named mincing-machine
We want to forward any messages that are sent to the sausage-factory queue on server 0, to the mincing-machine
+ on server 1.
We only want to make aardvark sausages, so we only forward messages where the property "name" is set
+ to "aardvark". It is known that other things, such are Sasquatches are also sent to the sausage-factory and we
+ want to reject those.
Moreover it is known that Aardvarks normally wear blue hats, and it's important that we only make sausages using + Aardvarks with green hats, so on the way we are going transform the property "hat" from "green" to "blue".
+Here's a snippet from hornetq-configuration.xml showing the bridge configuration
+
+ <bridge name="my-bridge">
+ <queue-name>jms.queue.sausage-factory</queue-name>
+ <forwarding-address>jms.queue.mincing-machine</forwarding-address>
+ <filter string="name='aardvark'"/>
+ <transformer-class-name>org.hornetq.jms.example.HatColourChangeTransformer</transformer-class-name>
+ <reconnect-attempts>-1</reconnect-attempts>
+ <static-connectors>
+ <connector-ref>remote-connector</connector-ref>
+ </static-connectors>
+ </bridge>
+
+
+ Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+
+ ic0 = getContext(0);
+
+
+
+
+ Queue sausageFactory = (Queue)ic0.lookup("/queue/sausage-factory");
+
+
+
+ ConnectionFactory cf0 = (ConnectionFactory)ic0.lookup("/ConnectionFactory");
+
+
+
+ ic1 = getContext(1);
+
+
+
+ Queue mincingMachine = (Queue)ic1.lookup("/queue/mincing-machine");
+
+
+
+
+
+ ConnectionFactory cf1 = (ConnectionFactory)ic1.lookup("/ConnectionFactory");
+
+
+
+
+
+ connection0 = cf0.createConnection();
+
+
+
+
+
+ connection1 = cf1.createConnection();
+
+
+
+
+
+ Session session0 = connection0.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+
+ Session session1 = connection1.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+
+ connection1.start();
+
+
+
+
+
+ MessageConsumer consumer = session1.createConsumer(mincingMachine);
+
+
+
+
+
+ MessageProducer producer = session0.createProducer(sausageFactory);
+
+
+
+
+ Message message = session0.createMessage();
+
+ message.setStringProperty("name", "aardvark");
+
+ message.setStringProperty("hat", "green");
+
+ producer.send(message);
+
+
+
+
+
+ Message receivedMessage = consumer.receive(5000);
+
+
+
+
+
+ message = session0.createMessage();
+
+ message.setStringProperty("name", "sasquatch");
+
+ message.setStringProperty("hat", "mauve");
+
+ producer.send(message);
+
+
+
+
+
+ receivedMessage = (TextMessage)consumer.receive(1000);
+
+
+
+
+
+
+ finally
+ {
+ if (connection0 != null)
+ {
+ connection0.close();
+ }
+
+ if (connection1 != null)
+ {
+ connection1.close();
+ }
+
+ if (ic0 != null)
+ {
+ ic0.close();
+ }
+
+ if (ic1 != null)
+ {
+ ic1.close();
+ }
+ }
+
+
+
+ JMS QueueBrowser Example
+ +This example shows you how to use a JMS QueueBrowser with HornetQ.
+ Queues are a standard part of JMS, please consult the JMS 1.1 specification for full details.
+ A QueueBrowser is used to look at messages on the queue without removing them.
+ It can scan the entire content of a queue or only messages matching a message selector.
+ The example will send 2 messages on a queue, use a QueueBrowser to browse + the queue (looking at the message without removing them) and finally consume the 2 messages +
+Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(topic);
+
+
+
+ TextMessage message_1 = session.createTextMessage("this is the 1st message");
+ TextMessage message_2 = session.createTextMessage("this is the 2nd message");
+
+
+
+ messageProducer.send(message_1);
+ messageProducer.send(message_2);
+
+
+
+ QueueBrowser browser = session.createBrowser(queue);
+
+
+
+ Enumeration messageEnum = browser.getEnumeration();
+ while (messageEnum.hasMoreElements())
+ {
+ TextMessage message = (TextMessage)messageEnum.nextElement();
+ System.out.println("Browsing: " + message.getText());
+ }
+
+
+
+ browser.close();
+
+
+ The messages were browsed but they were not removed from the queue. We will now consume them.
+ +
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+
+
+ connection.start();
+
+
+
+ TextMessage messageReceived = (TextMessage)messageConsumer.receive(5000);
+ System.out.println("Received message: " + messageReceived.getText());
+ messageReceived = (TextMessage)messageConsumer.receive(5000);
+ System.out.println("Received message: " + messageReceived.getText());
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ Client Kickoff Example
+ +This example shows how to kick off a client connected to HornetQ + using JMX
+ +The example will connect to HornetQ. Using JMX, we will list the remote addresses connected to the + server and close the corresponding connections. The client will be kicked off from HornetQ receiving + an exception that its JMS connection was interrupted.
+ +Example configuration
+ +HornetQ exposes its managed resources by default on the platform MBeanServer.
+To access this MBeanServer remotely, the Java Virtual machine must be started with system properties: +
+ -Dcom.sun.management.jmxremote
+ -Dcom.sun.management.jmxremote.port=3000
+ -Dcom.sun.management.jmxremote.ssl=false
+ -Dcom.sun.management.jmxremote.authenticate=false
+
+ These properties are explained in the Java 5 Management guide + (please note that for this example, we will disable user authentication for simplicity).
+With these properties, HornetQ server will be manageable remotely using standard JMX URL on port 3000.
Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext(0);
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ final AtomicReference<JMSException> exception = new AtomicReference<JMSException>();
+ connection.setExceptionListener(new ExceptionListener()
+ {
+ public void onException(JMSException e)
+ {
+ exception.set(e);
+ }
+ });
+
+
+
+ connection.start();
+
+
+
+ ObjectName on = ObjectNameBuilder.DEFAULT.getHornetQServerObjectName();
+ JMXConnector connector = JMXConnectorFactory.connect(new JMXServiceURL(JMX_URL), new HashMap());
+ MBeanServerConnection mbsc = connector.getMBeanServerConnection();
+ HornetQServerControlMBean serverControl = (HornetQServerControlMBean)MBeanServerInvocationHandler.newProxyInstance(mbsc,
+ on,
+ HornetQServerControlMBean.class,
+ false);
+
+
+
+
+ String[] remoteAddresses = serverControl.listRemoteAddresses();
+ for (String remoteAddress : remoteAddresses)
+ {
+ System.out.println(remoteAddress);
+ }
+
+
+
+ It will display a single address corresponding to the connection opened at step 3.
+ +
+ serverControl.closeConnectionsForAddress(remoteAddresses[0]);
+
+
+ Warnings be displayed on the server output:
+
+ org.hornetq.jms.example.SpawnedJMSServer out:11:22:33,034 WARN @RMI TCP Connection(3)-192.168.0.10 [RemotingConnectionImpl] Connection failure has been detected connections for /192.168.0.10:52707 closed by management:0
+ org.hornetq.jms.example.SpawnedJMSServer out:11:22:33,035 WARN @RMI TCP Connection(3)-192.168.0.10 [ServerSessionImpl] Client connection failed, clearing up resources for session 4646da35-2fe8-11de-9ce9-752ccc2b26e4
+ org.hornetq.jms.example.SpawnedJMSServer out:11:22:33,035 WARN @RMI TCP Connection(3)-192.168.0.10 [ServerSessionImpl] Cleared up resources for session 4646da35-2fe8-11de-9ce9-752ccc2b26e4
+
+
+
+
+ exception.get().printStackTrace();
+
+
+ When the connection was closed on the server-side by the call to serverControl.closeConnectionsForAddress(),
+ the client's connection was disconnected and its exception listener was notified.
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ More information
+ + + + \ No newline at end of file diff --git a/examples/jms/client-kickoff/src/main/java/org/hornetq/jms/example/ClientKickoffExample.java b/examples/jms/client-kickoff/src/main/java/org/hornetq/jms/example/ClientKickoffExample.java new file mode 100644 index 0000000000..6923faa410 --- /dev/null +++ b/examples/jms/client-kickoff/src/main/java/org/hornetq/jms/example/ClientKickoffExample.java @@ -0,0 +1,126 @@ +/* + * Copyright 2005-2014 Red Hat, Inc. + * Red Hat licenses this file to you under the Apache License, version + * 2.0 (the "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * http://www.apache.org/licenses/LICENSE-2.0 + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + * implied. See the License for the specific language governing + * permissions and limitations under the License. + */ +package org.hornetq.jms.example; + +import java.util.HashMap; +import java.util.concurrent.atomic.AtomicReference; + +import javax.jms.ExceptionListener; +import javax.jms.JMSException; +import javax.jms.QueueConnection; +import javax.jms.QueueConnectionFactory; +import javax.management.MBeanServerConnection; +import javax.management.MBeanServerInvocationHandler; +import javax.management.ObjectName; +import javax.management.remote.JMXConnector; +import javax.management.remote.JMXConnectorFactory; +import javax.management.remote.JMXServiceURL; +import javax.naming.InitialContext; + +import org.hornetq.api.core.management.HornetQServerControl; +import org.hornetq.api.core.management.ObjectNameBuilder; +import org.hornetq.common.example.HornetQExample; + +/** + * An example that shows how to kick off a client connected to HornetQ by using JMX. + * + * @author Jeff Mesnil + */ +public class ClientKickoffExample extends HornetQExample +{ + private static final String JMX_URL = "service:jmx:rmi:///jndi/rmi://localhost:3000/jmxrmi"; + + public static void main(final String[] args) + { + new ClientKickoffExample().run(args); + } + + @Override + public boolean runExample() throws Exception + { + QueueConnection connection = null; + InitialContext initialContext = null; + try + { + // Step 1. Create an initial context to perform the JNDI lookup. + initialContext = getContext(0); + + // Step 2. Perform a lookup on the Connection Factory + QueueConnectionFactory cf = (QueueConnectionFactory)initialContext.lookup("/ConnectionFactory"); + + // Step 3.Create a JMS Connection + connection = cf.createQueueConnection(); + + // Step 4. Set an exception listener on the connection to be notified after a problem occurred + final AtomicReferenceClient Side Kickoff Example
+ +This example demonstrates how you can listen on failover event on the client side.
+ +In this example there are two nodes running in a cluster, both server will be running for start, + but after a while the first server will crash. This will trigger an fail oever event.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext(0);
+
+
+
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+
+
+ Thread.sleep(5000);
+ connectionA = connectionFactory.createConnection();
+ ((HornetQConnection)connectionA).setFailoverListener(new FailoverListenerImpl());
+
+
+
+
+ Session sessionA = connectionA.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer producerA = sessionA.createProducer(queue);
+
+
+
+
+ final int numMessages = 10;
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage messageA = sessionA.createTextMessage("A:This is text message " + i);
+ producerA.send(messageA);
+ System.out.println("Sent message: " + messageA.getText());
+ }
+
+
+
+
+ connectionA.start();
+
+
+
+ consume(sessionA, queue, numMessages, "A");
+
+
+
+
+ if (connectionA != null)
+ {
+ connectionA.close();
+ }
+
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+
+
+ JMS Client-Side Load-Balancing Example
+ +This example demonstrates how connnections created from a single JMS Connection factory can be created + to different nodes of the cluster. In other words it demonstrates how HornetQ does client side load balancing of + connections across the cluster.
+The particular load-balancing policy can be chosen to be random, round-robin or user-defined. Please see the user + guide for more details of how to configure the specific load-balancing policy. In this example we will use + the default round-robin load balancing policy.
+The list of servers over which HornetQ will round-robin the connections can either be specified explicitly + in the connection factory when instantiating it directly, when configuring it on the server or configured + to use UDP discovery to discover the list of servers over which to round-robin. This example will use UDP + discovery to obtain the list.
+This example starts three servers which all broadcast their location using UDP discovery. The UDP broadcast configuration
+ can be seen in the hornetq-configuration.xml file.
A JMS ConnectionFactory is deployed on each server specifying the discovery group that will be used by that + connection factory.
+For more information on HornetQ load balancing, and clustering in general, please see the clustering + section of the user manual.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ initialContext = getContext(0);
+
+
+
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+
+
+ Connection conn = connectionFactory.createConnection();
+ connectionA = connectionFactory.createConnection();
+ connectionB = connectionFactory.createConnection();
+ connectionC = connectionFactory.createConnection();
+ conn.close();
+
+
+
+
+
+ Session sessionA = connectionA.createSession(false, Session.AUTO_ACKNOWLEDGE);
+ Session sessionB = connectionB.createSession(false, Session.AUTO_ACKNOWLEDGE);
+ Session sessionC = connectionC.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+
+ MessageProducer producerA = sessionA.createProducer(queue);
+ MessageProducer producerB = sessionB.createProducer(queue);
+ MessageProducer producerC = sessionC.createProducer(queue);
+
+
+
+
+
+ final int numMessages = 10;
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage messageA = sessionA.createTextMessage("A:This is text message " + i);
+ producerA.send(messageA);
+ System.out.println("Sent message: " + messageA.getText());
+
+ TextMessage messageB = sessionB.createTextMessage("B:This is text message " + i);
+ producerB.send(messageB);
+ System.out.println("Sent message: " + messageB.getText());
+
+ TextMessage messageC = sessionC.createTextMessage("C:This is text message " + i);
+ producerC.send(messageC);
+ System.out.println("Sent message: " + messageC.getText());
+ }
+
+
+
+
+
+ connectionA.start();
+ connectionB.start();
+ connectionC.start();
+
+
+
+
+
+ consume(sessionA, queue, numMessages, "A");
+ consume(sessionB, queue, numMessages, "B");
+ consume(sessionC, queue, numMessages, "C");
+
+
+
+
+
+ finally
+ {
+ if (connectionA != null)
+ {
+ connectionA.close();
+ }
+ if (connectionB != null)
+ {
+ connectionB.close();
+ }
+ if (connectionC != null)
+ {
+ connectionC.close();
+ }
+
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ }
+
+
+
+ JMS Durable Subscription Example
+ +This example demonstrates a clustered JMS durable subscription. + Normally durable subscriptions exist on a single node and can only have one subscriber at any one time, + however, with HornetQ it's possible to create durable subscription instances with the same name and client-id + on different nodes of the cluster, and consume from them simultaneously. + This allows the work of processing messages from a durable subscription to be spread across the cluster in + a similar way to how JMS Queues can be load balanced across the cluster +
+In this example we first configure the two nodes to form a cluster, then we then create a durable subscriber + with the same name and client-id on both nodes, and we create a producer on only one of the nodes.
+We then send some messages via the producer, and we verify that the messages are round robin'd between + the two subscription instances. Note that each durable subscription instance with the same name and client-id + does not receive its own copy of the messages. This is because the instances on different nodes form a + single "logical" durable subscription, in the same way multiple JMS Queue instances on different nodes + form a single "local" JMS Queue
+This example uses JNDI to lookup the JMS Queue and ConnectionFactory objects. If you prefer not to use + JNDI, these could be instantiated directly. +
Here's the relevant snippet from the server configuration, which tells the server to form a cluster between the two nodes + and to load balance the messages between the nodes.
+
+ <cluster-connection name="my-cluster">
+ <address>jms</address>
+ <retry-interval>500</retry-interval>
+ <use-duplicate-detection>true</use-duplicate-detection>
+ <forward-when-no-consumers>true</forward-when-no-consumers>
+ <max-hops>1</max-hops>
+ <discovery-group-ref discovery-group-name="my-discovery-group"/>
+ </cluster-connection>
+
+
+ For more information on HornetQ load balancing, and clustering in general, please see the clustering + section of the user manual.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+
+ ic0 = getContext(0);
+
+
+
+
+ Topic topic = (Topic)ic0.lookup("/topic/exampleTopic");
+
+
+
+ ConnectionFactory cf0 = (ConnectionFactory)ic0.lookup("/ConnectionFactory");
+
+
+
+ ic1 = getContext(1);
+
+
+
+ ConnectionFactory cf1 = (ConnectionFactory)ic1.lookup("/ConnectionFactory");
+
+
+
+
+
+ connection0 = cf0.createConnection();
+ final String clientID = "my-client-id";
+ connection0.setClientID(clientID);
+
+
+
+
+
+ connection1 = cf1.createConnection();
+ connection1.setClientID(clientID);
+
+
+
+
+
+ Session session0 = connection0.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+
+ Session session1 = connection1.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+
+ connection0.start();
+
+ connection1.start();
+
+
+
+
+
+ final String subscriptionName = "my-subscription";
+
+ MessageConsumer subscriber0 = session0.createDurableSubscriber(topic, subscriptionName);
+
+ MessageConsumer subscriber1 = session1.createDurableSubscriber(topic, subscriptionName);
+
+
+
+
+
+ MessageProducer producer = session0.createProducer(topic);
+
+
+
+
+ final int numMessages = 10;
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session0.createTextMessage("This is text message " + i);
+
+ producer.send(message);
+
+ System.out.println("Sent message: " + message.getText());
+ }
+
+
+
+
+
+ for (int i = 0; i < numMessages; i += 2)
+ {
+ TextMessage message0 = (TextMessage)consumer0.receive(5000);
+
+ System.out.println("Got message: " + message0.getText() + " from node 0");
+
+ TextMessage message1 = (TextMessage)consumer1.receive(5000);
+
+ System.out.println("Got message: " + message1.getText() + " from node 1");
+ }
+
+
+
+
+
+ finally
+ {
+ if (connection0 != null)
+ {
+ connection0.close();
+ }
+
+ if (connection1 != null)
+ {
+ connection1.close();
+ }
+ }
+
+
+
+ JMS Clustered Grouping Example
+ +This example demonstrates how to ensure strict ordering across a cluster using clustered message grouping
+We create 3 nodes each with a grouping message handler, one with a Local handler and 2 with a Remote handler.
+The local handler acts as an arbitrator for the 2 remote handlers, holding the information on routes and communicating + the routing info with the remote handlers on the other 2 nodes
+We then send some messages to each node with the same group id set and ensure the same consumer receives all of them
+Here's the relevant snippet from the server configuration that has the local handler
+
+
+ <cluster-connections>
+ <cluster-connection name="my-cluster">
+ <address>jms</address>
+ <connector-ref>netty-connector</connector-ref>
+ <retry-interval>500</retry-interval>
+ <use-duplicate-detection>true</use-duplicate-detection>
+ <forward-when-no-consumers>true</forward-when-no-consumers>
+ <max-hops>1</max-hops>
+ <discovery-group-ref discovery-group-name="my-discovery-group"/>
+ </cluster-connection>
+ </cluster-connections>
+
+ <grouping-handler name="my-grouping-handler">
+ <type>LOCAL</type>
+ <address>jms</address>
+ <timeout>5000</timeout>
+ </grouping-handler>
+
+
+
+ Here's the relevant snippet from the server configuration that has the remote handlers
+
+
+ <cluster-connections>
+ <cluster-connection name="my-cluster">
+ <address>jms</address>
+ <retry-interval>500</retry-interval>
+ <use-duplicate-detection>true</use-duplicate-detection>
+ <forward-when-no-consumers>true</forward-when-no-consumers>
+ <max-hops>1</max-hops>
+ <discovery-group-ref discovery-group-name="my-discovery-group"/>
+ </cluster-connection>
+ </cluster-connections>
+
+ <grouping-handler name="my-grouping-handler">
+ <type>REMOTE</type>
+ <address>jms</address>
+ <timeout>5000</timeout>
+ </grouping-handler>
+
+
+
+ For more information on HornetQ clustering and grouping see the clustering and grouping + section of the user manual.
+Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ ic0 = getContext(0);
+
+
+
+ Queue queue = (Queue)ic0.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf0 = (ConnectionFactory)ic0.lookup("/ConnectionFactory");
+
+
+
+ ic1 = getContext(1);
+
+
+
+ ConnectionFactory cf1 = (ConnectionFactory)ic1.lookup("/ConnectionFactory");
+
+
+
+
+ ic2 = getContext(2);
+
+
+
+ ConnectionFactory cf2 = (ConnectionFactory)ic2.lookup("/ConnectionFactory");
+
+
+
+
+ connection0 = cf0.createConnection();
+
+
+
+ connection1 = cf1.createConnection();
+
+
+
+ connection2 = cf2.createConnection();
+
+
+
+ Session session0 = connection0.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ Session session1 = connection1.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ Session session2 = connection2.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+ connection0.start();
+
+ connection1.start();
+
+ connection2.start();
+
+
+
+ MessageConsumer consumer = session0.createConsumer(queue);
+
+
+
+
+ MessageProducer producer0 = session0.createProducer(queue);
+
+ MessageProducer producer1 = session1.createProducer(queue);
+
+ MessageProducer producer2 = session2.createProducer(queue);
+
+
+
+
+ final int numMessages = 10;
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session0.createTextMessage("This is text message " + i);
+
+ message.setStringProperty(HornetQMessage.JMSXGROUPID, "Group-0");
+
+ producer0.send(message);
+
+ System.out.println("Sent messages: " + message.getText() + " to node 0");
+ }
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session1.createTextMessage("This is text message " + (i + 10));
+
+ message.setStringProperty(HornetQMessage.JMSXGROUPID, "Group-0");
+
+ producer1.send(message);
+
+ System.out.println("Sent messages: " + message.getText() + " to node 1");
+
+ }
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session2.createTextMessage("This is text message " + (i + 20));
+
+ message.setStringProperty(HornetQMessage.JMSXGROUPID, "Group-0");
+
+ producer2.send(message);
+
+ System.out.println("Sent messages: " + message.getText() + " to node 2");
+ }
+
+
+
+
+
+ for (int i = 0; i < numMessages * 3; i++)
+ {
+ TextMessage message0 = (TextMessage)consumer.receive(5000);
+
+ System.out.println("Got message: " + message0.getText() + " from node 0");
+
+ }
+
+
+
+
+ if (connection0 != null)
+ {
+ connection0.close();
+ }
+
+ if (connection1 != null)
+ {
+ connection1.close();
+ }
+
+ if (connection2 != null)
+ {
+ connection2.close();
+ }
+
+ if (ic0 != null)
+ {
+ ic0.close();
+ }
+
+ if (ic1 != null)
+ {
+ ic1.close();
+ }
+
+ if (ic2 != null)
+ {
+ ic2.close();
+ }
+
+
+ HornetQ Clustering with JGroups Example
+ +This example demonstrates the working of a two node cluster using JGroups as the underlying topology broadcasting/discovery + technique.
+We deploy a queue on to the cluster, then create a consumer on the queue on each node, and we create a producer on only one of the nodes.
+We then send some messages via the producer, and we verify that both consumers receive the sent messages + in a round-robin fashion.
+This example uses JNDI to lookup the JMS Queue and ConnectionFactory objects. If you prefer not to use + JNDI, these could be instantiated directly.
+To enable HornetQ to use JGroups you need to configure JGroups configuration file and make sure it is on the classpath + by placing in the configuration directory, the file test-jgroups-file_ping.xml is the configuration used in this + exaample
+You then configure the jgroups file used by the broadcast and discovery groups in the configuration along with the + channel name which you want this cluster to share.
+
+
+ <broadcast-groups>
+ <broadcast-group name="my-broadcast-group">
+ <broadcast-period>5000</broadcast-period>
+ <jgroups-file>test-jgroups-file_ping.xml</jgroups-file>
+ <jgroups-channel>hornetq_broadcast_channel</jgroups-channel>
+ <connector-ref>netty-connector</connector-ref>
+ </broadcast-group>
+ </broadcast-groups>
+
+ <discovery-groups>
+ <discovery-group name="my-discovery-group">
+ <jgroups-file>test-jgroups-file_ping.xml</jgroups-file>
+ <jgroups-channel>hornetq_broadcast_channel</jgroups-channel>
+ <refresh-timeout>10000</refresh-timeout>
+ </discovery-group>
+ </discovery-groups>
+
+
+ For more information on HornetQ clustering in general, please see the clustering + section of the user manual.
+Example step-by-step
+To run the example, simply type ./build.sh (or build.bat on windows) from this directory
-
+
+
+ ic0 = getContext(0);
+
+
+
+
+ Queue queue = (Queue)ic0.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf0 = (ConnectionFactory)ic0.lookup("/ConnectionFactory");
+
+
+
+ ic1 = getContext(1);
+
+
+
+ ConnectionFactory cf1 = (ConnectionFactory)ic1.lookup("/ConnectionFactory");
+
+
+
+
+
+ connection0 = cf0.createConnection();
+
+
+
+
+
+ connection1 = cf1.createConnection();
+
+
+
+
+
+ Session session0 = connection0.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+
+ Session session1 = connection1.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+
+ connection0.start();
+
+ connection1.start();
+
+
+
+
+
+ MessageConsumer consumer0 = session0.createConsumer(queue);
+
+ MessageConsumer consumer1 = session1.createConsumer(queue);
+
+
+
+
+
+ MessageProducer producer = session0.createProducer(queue);
+
+
+
+
+ final int numMessages = 10;
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session0.createTextMessage("This is text message " + i);
+
+ producer.send(message);
+
+ System.out.println("Sent message: " + message.getText());
+ }
+
+
+
+
+
+ for (int i = 0; i < numMessages; i += 2)
+ {
+ TextMessage message0 = (TextMessage)consumer0.receive(5000);
+
+ System.out.println("Got message: " + message0.getText() + " from node 0");
+
+ TextMessage message1 = (TextMessage)consumer1.receive(5000);
+
+ System.out.println("Got message: " + message1.getText() + " from node 1");
+ }
+
+
+
+
+
+ finally
+ {
+ if (connection0 != null)
+ {
+ connection0.close();
+ }
+
+ if (connection1 != null)
+ {
+ connection1.close();
+ }
+ }
+
+
+
+ JMS Load Balanced Clustered Queue Example
+ +This example demonstrates a JMS queue deployed on two different nodes. The two nodes are configured to form a cluster.
+We then create a consumer on the queue on each node, and we create a producer on only one of the nodes.
+We then send some messages via the producer, and we verify that both consumers receive the sent messages + in a round-robin fashion.
+In other words, HornetQ load balances the sent messages across all consumers on the cluster
+This example uses JNDI to lookup the JMS Queue and ConnectionFactory objects. If you prefer not to use + JNDI, these could be instantiated directly.
+Here's the relevant snippet from the server configuration, which tells the server to form a cluster between the two nodes + and to load balance the messages between the nodes.
+
+ <cluster-connection name="my-cluster">
+ <address>jms</address>
+ <connector-ref>netty-connector</connector-ref>
+ <retry-interval>500</retry-interval>
+ <use-duplicate-detection>true</use-duplicate-detection>
+ <forward-when-no-consumers>true</forward-when-no-consumers>
+ <max-hops>1</max-hops>
+ <discovery-group-ref discovery-group-name="my-discovery-group"/>
+ </cluster-connection>
+
+
+ For more information on HornetQ load balancing, and clustering in general, please see the clustering + section of the user manual.
+Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+
+ ic0 = getContext(0);
+
+
+
+
+ Queue queue = (Queue)ic0.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf0 = (ConnectionFactory)ic0.lookup("/ConnectionFactory");
+
+
+
+ ic1 = getContext(1);
+
+
+
+ ConnectionFactory cf1 = (ConnectionFactory)ic1.lookup("/ConnectionFactory");
+
+
+
+
+
+ connection0 = cf0.createConnection();
+
+
+
+
+
+ connection1 = cf1.createConnection();
+
+
+
+
+
+ Session session0 = connection0.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+
+ Session session1 = connection1.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+
+ connection0.start();
+
+ connection1.start();
+
+
+
+
+
+ MessageConsumer consumer0 = session0.createConsumer(queue);
+
+ MessageConsumer consumer1 = session1.createConsumer(queue);
+
+
+
+
+
+ MessageProducer producer = session0.createProducer(queue);
+
+
+
+
+ final int numMessages = 10;
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session0.createTextMessage("This is text message " + i);
+
+ producer.send(message);
+
+ System.out.println("Sent message: " + message.getText());
+ }
+
+
+
+
+
+ for (int i = 0; i < numMessages; i += 2)
+ {
+ TextMessage message0 = (TextMessage)consumer0.receive(5000);
+
+ System.out.println("Got message: " + message0.getText() + " from node 0");
+
+ TextMessage message1 = (TextMessage)consumer1.receive(5000);
+
+ System.out.println("Got message: " + message1.getText() + " from node 1");
+ }
+
+
+
+
+
+ finally
+ {
+ if (connection0 != null)
+ {
+ connection0.close();
+ }
+
+ if (connection1 != null)
+ {
+ connection1.close();
+ }
+ }
+
+
+
+ JMS Clustered Stand-alone Example
+ +This example demonstrates a JMS Topic deployed on three different nodes. + The three nodes are configured to form a cluster.
+Subscribers for the topic are created on each node, and a producer is created on only one of the nodes.
+Some messages are sent by the producer, and we verify that all subscribers receive all the + sent messages.
+This example uses HornetQ's default stand-alone clustered configuration. + The relevant snippet from the server configuration, which tells the servers to form a cluster between the three nodes + and to load balance the messages between the nodes is:
+
+ <cluster-connection name="my-cluster">
+ <address>jms</address>
+ <discovery-group-ref discovery-group-name="dg-group1"/>
+ </cluster-connection>
+
+
+ Example step-by-step
+To run the example, simply type mvn verify from this directory. This will
+ automatically start the 3 cluster nodes, each with its specific configuration.
To start the tests manually, the following steps are:
+-
+
JMS Completion Listener Example
+ +This example shows you how to send a message asynchronously to HornetQ and use a CompletionListener to be notified of + the Broker receiving it
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ jmsContext = cf.createContext();
+
+
+
+ JMSProducer producer = jmsContext.createProducer();
+
+
+
+ producer.setAsync(new CompletionListener()
+ {
+ @Override
+ public void onCompletion(Message message)
+ {
+ System.out.println("message acknowledged by HornetQ");
+ latch.countDown();
+ }
+
+ @Override
+ public void onException(Message message, Exception e)
+ {
+ e.printStackTrace();
+ }
+ });
+
+
+
+ producer.send(queue, "this is a string");
+
+
+
+ return latch.await(5, TimeUnit.SECONDS);
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (jmsContext != null)
+ {
+ jmsContext.close();
+ }
+ }
+
+
+
+
+ JMS Context Example
+ +This example shows you how to send and receive a message to a JMS Queue using HornetQ by using a JMS Context
+A JMSContext is part of JMS 2.0 and combines the JMS Connection and Session Objects into a simple Interface
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ jmsContext = cf.createContext();
+
+
+
+ jmsContext.createProducer().setDeliveryMode(DeliveryMode.PERSISTENT).send(queue, "this is a string")
+
+
+
+ String payLoad = jmsContext.createConsumer(queue).receiveBody(String.class);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (jmsContext != null)
+ {
+ jmsContext.close();
+ }
+ }
+
+
+
+
+ JMS Shared Consumer Example
+ +This example shows you how can use shared consumers to share a subscription on a topic. In JMS 1.1 this was not allowed + and so caused a scalability issue. In JMS 2 this restriction has been lifted so you can share the load across different + threads and connections.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Topic topic = (Topic) initialContext.lookup("/topic/exampleTopic");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ jmsContext = cf.createContext();
+
+
+
+ JMSProducer producer = jmsContext.createProducer();
+
+
+
+ JMSConsumer jmsConsumer = jmsContext.createSharedConsumer(topic, "sc1");
+
+
+
+ jmsContext2 = cf.createContext();
+
+
+
+ JMSConsumer jmsConsumer2 = jmsContext2.createSharedConsumer(topic, "sc1");
+
+
+
+
+ producer.send(topic, "this is a String!");
+
+ producer.send(topic, "this is a second String!") ;
+
+
+
+
+ String body = jmsConsumer.receiveBody(String.class, 5000);
+
+ body = jmsConsumer2.receiveBody(String.class, 5000);
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (jmsContext != null)
+ {
+ jmsContext.close();
+ }
+ if (jmsContext2 != null)
+ {
+ jmsContext2.close();
+ }
+ }
+
+
+
+
+ JMX Management Example
+ +This example shows how to manage HornetQ using JMX
+ +Example configuration
+ +HornetQ exposes its managed resources by default on the platform MBeanServer.
+To access this MBeanServer remotely, the Java Virtual machine must be started with system properties: +
+ -Dcom.sun.management.jmxremote
+ -Dcom.sun.management.jmxremote.port=3000
+ -Dcom.sun.management.jmxremote.ssl=false
+ -Dcom.sun.management.jmxremote.authenticate=false
+
+ These properties are explained in the Java 5 Management guide + (please note that for this example, we will disable user authentication for simplicity sake).
+With these properties, HornetQ server will be manageable remotely using standard JMX URL on port 3000.
Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext(0);
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(topic);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+
+ messageProducer.send(message);
+
+
+ Now that we have a message in the queue, we will manage the queue by retrieving the number of messages in the queue + (i.e. 1) and by removing the message which has been sent in step 8.
+ +
+ ObjectName on = ObjectNameBuilder.DEFAULT.getJMSQueueObjectName(queue.getQueueName());
+
+
+
+ JMXConnector connector = JMXConnectorFactory.connect(new JMXServiceURL(JMX_URL), new HashMap());
+
+
+
+ TextMessage messageReceived = (TextMessage) messageConsumer.receive(5000);
+
+
+
+ JMSQueueControl queueControl = (JMSQueueControl)MBeanServerInvocationHandler.newProxyInstance(mbsc,
+ on,
+ JMSQueueControl.class,
+ false);
+
+
+
+
+ System.out.println(queueControl.getName() + " contains " + queueControl.getMessageCount() + " messages");
+
+
+
+ System.out.println("message has been removed: " + queueControl.removeMessage(message.getJMSMessageID()));
+
+
+
+ System.out.println(queueControl.getName() + " contains " + queueControl.getMessageCount() + " messages");
+
+
+
+ connector.close()
+
+
+ We will now try to consume the message sent to the queue but it won't be there: it has been removed by the management operation
+ +
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+
+
+ connection.start();
+
+
+
+ TextMessage messageReceived = (TextMessage) messageConsumer.receive(5000);
+ System.out.println("Received message: " + messageReceived);
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ More information
+ +-
+
Large Message Example
+ +This example shows you how to send and receive very large messages with HornetQ.
+HornetQ supports the sending and receiving of huge messages, much larger than can fit in available RAM + on the client or server. Effectively the only limit to message size is the amount of disk space you have on the server.
+Large messages are persisted on the server so they can survive a server restart. In other words HornetQ doesn't just + do a simple socket stream from the sender to the consumer.
+In order to do this HornetQ provides an extension to JMS where you can use an InputStream or OutputStream as the source and destination for your messages. You can send messages as large as it would fit in your disk.
+You may also choose to read LargeMessages using the regular ByteStream or ByteMessage methods, but using the InputStream and OutputStream will provide you a much better performance
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
In this example we limit both the server and the client to be running in a maximum of 50MB of RAM, + and we send a message with a body of size 256MB.
+HornetQ can support much large message sizes but we + choose these sizes and limit RAM so the example runs more quickly.
+We create a file on disk representing the message body, create + a FileInputStream on that file and set that InputStream as the body of the message before sending.
+The message is sent, then we stop the server, and restart it. This demonstrates the large message will survive a restart of the server.
+Once the server is restarted we receive the message and stream it's body to another file on disk.
+ +-
+
+ initialContext = getContext(0);
+
+
+
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+
+
+ connection = cf.createConnection();
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+ MessageProducer producer = session.createProducer(queue);
+
+
+
+
+
+ File fileInput = new File("huge_message_to_send.dat");
+
+ fileInput.createNewFile();
+
+ createFile(fileInput, FILE_SIZE);
+
+
+
+
+ BytesMessage message = session.createBytesMessage();
+
+
+
+ FileInputStream fileInputStream = new FileInputStream(fileInput);
+
+ BufferedInputStream bufferedInput = new BufferedInputStream(fileInputStream);
+
+ message.setObjectProperty("JMS_HQ_InputStream", bufferedInput);
+
+ producer.send(message);
+
+ messageProducer.send(message);
+
+
+
+
+ connection.close();
+
+ initialContext.close();
+
+ stopServer(0);
+
+ // Give the server a little time to shutdown properly
+ Thread.sleep(5000);
+
+ startServer(0);
+
+
+
+
+
+ initialContext = getContext(0);
+
+ queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+
+ cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+ connection = cf.createConnection();
+
+ session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+ connection.start();
+
+
+
+
+ BytesMessage messageReceived = (BytesMessage)messageConsumer.receive(120000);
+
+ File outputFile = new File("huge_message_received.dat");
+
+ FileOutputStream fileOutputStream = new FileOutputStream(outputFile);
+
+ BufferedOutputStream bufferedOutput = new BufferedOutputStream(fileOutputStream);
+
+
+ messageReceived.setObjectProperty("JMS_HQ_SaveStream", bufferedOutput);
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+ * This may take some considerable time to create, send and consume - if it takes too long or you
+ * don't have enough disk space just reduce the file size here
+ */
+ private static final long FILE_SIZE = 2L * 1024 * 1024 * 1024; // 10 GiB message
+
+ @Override
+ public boolean runExample() throws Exception
+ {
+ Connection connection = null;
+ InitialContext initialContext = null;
+
+ try
+ {
+ // Step 1. Create an initial context to perform the JNDI lookup.
+ initialContext = getContext(0);
+
+ // Step 2. Perfom a lookup on the queue
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+
+ // Step 3. Perform a lookup on the Connection Factory. This ConnectionFactory has a special attribute set on
+ // it.
+ // Messages with more than 10K are considered large
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+ // Step 4. Create the JMS objects
+ connection = cf.createConnection();
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+ MessageProducer producer = session.createProducer(queue);
+
+ // Step 5. Create a huge file - this will form the body of the message we will send.
+
+ System.out.println("Creating a file to send of size " + FILE_SIZE +
+ " bytes. This may take a little while... " +
+ "If this is too big for your disk you can easily change the FILE_SIZE in the example.");
+
+ File fileInput = new File("huge_message_to_send.dat");
+
+ createFile(fileInput, FILE_SIZE);
+
+ System.out.println("File created.");
+
+ // Step 6. Create a BytesMessage
+ BytesMessage message = session.createBytesMessage();
+
+ // Step 7. We set the InputStream on the message. When sending the message will read the InputStream
+ // until it gets EOF. In this case we point the InputStream at a file on disk, and it will suck up the entire
+ // file, however we could use any InputStream not just a FileInputStream.
+ FileInputStream fileInputStream = new FileInputStream(fileInput);
+ BufferedInputStream bufferedInput = new BufferedInputStream(fileInputStream);
+
+ message.setObjectProperty("JMS_HQ_InputStream", bufferedInput);
+
+ System.out.println("Sending the huge message.");
+
+ // Step 9. Send the Message
+ producer.send(message);
+
+ System.out.println("Large Message sent");
+
+ System.out.println("Stopping server.");
+
+ // Step 10. To demonstrate that that we're not simply streaming the message from sending to consumer, we stop
+ // the server and restart it before consuming the message. This demonstrates that the large message gets
+ // persisted, like a
+ // normal persistent message, on the server. If you look at ./build/data/largeMessages you will see the
+ // largeMessage stored on disk the server
+
+ connection.close();
+
+ initialContext.close();
+
+ killServer(0);
+
+ // Give the server a little time to shutdown properly
+ Thread.sleep(5000);
+
+ reStartServer(0, 60000);
+
+ System.out.println("Server restarted.");
+
+ // Step 11. Now the server is restarted we can recreate the JMS Objects, and start the new connection
+
+ initialContext = getContext(0);
+
+ queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+
+ cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+ connection = cf.createConnection();
+
+ session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+ connection.start();
+
+ System.out.println("Receiving message.");
+
+ // Step 12. Receive the message. When we receive the large message we initially just receive the message with
+ // an empty body.
+ BytesMessage messageReceived = (BytesMessage)messageConsumer.receive(120000);
+
+ System.out.println("Received message with: " + messageReceived.getLongProperty("_HQ_LARGE_SIZE") +
+ " bytes. Now streaming to file on disk.");
+
+ // Step 13. We set an OutputStream on the message. This causes the message body to be written to the
+ // OutputStream until there are no more bytes to be written.
+ // You don't have to use a FileOutputStream, you can use any OutputStream.
+ // You may choose to use the regular BytesMessage or
+ // StreamMessage interface but this method is much faster for large messages.
+
+ File outputFile = new File("huge_message_received.dat");
+
+ FileOutputStream fileOutputStream = new FileOutputStream(outputFile);
+
+ BufferedOutputStream bufferedOutput = new BufferedOutputStream(fileOutputStream);
+
+ // Step 14. This will save the stream and wait until the entire message is written before continuing.
+ messageReceived.setObjectProperty("JMS_HQ_SaveStream", bufferedOutput);
+
+ fileOutputStream.close();
+
+ System.out.println("File streamed to disk. Size of received file on disk is " + outputFile.length());
+
+ return true;
+ }
+ finally
+ {
+ // Step 12. Be sure to close our resources!
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+ }
+
+ /**
+ * @param file
+ * @param fileSize
+ * @throws FileNotFoundException
+ * @throws IOException
+ */
+ private void createFile(final File file, final long fileSize) throws IOException
+ {
+ FileOutputStream fileOut = new FileOutputStream(file);
+ BufferedOutputStream buffOut = new BufferedOutputStream(fileOut);
+ byte[] outBuffer = new byte[1024 * 1024];
+ for (long i = 0; i < fileSize; i += outBuffer.length)
+ {
+ buffOut.write(outBuffer);
+ }
+ buffOut.close();
+ }
+
+}
diff --git a/examples/jms/large-message/src/main/resources/hornetq/server0/hornetq-configuration.xml b/examples/jms/large-message/src/main/resources/hornetq/server0/hornetq-configuration.xml
new file mode 100644
index 0000000000..51136028ac
--- /dev/null
+++ b/examples/jms/large-message/src/main/resources/hornetq/server0/hornetq-configuration.xml
@@ -0,0 +1,42 @@
+
Last-Value Queue Example
+ +This example shows you how to configure and use last-value queues.
+Last-Value queues are special queues which discard any messages when a newer message with the same value for a well-defined Last-Value property is put in the queue. + In other words, a Last-Value queue only retains the last value.
+A typical example for Last-Value queue is for stock prices, where you are only interested by the latest value for a particular stock.
+ +The example will send 3 messages with the same Last-Value property to a to a Last-Value queue.
+ We will browse the queue and see that only the last message is in the queue, the first two messages have been discarded.
+ We will then consume from the queue the last message.
Example setup
+Last-Value queues are defined in the configuration file hornetq-configuration.xml:
+
+ <address-setting match="jms.queue.lastValueQueue">
+ <last-value-queue>true</last-value-queue>
+ </address-setting>
+
+
+ Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/lastValueQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+ MessageProducer producer = session.createProducer(queue);
+
+
+
+ TextMessage message = session.createTextMessage("1st message with Last-Value property set");
+ message.setStringProperty("_HQ_LVQ_NAME", "STOCK_NAME");
+ producer.send(message);
+ System.out.format("Sent message: %s\n", message.getText());
+
+
+ The Last-Value key is defined in HornetQ's MessageImpl class. Its value is "_HQ_LVQ_NAME"
+ message = session.createTextMessage("2nd message with Last-Value property set");
+ message.setStringProperty("_HQ_LVQ_NAME", "STOCK_NAME");
+ producer.send(message);
+ System.out.format("Sent message: %s\n", message.getText());
+
+
+
+ message = session.createTextMessage("3rd message with Last-Value property set");
+ message.setStringProperty("_HQ_LVQ_NAME", "STOCK_NAME");
+ producer.send(message);
+ System.out.format("Sent message: %s\n", message.getText());
+
+
+ When the 2nd message was sent to the queue, the 1st message was discarded.
+ Similarly, when the 3rd message was sent to the queue, the 2nd message was discarded.
+ Only the 3rd message remains in the queue.
+ QueueBrowser browser = session.createBrowser(queue);
+ Enumeration enumeration = browser.getEnumeration();
+ while (enumeration.hasMoreElements())
+ {
+ TextMessage messageInTheQueue = (TextMessage)enumeration.nextElement();
+ System.out.format("Message in the queue: %s\n", messageInTheQueue.getText());
+ }
+ browser.close();
+
+
+
+ We will now consume the message on the queue
+ +
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+
+
+ connection.start();
+
+
+
+ TextMessage messageReceived = (TextMessage)messageConsumer.receive(5000);
+ System.out.format("Received message: %s\n", messageReceived.getText());
+
+
+
+ messageReceived = (TextMessage)messageConsumer.receive(5000);
+ System.out.format("Received message: %s\n", messageReceived);
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ More information
+ +-
+
Management Notification Example
+This example shows how to receive management notifications from HornetQ using JMS Messages.
+HornetQ servers emit management notifications when events of interest occur (consumers are created or closed,
+ destinations are created or deleted, security authentication fails, etc.).
+ These notifications can be received either by using JMX (see JMX example) or by receiving JMS Messages
+ from a well-known destination.
This example will setup a JMS MessageListener to receive management notifications. We will also perform normal JMS operations to see the kind + of notifications they trigger.
+ +Example configuration
+ +HornetQ can configured to send JMS messages when management notifications are emitted on the server.
+By default, the management name is called hornetq.notifications but this can be configured in hornetq-configuration.xml.
+ For this example, we will set it to jms.topic.notificationsTopic to be able to receive notifications from a JMS Topic.
+ <management-notification-address>jms.topic.notificationsTopic</management-notification-address>
+
+
+ Since we want to lookup the notifications topic using JNDI, we also declare it in hornetq-jms.xml +
+ <topic name="notificationsTopic">
+ <entry name="/topic/notificationsTopic"/>
+ </topic>
+
+ The notification queue requires permission to create/delete temporary queues and consume messages. + This is also configured in hornetq-configuration.xml
+
+
+ <security-setting match="jms.topic.notificationsTopic">
+ <permission type="consume" roles="guest"/>
+ <permission type="createNonDurableQueue" roles="guest"/>
+ <permission type="deleteNonDurableQueue" roles="guest"/>
+ </security-setting>
+
+
+ Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext(0);
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+ MessageProducer producer = session.createProducer(queue);
+
+
+
+ Topic notificationsTopic = (Topic) initialContext.lookup("/topic/notificationsTopic");
+
+
+
+ MessageConsumer notificationConsumer = session.createConsumer(notificationsTopic);
+ notificationConsumer.setMessageListener(new MessageListener()
+ {
+ public void onMessage(Message notif)
+ {
+ System.out.println("------------------------");
+ System.out.println("Received notification:");
+ try
+ {
+ Enumeration propertyNames = notif.getPropertyNames();
+ while (propertyNames.hasMoreElements())
+ {
+ String propertyName = (String)propertyNames.nextElement();
+ System.out.format(" %s: %s\n", propertyName, notif.getObjectProperty(propertyName));
+ }
+ }
+ catch (JMSException e)
+ {
+ }
+ System.out.println("------------------------");
+ }
+ });
+
+
+
+ connection.start();
+
+
+ Now that a message listener is setup to receive management notifications, we will perform regular JMS operations to + see what kind of notifications are triggered
+ +
+ MessageConsumer consumer = session.createConsumer(queue);
+
+
+ This will generate a CONSUMER_CREATED notification:
+
+ ------------------------
+ Received notification:
+ _HQ_RoutingName: jms.queue.exampleQueue
+ _HQ_Address: jms.queue.exampleQueue
+ ...
+ _HQ_ConsumerCount: 1
+ ...
+ _HQ_NotifType: CONSUMER_CREATED
+ ------------------------
+
+ The notification tells us that a consumer was created for the JMS queue exampleQueue. When the notification
+ was emitted, this consumer was the only one for the queue
+ consumer.close();
+
+
+ This will generate a CONSUMER_CLOSED notification:
+
+ ------------------------
+ Received notification:
+ _HQ_RoutingName: jms.queue.exampleQueue
+ _HQ_Address: jms.queue.exampleQueue
+ ...
+ _HQ_ConsumerCount: 0
+ ...
+ _HQ_NotifType: CONSUMER_CLOSED
+ ------------------------
+
+ The notification tells us that a consumer was closed for the JMS queue exampleQueue. When the notification
+ was emitted, there were no other consumers on the queue
+ try
+ {
+ cf.createConnection("not.a.valid.user", "not.a.valid.password");
+ } catch (JMSException e)
+ {
+ }
+
+
+ This will generate a SECURITY_AUTHENTICATION_VIOLATION notification:
+
+ ------------------------
+ Received notification:
+ _HQ_User: not.a.valid.user
+ ...
+ _HQ_NotifType: SECURITY_AUTHENTICATION_VIOLATION
+ ------------------------
+
+
+ The notification tells us that a user named not.a.valid.user failed to authenticate when creating a connection to HornetQ.
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ More information
+ +-
+
Management Example
+This example shows how to manage HornetQ using JMS Messages to invoke management operations on the server.
To manage HornetQ using JMX, see the JMX example.
+ +Example configuration
+ +HornetQ can be managed by sending JMS messages with specific properties to its management queue.
+ By default, the management name is calledhornetq.management but this can be configured in hornetq-configuration.xml
+
+ <management-address>hornetq.management</management-address>
+
+
+ The management queue requires a "special" user permission manage to be able to receive management messages.
+ This is also configured in hornetq-configuration.xml
+ <security-setting match="hornetq.management">
+ <permission type="manage" roles="guest" />
+ </security-setting>
+
+
+ Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext(0);
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(topic);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+
+ messageProducer.send(message);
+
+
+ Now that we have a message in the queue, we will manage the queue by retrieving the number of messages in the queue + (i.e. 1) and by removing the message which has been sent in step 8.
+ +
+ Queue managementQueue = new HornetQQueue("hornetq.management", "hornetq.management");
+
+
+
+ QueueRequestor requestor = new QueueRequestor(session, managementQueue);
+
+
+
+ connection.start()
+
+
+
+ Message m = session.createMessage();
+
+
+
+ JMSManagementHelper.putAttribute(m, "jms.queue.exampleQueue", "MessageCount");
+
+
+
+ Message reply = requestor.request(m);
+
+
+
+ m = session.createMessage();
+
+
+
+ JMSManagementHelper.putOperationInvocation(m, "jms.queue.exampleQueue", "removeMessage", message.getJMSMessageID());
+
+
+
+ reply = requestor.request(m);
+
+
+
+ boolean success = JMSManagementHelper.hasOperationSucceeded(reply);
+ System.out.println("operation invocation has succeeded: " + success);
+
+
+
+ boolean messageRemoved = (Boolean)JMSManagementHelper.getResult(reply);
+ System.out.println("message has been removed: " + messageRemoved);
+
+
+ We will now consume the message from the queue but there will be none: the message sent at step 8 was removed by the management operation
+ +
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+
+
+ TextMessage messageReceived = (TextMessage) messageConsumer.receive(5000);
+ System.out.println("Received message: " + messageReceived);
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ More information
+ +-
+
JMS Message Counter Example
+ +This example shows you how to use message counters to obtain message information for a JMS queue.
+The example will show how to configure sampling of message counters.
+ We will produce and consume 1 message from a queue. Interleaved with the JMS operation, we will retrieve the queue's message counters
+ at different times to display the metrics on the queue.
+
Example setup
+Message counter is configured in the server configuration file hornetq-configuration.xml:
+
+ <message-counter-enabled>true</message-counter-enabled>
+ <message-counter-sample-period>2000</message-counter-sample-period>
+ <message-counter-max-day-history>2</message-counter-max-day-history>
+
+ By default, Message counter is not enabled (for performance reason). To enable them, set message-counter-enabled to true.
+ Queues are sampled every 10 seconds by default. For this example we will reduce it to 2 seconds by setting message-counter-sample-period to 2000.
+ HornetQ holds in memory the message counters' history for a maximum number of days (10 by default). We can change the number of days the history is kept by setting
+ the message-counter-max-day-history parameter.
The sample period and the max day history parameters have an small impact on the performance of HornetQ (the resources taken to sample a queue are not available to the system's + normal use). You should set these parameters accordingly to the use and throughput of your messages.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createQueueConnection();
+ QueueSession session = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
+ MessageProducer producer = session.createProducer(queue);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+ producer.send(message);
+ System.out.println("Sent message: " + message.getText());
+
+
+
+ System.out.println("Sleep a little bit to have the queue sampled...");
+ Thread.sleep(3000);
+
+
+ We now need to retrieve the message counters. They're available from the JMS Queue management resource. In this example, we + will retrieve them using JMX (see the JMX example for a more complete description). You can also use JMS message to retrieve them (see the Management example to + learn about managing HornetQ using JMS messages).
+ +
+ ObjectName on = ObjectNameBuilder.DEFAULT.getJMSQueueObjectName(queue.getQueueName());
+ JMXConnector connector = JMXConnectorFactory.connect(new JMXServiceURL(JMX_URL), new HashMap());
+ MBeanServerConnection mbsc = connector.getMBeanServerConnection();
+ JMSQueueControl queueControl = (JMSQueueControl)MBeanServerInvocationHandler.newProxyInstance(mbsc,
+ on,
+ JMSQueueControl.class,
+ false);
+
+
+
+ String counters = queueControl.listMessageCounter();
+ MessageCounterInfo messageCounter = MessageCounterInfo.fromJSON(counters);>
+
+
+
+ displayMessageCounter(messageCounter);
+
+
+ The message counter contains a variety of metrics on the queue which is sampled (total messages added to the queue, current depth of the queue, deltas since the last sample, timestamp + of the last message added, timestamp of the last sample, etc.)
+
+
+ private void displayMessageCounter(MessageCounterInfo counter)
+ {
+ System.out.format("%s (sample updated at %s)\n", counter.getName(), counter.getUdpateTimestamp());
+ System.out.format(" %s message(s) added to the queue (since last sample: %s)\n", counter.getCount(),
+ counter.getCountDelta());
+ System.out.format(" %s message(s) in the queue (since last sample: %s)\n", counter.getDepth(),
+ counter.getDepthDelta());
+ System.out.format(" last message added at %s\n\n", counter.getLastAddTimestamp());
+ }
+
+
+
+ System.out.println("Sleep a little bit again...");
+ Thread.sleep(3000);
+
+
+
+ counters = queueControl.listMessageCounter();
+ messageCounter = MessageCounterInfo.fromJSON(counters);
+ displayMessageCounter(messageCounter);
+
+
+ We will now consume a message from the queue before listing a last time the message counters
+ +
+ MessageConsumer consumer = session.createConsumer(queue);
+
+
+
+ connection.start();
+
+
+
+ TextMessage messageReceived = (TextMessage)consumer.receive(5000);
+ System.out.format("Received message: %s\n\n", messageReceived.getText());
+
+
+
+ System.out.println("Sleep a little bit one last time...");
+ Thread.sleep(3000);
+
+
+
+ counters = queueControl.listMessageCounter();
+ messageCounter = MessageCounterInfo.fromJSON(counters);
+ displayMessageCounter(messageCounter);
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ Message Group Example
+ +This example shows you how to configure and use message groups with HornetQ.
+ +Message groups are sets of messages that has the following characteristics:
+You can make any message belong to a message group by setting its 'JMXGroupID' string property to the group id. + In this example we create a message group 'Group-0'. And make such a message group of 10 messages. It also create two consumers on the queue + where the 10 'Group-0' group messages are to be sent. You can see that with message grouping enabled, all the 10 messages will be received by + the first consumer. The second consumer will receive none.
+ +Alternatively, HornetQ's connection factories can be configured to auto group messages. By setting autogroup to true on the HornetQConnectionFactory
+ (or setting <autogroup>true</autogroup> in hornetq-jms.xml's connection factory settings), a random unique id
+ will be picked to create a message group. Every messages sent by a producer created from this connection factory will automatically
+ be part of this message group.
Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(topic);
+
+
+
+
+ MessageConsumer consumer1 = session.createConsumer(queue);
+ consumer1.setMessageListener(new SimpleMessageListener("consumer-1"));
+ MessageConsumer consumer2 = session.createConsumer(queue);
+ consumer2.setMessageListener(new SimpleMessageListener("consumer-2"));
+
+
+
+
+
+ int msgCount = 10;
+ TextMessage[] groupMessages = new TextMessage[msgCount];
+ for (int i = 0; i < msgCount; i++)
+ {
+ groupMessages[i] = session.createTextMessage("Group-0 message " + i);
+ groupMessages[i].setStringProperty("JMSXGroupID", "Group-0");
+ producer.send(groupMessages[i]);
+ System.out.println("Sent message: " + groupMessages[i].getText());
+ }
+
+
+
+
+ connection.start();
+
+
+
+
+ String trueReceiver = messageReceiverMap.get(groupMessages[0].getText());
+ for (TextMessage grpMsg : groupMessages)
+ {
+ String receiver = messageReceiverMap.get(grpMsg.getText());
+ if (!trueReceiver.equals(receiver))
+ {
+ System.out.println("Group message [" + grpMsg.getText() + "[ went to wrong receiver: " + receiver);
+ result = false;
+ }
+ }
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ More information
+ +-
+
Message Group Example
+ +This example shows you how to configure and use message groups via a connection factory with HornetQ.
+ +Message groups are sets of messages that has the following characteristics:
+You can make any message belong to a message group by setting a 'group-id' on the connection factory. All producers created via this connection factory will set that group id on its messages. + In this example we set the group id 'Group-0'on a connection factory and send messages via 2 different producers and check that only 1 consumer receives them.
+ +Alternatively, HornetQ's connection factories can be configured to auto group messages. By setting autogroup to true on the HornetQConnectionFactory
+ (or setting <autogroup>true</autogroup> in hornetq-jms.xml's connection factory settings), a random unique id
+ will be picked to create a message group. Every messages sent by a producer created from this connection factory will automatically
+ be part of this message group.
Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+ MessageProducer producer1 = session.createProducer(queue);
+
+ MessageProducer producer2 = session.createProducer(queue);
+
+
+
+
+ MessageConsumer consumer1 = session.createConsumer(queue);
+ consumer1.setMessageListener(new SimpleMessageListener("consumer-1"));
+ MessageConsumer consumer2 = session.createConsumer(queue);
+ consumer2.setMessageListener(new SimpleMessageListener("consumer-2"));
+
+
+
+
+
+ int msgCount = 10;
+ for (int i = 0; i < msgCount; i++)
+ {
+ TextMessage m = session.createTextMessage("producer1 message " + i);
+ producer1.send(m);
+ System.out.println("Sent message: " + m.getText());
+ TextMessage m2 = session.createTextMessage("producer2 message " + i);
+ producer2.send(m2);
+ System.out.println("Sent message: " + m2.getText());
+ }
+
+
+
+
+ connection.start();
+
+
+
+
+ String trueReceiver = messageReceiverMap.get("producer1 message " + 0);
+ for (int i = 0; i < msgCount; i++)
+ {
+ String receiver = messageReceiverMap.get("producer1 message " + i);
+ if (!trueReceiver.equals(receiver))
+ {
+ System.out.println("Group message [producer1 message " + i + "] went to wrong receiver: " + receiver);
+ result = false;
+ }
+ receiver = messageReceiverMap.get("producer2 message " + i);
+ if (!trueReceiver.equals(receiver))
+ {
+ System.out.println("Group message [producer2 message " + i + "] went to wrong receiver: " + receiver);
+ result = false;
+ }
+ }
+
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ More information
+ +-
+
JMS Message Priority Example
+ +This example shows how messages with different priorities are delivered in different orders.
+ +The Message Priority property carries the delivery preference of sent messages. It can be set by the message's + standard header field 'JMSPriority' as defined in JMS specification version 1.1. The value is of type + integer, ranging from 0 (the lowest) to 9 (the highest). When messages are being delivered, their priorities + will effect their order of delivery. Messages of higher priorities will likely be delivered before those + of lower priorities. Messages of equal priorities are delivered in the natural order of their arrival at + their destinations. Please consult the JMS 1.1 specification for full details.
+ +In this example, three messages are sent to a queue with different priorities. The first message is sent + with default priority (4), the second is sent with a higher priority (5), and the third has the highest + priority (9). At the receiving end, we will show the order of receiving of the three messages. You will + see that the third message, though last sent, will 'jump' forward to be the first one received. The second + is also received ahead of the message first sent, but behind the third message. The first message, regardless + of its being sent first, arrives last.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(topic);
+
+
+
+
+ MessageConsumer redConsumer = session.createConsumer(queue);
+ redConsumer.setMessageListener(new SimpleMessageListener());
+
+
+
+
+
+ TextMessage[] sentMessages = new TextMessage[3];
+ sentMessages[0] = session.createTextMessage("first message");
+ sentMessages[1] = session.createTextMessage("second message");
+ sentMessages[2] = session.createTextMessage("third message");
+
+
+
+
+
+ producer.send(sentMessages[0]);
+ System.out.println("Message sent: " + sentMessages[0].getText() + " with priority: " + sentMessages[0].getJMSPriority());
+ producer.send(sentMessages[1], DeliveryMode.NON_PERSISTENT, 5, 0);
+ System.out.println("Message sent: " + sentMessages[1].getText() + "with priority: " + sentMessages[1].getJMSPriority());
+ producer.send(sentMessages[2], DeliveryMode.NON_PERSISTENT, 9, 0);
+ System.out.println("Message sent: " + sentMessages[2].getText() + "with priority: " + sentMessages[2].getJMSPriority());
+
+
+
+
+
+ connection.start();
+
+
+
+
+
+ Thread.sleep(5000);
+
+
+
+
+
+ for (int i = 0; i < 3; i++)
+ {
+ TextMessage rm = msgReceived.get(i);
+ if (!rm.getText().equals(sentMessages[2-i].getText()))
+ {
+ System.err.println("Priority is broken!");
+ result = false;
+ }
+ }
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ No Consumer Buffering Example
+ +By default, HornetQ consumers buffer messages from the server in a client side buffer + before actual delivery actually occurs.
+This improves performance since otherwise every time you called receive() or had processed the last + message in a MessageListener onMessage() method, the HornetQ client would have to go the + server to request the next message involving a network round trip for every message reducing performance.
+Therefore, by default, HornetQ pre-fetches messages into a buffer on each consumer. The total maximum size of
+ messages in bytes that will be buffered on each consumer is determined by the consumer-window-size
+ parameter on the connection factory.
In some cases it is not desirable to buffer any messages on the client side consumer.
+An example would be an order queue which had multiple consumers that processed orders from the queue. + Each order takes a significant time to process, but each one should be processed in a timely fashion.
+If orders were buffered in each consumer, and a new consumer was added that consumer would not be able + to process orders which were already in the client side buffer of another consumer.
+To turn off client side buffering of messages, set consumer-window-size to zero.
With HornetQ you can specify a maximum consume rate at which a JMS MessageConsumer will consume messages.
+ This can be specified when creating or deploying the connection factory. See hornetq-jms.xml
Example step-by-step
+In this example we specify a consumer-window-size of 0 bytes in the hornetq-jms.xml
+ file when deploying the connection factory:
+
+ <connection-factory name="ConnectionFactory">
+ <connector-ref connector-name="netty-connector"/>
+ <entries>
+ <entry name="ConnectionFactory"/>
+ </entries>
+
+ <!-- We set the consumer window size to 0, which means messages are not buffered at all
+ on the client side -->
+ <consumer-window-size>0</consumer-window-size>
+
+ </connection-factory>
+
+
+ We create a consumer on a queue and send 10 messages to it. We then create another consumer on + the same queue.
+We then consume messages from each consumer in a semi-random order. We note that the messages + are consumed in the order they were sent.
+If the messages had been buffered in each consumer they would not be available to be consumed + in an order determined afer delivery.
+ +To run the example, simply type mvn verify from this directory
-
+
+ initialContext = getContext(0);
+
+
+
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer producer = session.createProducer(queue);
+
+
+
+ MessageConsumer consumer1 = session.createConsumer(queue);
+
+
+
+
+ connection.start();
+
+
+
+
+
+
+ final int numMessages = 10;
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session.createTextMessage("This is text message: " + i);
+
+ producer.send(message);
+ }
+
+
+
+
+ MessageConsumer consumer2 = session.createConsumer(queue);
+
+
+
+
+ for (int i = 0; i < 3; i++)
+ {
+ TextMessage message = (TextMessage)consumer2.receive(2000);
+
+ System.out.println("Consumed message from consumer2: " + message.getText());
+ }
+
+
+
+
+
+ for (int i = 0; i < 5; i++)
+ {
+ TextMessage message = (TextMessage)consumer1.receive(2000);
+
+ System.out.println("Consumed message from consumer1: " + message.getText());
+ }
+
+
+
+
+
+ for (int i = 0; i < 2; i++)
+ {
+ TextMessage message = (TextMessage)consumer1.receive(2000);
+
+ System.out.println("Consumed message from consumer2: " + message.getText());
+ }
+
+
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ More information
+ +-
+
JMS Failover Without Transactions Example
+ +This example demonstrates two servers coupled as a live-backup pair for high availability (HA), and a client + connection failing over from live to backup when the live server is crashed.
+Failover behavior differs whether the JMS session is transacted or not.
+When a non-transacted JMS session is used, once and only once delivery is not guaranteed + and it is possible some messages will be lost or delivered twice, depending when the failover to the backup server occurs.
+It is up to the client to deal with such cases. To ensure once and only once delivery, the client must + use transacted JMS sessions (as shown in the example for failover with transactions).
+For more information on HornetQ failover and HA, and clustering in general, please see the clustering + section of the user manual.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
In this example, the live server is server 1, and the backup server is server 0
+The connection will initially be created to server1, server 1 will crash, and the client will carry on + seamlessly on server 0, the backup server.
+-
+
+ initialContext = getContext(1); ++ +
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+ ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+ + connection = connectionFactory.createConnection(); ++ +
+ Session session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE); ++ +
+ connection.start(); ++ +
+ MessageProducer producer = session.createProducer(queue); + MessageConsumer consumer = session.createConsumer(queue); ++ +
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session.createTextMessage("This is text message " + i);
+ producer.send(message);
+ System.out.println("Sent message: " + message.getText());
+ }
+
+
+
+ TextMessage message0 = null;
+ for (int i = 0; i < numMessages / 2; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+ message0.acknowledge();
+
+
+
+ for (int i = numMessages / 2; i < numMessages; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+
+
+ + killServer(1); + Thread.sleep(2000); ++ +
+ try
+ {
+ message0.acknowledge();
+ }
+ catch (JMSException e)
+ {
+ System.err.println("Got exception while acknowledging message: " + e.getMessage());
+ }
+
+
+
+ for (int i = numMessages / 2; i < numMessages; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.printf("Got message: %s (redelivered?: %s)\n", message0.getText(), message0.getJMSRedelivered());
+ }
+ message0.acknowledge();
+
+
+
+ finally
+ {
+ if (connection != null)
+ {
+ connection.close();
+ }
+
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ }
+
+
+ Paging Example
+ +This example shows how HornetQ would avoid running out of memory resources by paging messages.
+A maxSize can be specified per Destination via the destinations settings configuration file (hornetq-configuration.xml).
+When messages routed to an address exceed the specified maxSize the server will begin to write messages to the file + system, this is called paging. This will continue to occur until messages have been delivered to consumers and subsequently + acknowledged freeing up memory. Messages will then be read from the file system , i.e. depaged, and routed as normal.
+Acknowledgement plays an important factor on paging as messages will stay on the file system until the memory is released + so it is important to make sure that the client acknowledges its messages.
+ + +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ Queue pageQueue = (Queue) initialContext.lookup("/queue/pagingQueue");
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE);
+
+
+
+
+ MessageProducer pageMessageProducer = session.createProducer(pageQueue);
+
+ pageMessageProducer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
+
+ BytesMessage message = session.createBytesMessage();
+ message.writeBytes(new byte[10 * 1024]);
+
+ for (int i = 0; i < 20; i++)
+ {
+ pageMessageProducer.send(message);
+ }
+
+ MessageProducer messageProducer = session.createProducer(queue);
+
+ messageProducer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
+
+ for (int i = 0; i < 30000; i++)
+ {
+ messageProducer.send(message);
+ }
+
+ // Thread.sleep(30000); // if you want to just our of curiosity, you can sleep here and inspect the created files just for
+
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+ connection.start();
+
+ for (int i = 0; i < 30000; i++)
+ {
+ message = (BytesMessage)messageConsumer.receive(1000);
+
+ if (i % 1000 == 0)
+ {
+ System.out.println("Received " + i + " messages");
+
+ message.acknowledge();
+ }
+ }
+
+ messageConsumer.close();
+ messageConsumer = session.createConsumer(pageQueue);
+
+ for (int i = 0; i < 20; i++)
+ {
+ message = (BytesMessage)messageConsumer.receive(1000);
+
+ System.out.println("Received message " + i + " from pageQueue");
+
+ message.acknowledge();
+ }
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+ JMS Simple Performance
+ +To start the server run mvn verify
To start the listener run mvn -Plistener package
To start the sender run mvn -Psender package
To configure the clients simply edit the perf.properties or client.jndi.properties in the
+ src/main/resources directory
JMS Pre-Acknowledge Example
+ +Standard JMS supports three acknowledgement modes: AUTO_ACKNOWLEDGE, CLIENT_ACKNOWLEDGE, and + DUPS_OK_ACKNOWLEDGE. For a full description on these modes please consult the JMS specification, or any + JMS tutorial.
+All of these standard modes involve sending acknowledgements from the client to the server. However + in some cases, you really don't mind losing messages in event of failure, so it would make sense + to acknowledge the message on the server before delivering it to the client.
+By acknowledging the message before sending to the client, you can avoid extra network traffic and CPU + work done in sending acknowledgements from client to server.
+The down-side of acknowledging on the server before delivery, is that if the system crashes after acknowledging + the message, but before the message has been received by the client, then, on recovery, that message + will be lost. This makes pre-acknowledgement not appropriate for all use cases, but it is very useful for some + use-cases when you can cope with such loss of messages
+
An example of a use-case where it might be a good idea to use pre-acknowledge, is for stock price update + messages. With these messages it might be ok to lose a message in event of crash, since the next price + update message will arrive soon, overriding the previous price.
+In order to use pre-acknowledge functionality with HornetQ the session has to be created with
+ a special, HornetQ specific acknowledgement mode, given by the value of
+ HornetQJMSConstants.PRE_ACKNOWLEDGE.
+
Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+
+ initialContext = getContext(0);
+
+
+
+
+
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+
+
+
+ connection = cf.createConnection();
+
+ Session session = connection.createSession(false, HornetQSession.PRE_ACKNOWLEDGE);
+
+ MessageProducer producer = session.createProducer(queue);
+
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+
+
+
+
+ TextMessage message1 = session.createTextMessage("This is a text message 1");
+
+ producer.send(message1);
+
+ System.out.println("Sent message: " + message1.getText());
+
+
+
+
+
+ int count = getMessageCount(connection);
+
+ System.out.println("Queue message count is " + count);
+
+
+
+
+
+ connection.start();
+
+ Thread.sleep(1000);
+
+
+
+
+
+ count = getMessageCount(connection);
+
+ System.out.println("Queue message count is now " + count);
+
+
+
+
+
+ TextMessage messageReceived = (TextMessage)messageConsumer.receive(5000);
+
+ System.out.println("Received message: " + messageReceived.getText());
+
+
+
+
+
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+
+
+ More information
+ +-
+
JMS Message Producer Rate Limiting
+ +With HornetQ you can specify a maximum send rate at which a JMS MessageProducer will send messages.
+ This can be specified when creating or deploying the connection factory. See hornetq-jms.xml
If this value is specified then HornetQ will ensure that messages are never produced at a rate higher than + specified. This is a form of producer throttling.
+Example step-by-step
+In this example we specify a producer-max-rate of 50 messages per second in the hornetq-jms.xml
+ file when deploying the connection factory:
+
+ <connection-factory name="ConnectionFactory">
+ <connector-ref connector-name="netty-connector"/>
+ <entries>
+ <entry name="ConnectionFactory"/>
+ </entries>
+
+ <!-- We limit producers created on this connection factory to produce messages at a maximum rate
+ of 50 messages per sec -->
+ <producer-max-rate>50</producer-max-rate>
+
+ </connection-factory>
+
+
+ We then simply send as many messages as we can in 10 seconds and note how many messages are actually sent.
+We note that the number of messages sent per second never exceeds the specified value of 50 messages per second.
To run the example, simply type mvn verify from this directory
-
+
+ initialContext = getContext(0);
+
+
+
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer producer = session.createProducer(queue);
+
+
+
+
+ final long duration = 10000;
+
+ int i = 0;
+
+ long start = System.currentTimeMillis();
+
+ while (System.currentTimeMillis() - start <= duration)
+ {
+ TextMessage message = session.createTextMessage("This is text message: " + i++);
+
+ producer.send(message);
+ }
+
+ long end = System.currentTimeMillis();
+
+ double rate = 1000 * (double)i / (end - start);
+
+ System.out.println("We sent " + i + " messages in " + (end - start) + " milliseconds");
+
+ System.out.println("Actual send rate was " + rate + " messages per second");
+
+
+
+
+
+ [java] Will now send as many messages as we can in 10 seconds...
+ [java] We sent 500 messages in 10072 milliseconds
+ [java] Actual send rate was 49.64257347100874 messages per second
+
+
+
+
+
+
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+ connection.start();
+
+ System.out.println("Now consuming the messages...");
+
+ i = 0;
+ while (true)
+ {
+ TextMessage messageReceived = (TextMessage)messageConsumer.receive(5000);
+
+ if (messageReceived == null)
+ {
+ break;
+ }
+
+ i++;
+ }
+
+ System.out.println("Received " + i + " messages");
+
+
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ Proton qpid java example
+ +HornetQ can be configured to accept requests from any AMQP client that supports the 1.0 version of the protocol. + This example shows a simply qpid java 1.0 client example
+To run the example simply run the command
To configure HornetQ to accept AMQP client connections you need to add an Acceptor like so:
+
+
+ <acceptor name="proton-acceptor">
+ <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class>
+ <param key="protocol" value="AMQP"/>
+ <param key="port" value="5672"/>
+ </acceptor>
+
+
+Example step-by-step
+-
+
+ connection= new Connection("localhost", 5672, null, null);
+
+
+
+ Session session = connection.createSession();
+
+
+
+ Sender sender = session.createSender("testQueue");
+
+
+
+ sender.send(new Message("I am an amqp message"));
+
+
+
+ Receiver rec = session.createMovingReceiver("testQueue");
+
+
+
+ rec.setCredit(UnsignedInteger.valueOf(1), false);
+
+
+
+ Message m = rec.receive(5000);
+ System.out.println("message = " + m.getPayload());
+
+
+
+ rec.acknowledge(m);
+
+
+
+ connection.close();
+
+Proton Ruby Example
+ +HornetQ can be configured to accept requests from any AMQP client that supports the 1.0 version of the protocol. + This example shows a simply proton ruby client that sends and receives messages
+To run the example you will need the following packages installed, alsa-lib.i686 libXv.i686 libXScrnSaver.i686 qt.i686 qt-x11.i686 qtwebkit-2.2.2-2.fc18.i686, gcc, ruby
+On fedora you can install these via the
you will also need the qpid-proton libraries installed, again
lastly you wull have to create the gems
To configure HornetQ to accept AMQP client connections you need to add an Acceptor like so:
+
+
+ <acceptor name="proton-acceptor">
+ <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class>
+ <param key="protocol" value="AMQP"/>
+ <param key="port" value="5672"/>
+ </acceptor>
+
+
+ Example step-by-step
+Firstly start the server by running the command
Then in a separate window you can run the send ruby script by running the command
You can then receive the message via the receive ruby script by running
Message Redistribution Example
+ +This example demonstrates message redistribution between queues with the same name deployed in different + nodes of a cluster.
+As demontrated in the clustered queue example, if queues with the same name are deployed on different nodes of + a cluster, HornetQ can be configured to load balance messages between the nodes on the server side.
+However, if the consumer(s) on a particular node are closed, then messages in the queue at that node can + appear to be stranded, since they have no local consumers.
+If this is undesirable, HornetQ can be configured to redistribute messages from the node + with no consumers, to nodes where there are consumers. If the consumers have JMS selectors set on them, then they + will only be redistributed to nodes with consumers whose selectors match.
+By default, message redistribution is disabled, but can be enabled by specifying some AddressSettings configuration
+ in either hornetq-queues.xml or hornetq-configuration.xml
Setting redistribution-delay to 0 will cause redistribution to occur immediately
+ once there are no more matching consumers on a particular queue instance. Setting it to a positive value > 0 specifies
+ a delay in milliseconds before attempting to redistribute. The delay is useful in the case that another consumer is
+ likely to be created on the queue, to avoid unnecessary redistribution.
Here's the relevant snippet from the hornetq-queues.xml configuration, which tells the server
+ to use a redistribution delay of 0 on any jms queues, i.e. any queues whose name starts with
+ jms.
+
+ <address-setting match="jms.#">
+ <redistribution-delay>0</redistribution-delay>
+ </address-setting>
+
+
+ For more information on HornetQ load balancing, and clustering in general, please see the clustering + section of the user manual.
+Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+
+ ic0 = getContext(0);
+
+
+
+
+ Queue queue = (Queue)ic0.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf0 = (ConnectionFactory)ic0.lookup("/ConnectionFactory");
+
+
+
+ ic1 = getContext(1);
+
+
+
+ ConnectionFactory cf1 = (ConnectionFactory)ic1.lookup("/ConnectionFactory");
+
+
+
+
+
+ connection0 = cf0.createConnection();
+
+
+
+
+
+ connection1 = cf1.createConnection();
+
+
+
+
+
+ Session session0 = connection0.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+
+ Session session1 = connection1.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+
+ connection0.start();
+
+ connection1.start();
+
+
+
+
+
+ MessageConsumer consumer0 = session0.createConsumer(queue);
+
+ MessageConsumer consumer1 = session1.createConsumer(queue);
+
+
+
+
+
+ MessageProducer producer = session0.createProducer(queue);
+
+
+
+
+ final int numMessages = 10;
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session0.createTextMessage("This is text message " + i);
+
+ producer.send(message);
+
+ System.out.println("Sent message: " + message.getText());
+ }
+
+
+
+
+
+ for (int i = 0; i < numMessages; i += 2)
+ {
+ TextMessage message0 = (TextMessage)consumer0.receive(5000);
+
+ System.out.println("Got message: " + message0.getText() + " from node 0");
+
+ TextMessage message1 = (TextMessage)consumer1.receive(5000);
+
+ System.out.println("Got message: " + message1.getText() + " from node 1");
+ }
+
+
+
+
+
+ message0.acknowledge();
+
+
+
+
+ session1.close();
+
+
+
+
+ for (int i = 0; i < numMessages; i += 2)
+ {
+ message0 = (TextMessage)consumer0.receive(5000);
+
+ System.out.println("Got message: " + message0.getText() + " from node 0");
+ }
+
+
+
+
+ message0.acknowledge();
+
+
+
+
+
+ finally
+ {
+ if (connection0 != null)
+ {
+ connection0.close();
+ }
+
+ if (connection1 != null)
+ {
+ connection1.close();
+ }
+
+ if (ic0 != null)
+ {
+ ic0.close();
+ }
+
+ if (ic1 != null)
+ {
+ ic1.close();
+ }
+ }
+
+
+
+ JMS QueueRequestor Example
+ +This example shows you how to use a QueueRequestor with HornetQ.
+JMS is mainly used to send messages asynchronously so that the producer of a message is not waiting for the result of the message consumption.
+ However, there are cases where it is necessary to have a synchronous behavior: the code sending a message requires a reply for this message
+ before continuing its execution.
+ A QueueRequestor facilitates this use case by providing a simple request/reply abstraction on top of JMS.
The example consists in two classes:
+-
+
Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+
+
+
+ QueueConnectionFactory cf = (QueueConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+
+ TextReverserService reverserService = new TextReverserService(cf, queue);
+
+
+
+ connection = cf.createQueueConnection();
+
+
+
+ connection.start();
+
+
+
+ QueueSession session = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ QueueRequestor queueRequestor = new QueueRequestor(session, queue);
+
+
+
+ TextMessage request = session.createTextMessage("Hello, World!");
+
+
+
+ TextMessage reply = (TextMessage)queueRequestor.request(request);
+
+
+
+ System.out.println("Send request: " + request.getText());
+ System.out.println("Received reply:" + reply.getText());
+
+
+
+ queueRequestor.close()
+
+
+
+ reverserService.close()
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ JMS Queue Selector Example
+ +This example shows you how to selectively consume messages using message selectors with queue consumers.
+ +Message selectors are strings with special syntax that can be used in creating consumers. Message consumers + created with a message selector will only receive messages that match its selector. On message delivery, the JBoss Message + Server evaluates the corresponding message headers of the messages against each selector, if any, and then delivers + the 'matched' messages to its consumer. Please consult the JMS 1.1 specification for full details.
+ +In this example, three message consumers are created on a queue. The first consumer is created with selector
+ 'color=red', it only receives messages that
+ have a 'color' string property of 'red' value; the second is created with selector 'color=green', it
+ only receives messages who have a 'color' string property of
+ 'green' value; and the third without a selector, which means it receives all messages. To illustrate, three messages
+ with different 'color' property values are created and sent.
Selectors can be used with both queue consumers and topic consumers. The difference is that with queue consumers, + a message is only delivered to one consumer on the queue, while topic consumers the message will be delivered to every + matching consumers. In this example, if the third consumer (anyConsumer) were the first consumer created, it will + consume the first message delivered, therefore there is no chance for the next consumer to get the message, even if it + matches the selector.
+ + +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ connection.start();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(queue);
+
+
+
+
+ String redSelector = "color='red'";
+ String greenSelector = "color='green'";
+
+
+
+
+
+ MessageConsumer redConsumer = session.createConsumer(queue, redSelector);
+ redConsumer.setMessageListener(new SimpleMessageListener("red"));
+
+
+
+
+
+ MessageConsumer greenConsumer = session.createConsumer(queue, greenSelector);
+ greenConsumer.setMessageListener(new SimpleMessageListener("green"));
+
+
+
+
+
+ MessageConsumer anyConsumer = session.createConsumer(queue);
+ anyConsumer.setMessageListener(new SimpleMessageListener("any"));
+
+
+
+
+
+ TextMessage redMessage = session.createTextMessage("Red");
+ redMessage.setStringProperty("color", "red");
+ TextMessage greenMessage = session.createTextMessage("Green");
+ greenMessage.setStringProperty("color", "green");
+ TextMessage blueMessage = session.createTextMessage("Blue");
+ blueMessage.setStringProperty("color", "blue");
+
+
+
+
+
+ producer.send(redMessage);
+ System.out.println("Message sent: " + redMessage.getText());
+ producer.send(greenMessage);
+ System.out.println("Message sent: " + greenMessage.getText());
+ producer.send(blueMessage);
+ System.out.println("Message sent: " + blueMessage.getText());
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ JMS Queue Example
+ +This example shows you how to send and receive a message to a JMS Queue using HornetQ.
+Queues are a standard part of JMS, please consult the JMS 1.1 specification for full details.
+A Queue is used to send messages point to point, from a producer to a consumer. The queue guarantees message ordering between these 2 points.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(topic);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+
+ messageProducer.send(message);
+
+
+
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+
+
+ connection.start();
+
+
+
+ TextMessage messageReceived = (TextMessage) messageConsumer.receive(5000);
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ JMS Reattach Example
+ +This example demonstrates how HornetQ connections can be configured to be resilient to + temporary network failures.
+In the case of a network failure being detected, either as a result of a failure to read/write to the connection, + or the failure of a pong to arrive back from the server in good time after a ping is sent, instead of + failing the connection immediately and notifying any user ExceptionListener objects, HornetQ + can be configured to automatically retry the connection, and reattach to the server when it becomes + available again across the network.
+When the client reattaches to the server it will be able to resume using its sessions and connections + where it left off
+This is different to client reconnect as the sessions, consumers etc still exist on the server. With reconnect + The client recreates its sessions and consumers as needed.
+This example starts a single server, connects to it and performs some JMS operations. We then + simulate failure of the network connection by temporarily stopping the network acceptor on the server. + (This is done by sending management messages, but that is not central to the purpose of the example).
+We then wait a few seconds, then restart the acceptor. The client reattaches and the session resumes + as if nothing happened.
+The JMS Connection Factory is configured to reattach automatically by specifying the various reconnect
+ related attributes in the hornetq-jms.xml file.
For more details on how to configure this and for clustering in general + please consult the HornetQ user manual.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ initialContext = getContext(0);
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(topic);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+
+ messageProducer.send(message);
+
+
+
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+
+
+ connection.start();
+
+
+
+ stopAcceptor(initialContext);
+
+
+
+
+ Thread.sleep(10000);
+
+ startAcceptor(initialContext);
+
+
+
+
+
+ TextMessage messageReceived = (TextMessage)messageConsumer.receive(5000);
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ JMS Multiple Failover using Replication Example
+ + Note that failback example is not working in 2.3.0.Alpha but will be fully functional in the next release. + +This example demonstrates three servers coupled as a live-backup-backup group for high availability (HA) using replication, and a client + connection failing over from live to backup when the live server is crashed and then to the second backup once the new live fails.
+ +For more information on HornetQ failover and HA, and clustering in general, please see the clustering + section of the user manual.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
In this example, the live server is server 1, and the backup server is server 0
+The connection will initially be created to server1, server 1 will crash, and the client will carry on + seamlessly on server 0, the backup server.
+ +-
+
+ initialContext = getContext(0); ++ +
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+ ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+ + connection = connectionFactory.createConnection(); ++ +
+ Session session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE); ++ +
+ connection.start(); ++ +
+ MessageProducer producer = session.createProducer(queue); ++ +
+ MessageConsumer consumer = session.createConsumer(queue); ++ +
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session.createTextMessage("This is text message " + i);
+ producer.send(message);
+ System.out.println("Sent message: " + message.getText());
+ }
+
+
+
+ TextMessage message0 = null;
+ for (int i = 0; i < numMessages / 3; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+ message0.acknowledge();
+
+
+ When server #0 crashes, the client automatically detects the failure and automatically + fails over from server #0 to server #1 (in your real program you wouldn't need to sleep). +
+ +
+ try
+ {
+ message0.acknowledge();
+ }
+ catch (JMSException e)
+ {
+ System.err.println("Got exception while acknowledging message: " + e.getMessage());
+ }
+
+
+
+ for (int i = numMessages / 3; i < (numMessages / 3) * 2; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.printf("Got message: %s (redelivered?: %s)\n", message0.getText(), message0.getJMSRedelivered());
+ }
+ message0.acknowledge();
+
+
+ now we Kill server #1 and wait for the server #2 to take over the responsibilities.
+ +
+ try
+ {
+ message0.acknowledge();
+ }
+ catch (JMSException e)
+ {
+ System.err.println("Got exception while acknowledging message: " + e.getMessage());
+ }
+
+
+
+
+ for (int i = (numMessages / 3) * 2; i < numMessages; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.printf("Got message: %s (redelivered?: %s)\n", message0.getText(), message0.getJMSRedelivered());
+ }
+ message0.acknowledge();
+
+
+
+ finally
+ {
+ if (connection != null)
+ {
+ connection.close();
+ }
+
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ }
+
+
+ + * After both servers are started, the live server is killed and the backup becomes active ("fails-over"). + *
+ * Later the live server is restarted and takes back its position by asking the backup to stop ("fail-back").
+ * @author Andy Taylor
+ */
+public class ReplicatedFailbackStaticExample extends HornetQExample
+{
+ public static void main(final String[] args)
+ {
+ new ReplicatedFailbackStaticExample().run(args);
+ }
+
+ @Override
+ public boolean runExample() throws Exception
+ {
+ final int numMessages = 30;
+
+ Connection connection = null;
+
+ InitialContext initialContext = null;
+
+ try
+ {
+ // Step 1. Get an initial context for looking up JNDI from the server #1
+ initialContext = getContext(0);
+
+ // Step 2. Look up the JMS resources from JNDI
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+ ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+ // Step 3. Create a JMS Connection
+ connection = connectionFactory.createConnection();
+
+ // Step 4. Create a *non-transacted* JMS Session with client acknowledgement
+ Session session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE);
+
+ // Step 5. Start the connection to ensure delivery occurs
+ connection.start();
+
+ // Step 6. Create a JMS MessageProducer and a MessageConsumer
+ MessageProducer producer = session.createProducer(queue);
+ MessageConsumer consumer = session.createConsumer(queue);
+
+ // Step 7. Send some messages to server #1, the live server
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session.createTextMessage("This is text message " + i);
+ producer.send(message);
+ System.out.println("Sent message: " + message.getText());
+ }
+
+ // Step 8. Receive and acknowledge a third of the sent messages
+ TextMessage message0 = null;
+ for (int i = 0; i < numMessages / 3; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+ message0.acknowledge();
+
+ // Step 9. Receive the rest third of the sent messages but *do not* acknowledge them yet
+ for (int i = numMessages / 3; i < numMessages; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+
+ // Step 10. Crash server #1, the live server, and wait a little while to make sure
+ // it has really crashed
+ Thread.sleep(2000);
+ killServer(0);
+
+ // Step 11. Acknowledging the 2nd half of the sent messages will fail as failover to the
+ // backup server has occurred
+ try
+ {
+ message0.acknowledge();
+ }
+ catch (JMSException e)
+ {
+ System.out.println("Got (the expected) exception while acknowledging message: " + e.getMessage());
+ }
+
+ // Step 12. Consume again the 2nd third of the messages again. Note that they are not considered as redelivered.
+ for (int i = numMessages / 3; i < (numMessages / 3) * 2; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.printf("Got message: %s (redelivered?: %s)\n", message0.getText(), message0.getJMSRedelivered());
+ }
+ message0.acknowledge();
+
+ reStartServer(0, 10000);
+
+ Thread.sleep(10000);
+
+ // Step 11. Acknowledging the 2nd half of the sent messages will fail as failover to the
+ // backup server has occurred
+ try
+ {
+ message0.acknowledge();
+ }
+ catch (JMSException e)
+ {
+ System.err.println("Got exception while acknowledging message: " + e.getMessage());
+ }
+
+ // Step 12. Consume again the 2nd third of the messages again. Note that they are not considered as redelivered.
+ for (int i = (numMessages / 3) * 2; i < numMessages; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.printf("Got message: %s (redelivered?: %s)\n", message0.getText(), message0.getJMSRedelivered());
+ }
+ message0.acknowledge();
+
+ return true;
+ }
+ finally
+ {
+ // Step 13. Be sure to close our resources!
+
+ if (connection != null)
+ {
+ connection.close();
+ }
+
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ }
+ }
+
+}
diff --git a/examples/jms/replicated-failback-static/src/main/resources/hornetq/server0/hornetq-configuration.xml b/examples/jms/replicated-failback-static/src/main/resources/hornetq/server0/hornetq-configuration.xml
new file mode 100644
index 0000000000..8fa244a3a6
--- /dev/null
+++ b/examples/jms/replicated-failback-static/src/main/resources/hornetq/server0/hornetq-configuration.xml
@@ -0,0 +1,65 @@
+
JMS Multiple Failover using Replication Example
+ + Note that failback example is not working in 2.3.0.Alpha but will be fully functional in the next release. + +This example demonstrates three servers coupled as a live-backup-backup group for high availability (HA) using replication, and a client + connection failing over from live to backup when the live server is crashed and then to the second backup once the new live fails.
+ +For more information on HornetQ failover and HA, and clustering in general, please see the clustering + section of the user manual.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
In this example, the live server is server 1, and the backup server is server 0
+The connection will initially be created to server1, server 1 will crash, and the client will carry on + seamlessly on server 0, the backup server.
+ +-
+
+ initialContext = getContext(0); ++ +
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+ ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+ + connection = connectionFactory.createConnection(); ++ +
+ Session session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE); ++ +
+ connection.start(); ++ +
+ MessageProducer producer = session.createProducer(queue); ++ +
+ MessageConsumer consumer = session.createConsumer(queue); ++ +
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session.createTextMessage("This is text message " + i);
+ producer.send(message);
+ System.out.println("Sent message: " + message.getText());
+ }
+
+
+
+ TextMessage message0 = null;
+ for (int i = 0; i < numMessages / 3; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+ message0.acknowledge();
+
+
+ When server #0 crashes, the client automatically detects the failure and automatically + fails over from server #0 to server #1 (in your real program you wouldn't need to sleep). +
+ +
+ try
+ {
+ message0.acknowledge();
+ }
+ catch (JMSException e)
+ {
+ System.err.println("Got exception while acknowledging message: " + e.getMessage());
+ }
+
+
+
+ for (int i = numMessages / 3; i < (numMessages / 3) * 2; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.printf("Got message: %s (redelivered?: %s)\n", message0.getText(), message0.getJMSRedelivered());
+ }
+ message0.acknowledge();
+
+
+ now we Kill server #1 and wait for the server #2 to take over the responsibilities.
+ +
+ try
+ {
+ message0.acknowledge();
+ }
+ catch (JMSException e)
+ {
+ System.err.println("Got exception while acknowledging message: " + e.getMessage());
+ }
+
+
+
+
+ for (int i = (numMessages / 3) * 2; i < numMessages; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.printf("Got message: %s (redelivered?: %s)\n", message0.getText(), message0.getJMSRedelivered());
+ }
+ message0.acknowledge();
+
+
+
+ finally
+ {
+ if (connection != null)
+ {
+ connection.close();
+ }
+
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ }
+
+
+ + * After both servers are started, the live server is killed and the backup becomes active ("fails-over"). + *
+ * Later the live server is restarted and takes back its position by asking the backup to stop ("fail-back").
+ * @author Andy Taylor
+ */
+public class ReplicatedFailbackExample extends HornetQExample
+{
+ public static void main(final String[] args)
+ {
+ new ReplicatedFailbackExample().run(args);
+ }
+
+ @Override
+ public boolean runExample() throws Exception
+ {
+ final int numMessages = 30;
+
+ Connection connection = null;
+
+ InitialContext initialContext = null;
+
+ try
+ {
+ // Step 1. Get an initial context for looking up JNDI from the server #1
+ initialContext = getContext(0);
+
+ // Step 2. Look up the JMS resources from JNDI
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+ ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+ // Step 3. Create a JMS Connection
+ connection = connectionFactory.createConnection();
+
+ // Step 4. Create a *non-transacted* JMS Session with client acknowledgement
+ Session session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE);
+
+ // Step 5. Start the connection to ensure delivery occurs
+ connection.start();
+
+ // Step 6. Create a JMS MessageProducer and a MessageConsumer
+ MessageProducer producer = session.createProducer(queue);
+ MessageConsumer consumer = session.createConsumer(queue);
+
+ // Step 7. Send some messages to server #1, the live server
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session.createTextMessage("This is text message " + i);
+ producer.send(message);
+ System.out.println("Sent message: " + message.getText());
+ }
+
+ // Step 8. Receive and acknowledge a third of the sent messages
+ TextMessage message0 = null;
+ for (int i = 0; i < numMessages / 3; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+ message0.acknowledge();
+
+ // Step 9. Receive the rest third of the sent messages but *do not* acknowledge them yet
+ for (int i = numMessages / 3; i < numMessages; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+
+ // Step 10. Crash server #1, the live server, and wait a little while to make sure
+ // it has really crashed
+ Thread.sleep(2000);
+ killServer(0);
+
+ // Step 11. Acknowledging the 2nd half of the sent messages will fail as failover to the
+ // backup server has occurred
+ try
+ {
+ message0.acknowledge();
+ }
+ catch (JMSException e)
+ {
+ System.out.println("Got (the expected) exception while acknowledging message: " + e.getMessage());
+ }
+
+ // Step 12. Consume again the 2nd third of the messages again. Note that they are not considered as redelivered.
+ for (int i = numMessages / 3; i < (numMessages / 3) * 2; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.printf("Got message: %s (redelivered?: %s)\n", message0.getText(), message0.getJMSRedelivered());
+ }
+ message0.acknowledge();
+
+ reStartServer(0, 10000);
+
+ Thread.sleep(10000);
+
+ // Step 11. Acknowledging the 2nd half of the sent messages will fail as failover to the
+ // backup server has occurred
+ try
+ {
+ message0.acknowledge();
+ }
+ catch (JMSException e)
+ {
+ System.err.println("Got exception while acknowledging message: " + e.getMessage());
+ }
+
+ // Step 12. Consume again the 2nd third of the messages again. Note that they are not considered as redelivered.
+ for (int i = (numMessages / 3) * 2; i < numMessages; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.printf("Got message: %s (redelivered?: %s)\n", message0.getText(), message0.getJMSRedelivered());
+ }
+ message0.acknowledge();
+
+ return true;
+ }
+ finally
+ {
+ // Step 13. Be sure to close our resources!
+
+ if (connection != null)
+ {
+ connection.close();
+ }
+
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ }
+ }
+
+}
diff --git a/examples/jms/replicated-failback/src/main/resources/hornetq/server0/hornetq-configuration.xml b/examples/jms/replicated-failback/src/main/resources/hornetq/server0/hornetq-configuration.xml
new file mode 100644
index 0000000000..fb7ece0a66
--- /dev/null
+++ b/examples/jms/replicated-failback/src/main/resources/hornetq/server0/hornetq-configuration.xml
@@ -0,0 +1,76 @@
+
JMS Multiple Failover using Replication Example
+ +This example demonstrates three servers coupled as a live-backup-backup group for high availability (HA) using replication, and a client + connection failing over from live to backup when the live server is crashed and then to the second backup once the new live fails.
+ +For more information on HornetQ failover and HA, and clustering in general, please see the clustering + section of the user manual.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
In this example, the live server is server 1, and the backup server is server 0
+The connection will initially be created to server1, server 1 will crash, and the client will carry on + seamlessly on server 0, the backup server.
+ +-
+
+ initialContext = getContext(0); ++ +
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+ ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+ + connection = connectionFactory.createConnection(); ++ +
+ Session session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE); ++ +
+ connection.start(); ++ +
+ MessageProducer producer = session.createProducer(queue); ++ +
+ MessageConsumer consumer = session.createConsumer(queue); ++ +
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session.createTextMessage("This is text message " + i);
+ producer.send(message);
+ System.out.println("Sent message: " + message.getText());
+ }
+
+
+
+ TextMessage message0 = null;
+ for (int i = 0; i < numMessages / 3; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+ message0.acknowledge();
+
+
+ When server #0 crashes, the client automatically detects the failure and automatically + fails over from server #0 to server #1 (in your real program you wouldn't need to sleep). +
+ +
+ try
+ {
+ message0.acknowledge();
+ }
+ catch (JMSException e)
+ {
+ System.err.println("Got exception while acknowledging message: " + e.getMessage());
+ }
+
+
+
+ for (int i = numMessages / 3; i < (numMessages / 3) * 2; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.printf("Got message: %s (redelivered?: %s)\n", message0.getText(), message0.getJMSRedelivered());
+ }
+ message0.acknowledge();
+
+
+ now we Kill server #1 and wait for the server #2 to take over the responsibilities.
+ +
+ try
+ {
+ message0.acknowledge();
+ }
+ catch (JMSException e)
+ {
+ System.err.println("Got exception while acknowledging message: " + e.getMessage());
+ }
+
+
+
+
+ for (int i = (numMessages / 3) * 2; i < numMessages; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.printf("Got message: %s (redelivered?: %s)\n", message0.getText(), message0.getJMSRedelivered());
+ }
+ message0.acknowledge();
+
+
+
+ finally
+ {
+ if (connection != null)
+ {
+ connection.close();
+ }
+
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ }
+
+
+ JMS Failover With Transaction using Replication Example
+ +This example demonstrates two servers coupled as a live-backup pair for high availability (HA) using replication, and a client + connection failing over from live to backup when the live server is crashed.
+Failover behavior differs whether the JMS session is transacter or not.
+When a transacted JMS session is used, once-and-only once delivery is guaranteed.
+-
+
HornetQ also provides an example for non-transaction failover.
+For more information on HornetQ failover and HA, and clustering in general, please see the clustering + section of the user manual.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
In this example, the live server is server 1, and the backup server is server 0
+The connection will initially be created to server1, server 1 will crash, and the client will carry on + seamlessly on server 0, the backup server.
+ +-
+
+ initialContext = getContext(1); ++ +
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+ ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+ + connection = connectionFactory.createConnection(); ++ +
+ Session session = connection.createSession(true, 0); ++ +
+ connection.start(); ++ +
+ MessageProducer producer = session.createProducer(queue); ++ +
+ MessageConsumer consumer = session.createConsumer(queue); ++ +
+ sendMessages(session, producer, numMessages, true); ++ +
When server #1 crashes, the client automatically detects the failure and automatically + fails over from server #1 to server #0 (in your real program you wouldn't need to sleep). +
+ +
+ try
+ {
+ session.commit();
+ } catch (TransactionRolledBackException e)
+ {
+ System.err.println("transaction has been rolled back: " + e.getMessage());
+ }
+
+
+ + sendMessages(session, producer, numMessages, false); ++ +
+ session.commit(); ++ + +
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+ session.commit();
+ System.out.println("Other message on the server? " + consumer.receive(5000));
+
+
+
+ finally
+ {
+ if (connection != null)
+ {
+ connection.close();
+ }
+
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ }
+
+
+ JMS Request-Reply Example
+ +This example shows you how to handle a request message and receive a reply. To get a reply message, the requesting client creates a temporary queue. Then it sends out the request message with JMSReplyTo set to the temporary queue. The request message is handled by a SimpleRequestServer, who is listening to the request queue for incoming requests. If a request message has arrived, it extracts the reply queue from the request message by JMSReplyTo header, and sends back a reply message. To let the client know to which request message a reply message is related, the server also set the JMSCorrelationID with the request message's JMSMessageID header to the reply message.
+Of course, in a real world example you would re-use the session, producer, consumer and temporary queue and not create a new one for each message! +Or better still use the correlation id, and just store the requests in a map, then you don't need a temporary queue at all + +
Request/Reply style messaging is supported through standard JMS message headers JMSReplyTo and JMSCorrelationID. This is often used in request-reply style communications between applications. + Whenever a client sends a message that expects a response, it can use this mechanism to implement. please consult the JMS 1.1 specification for full details.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+
++ +SimpleRequestServer server = new SimpleRequestServer();+server.start();+
+ initialContext = getContext();
+
+
+
+ Queue requestQueue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ connection.start();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer producer = session.createProducer(requestQueue);
+
+
+
+ TemporaryQueue replyQueue = session.createTemporaryQueue();
+
+
+
+ MessageConsumer replyConsumer = session.createConsumer(replyQueue);
+
+
+
+ TextMessage requestMsg = session.createTextMessage("A request message");
+
+
+
+ requestMsg.setJMSReplyTo(replyQueue);
+
+
+
+ producer.send(requestMsg);
+
+
+
+ requestMap.put(requestMsg.getJMSMessageID(), requestMsg);
+
+
+
+ TextMessage replyMessageReceived = (TextMessage)replyConsumer.receive();
+
+
+
+ TextMessage matchedMessage = requestMap.get(replyMessageReceived.getJMSCorrelationID());
+
+
+
+ replyConsumer.close();
+
+
+
+ replyQueue.delete();
+
+
+
+ server.shutdown();
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ -
+
+ Destination replyDestination = request.getJMSReplyTo();
+
+
+
+ TextMessage replyMessage = session.createTextMessage("A reply message");
+
+
+
+ replyMessage.setJMSCorrelationID(request.getJMSCorrelationID());
+
+
+
+ replyProducer.send(replyMessage);
+
+ Ajax Chat Demo
++ + +
+ + + +
+ +
Messages:
++ ++ + + diff --git a/examples/jms/rest/javascript-chat/src/test/java/org/jboss/resteasy/messaging/test/AutoAckTopicTest.java b/examples/jms/rest/javascript-chat/src/test/java/org/jboss/resteasy/messaging/test/AutoAckTopicTest.java new file mode 100644 index 0000000000..278ae4e341 --- /dev/null +++ b/examples/jms/rest/javascript-chat/src/test/java/org/jboss/resteasy/messaging/test/AutoAckTopicTest.java @@ -0,0 +1,91 @@ +/* + * Copyright 2005-2014 Red Hat, Inc. + * Red Hat licenses this file to you under the Apache License, version + * 2.0 (the "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * http://www.apache.org/licenses/LICENSE-2.0 + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + * implied. See the License for the specific language governing + * permissions and limitations under the License. + */ +package org.jboss.resteasy.messaging.test; + +import org.jboss.resteasy.client.ClientRequest; +import org.jboss.resteasy.client.ClientResponse; +import org.jboss.resteasy.spi.Link; +import org.hornetq.rest.util.LinkStrategy; +import org.junit.Assert; +import org.junit.Test; + + +/** + * @author Bill Burke + * @version $Revision: 1 $ + */ +public class AutoAckTopicTest +{ + public static Link getLinkByTitle(LinkStrategy strategy, ClientResponse response, String title) + { + return response.getLinkHeader().getLinkByTitle(title); + } + + @Test + public void testSuccessFirst() throws Exception + { + ClientRequest request = new ClientRequest("http://localhost:9095/topics/jms.topic.chat"); + + ClientResponse response = request.head(); + Assert.assertEquals("*****", 200, response.getStatus()); + Link sender = getLinkByTitle(null, response, "create"); + Link subscriptions = getLinkByTitle(null, response, "subscriptions"); + + /* + ClientResponse res = subscriptions.request().post(); + Assert.assertEquals(201, res.getStatus()); + Link sub1 = res.getLocation(); + Assert.assertNotNull(sub1); + Link consumeNext1 = MessageTestBase.getLinkByTitle(manager.getTopicManager().getLinkStrategy(), res, "consume-next"); + Assert.assertNotNull(consumeNext1); + System.out.println("consumeNext1: " + consumeNext1); + + + res = subscriptions.request().post(); + Assert.assertEquals(201, res.getStatus()); + Link sub2 = res.getLocation(); + Assert.assertNotNull(sub2); + Link consumeNext2 = MessageTestBase.getLinkByTitle(manager.getTopicManager().getLinkStrategy(), res, "consume-next"); + Assert.assertNotNull(consumeNext1); + + + res = sender.request().body("text/plain", Integer.toString(1)).post(); + Assert.assertEquals(201, res.getStatus()); + res = sender.request().body("text/plain", Integer.toString(2)).post(); + Assert.assertEquals(201, res.getStatus()); + + res = consumeNext1.request().post(String.class); + Assert.assertEquals(200, res.getStatus()); + Assert.assertEquals("1", res.getEntity(String.class)); + consumeNext1 = MessageTestBase.getLinkByTitle(manager.getTopicManager().getLinkStrategy(), res, "consume-next"); + + res = consumeNext1.request().post(String.class); + Assert.assertEquals(200, res.getStatus()); + Assert.assertEquals("2", res.getEntity(String.class)); + consumeNext1 = MessageTestBase.getLinkByTitle(manager.getTopicManager().getLinkStrategy(), res, "consume-next"); + + res = consumeNext2.request().post(String.class); + Assert.assertEquals(200, res.getStatus()); + Assert.assertEquals("1", res.getEntity(String.class)); + consumeNext2 = MessageTestBase.getLinkByTitle(manager.getTopicManager().getLinkStrategy(), res, "consume-next"); + + res = consumeNext2.request().post(String.class); + Assert.assertEquals(200, res.getStatus()); + Assert.assertEquals("2", res.getEntity(String.class)); + consumeNext2 = MessageTestBase.getLinkByTitle(manager.getTopicManager().getLinkStrategy(), res, "consume-next"); + Assert.assertEquals(204, sub1.request().delete().getStatus()); + Assert.assertEquals(204, sub2.request().delete().getStatus()); + */ + } + +} \ No newline at end of file diff --git a/examples/jms/rest/jms-to-rest/README.txt b/examples/jms/rest/jms-to-rest/README.txt new file mode 100644 index 0000000000..eafb074170 --- /dev/null +++ b/examples/jms/rest/jms-to-rest/README.txt @@ -0,0 +1,49 @@ +System Requirements: +You will need JDK 1.6 and Maven to run this example. This example has been tested with Maven 2.2.1. It may or may not work +with earlier or later versions of Maven. + + +This is an example of mixing JMS producers and consumers with REST producers and consumers. The REST clients have been +written in both Java using RESTEasy's client library and within the Python language. You will need Python 2.6.1 or higher +to be able to run the Python clients. + +To run the example you will need 5 shell-script windows (or you'll need to run 4 processes in background) + +Step 1: +$ mvn jetty:run + +This will bring up HornetQ and the HornetQ REST Interface. + +Step 2: +$ mvn exec:java -Dexec.mainClass="RestReceive" + +This will bring up a Java REST client that is continuously pulling the server through a consume-next (see doco for details). + +Step 3: +$ mvn exec:java -Dexec.mainClass="JmsReceive" + +This will bring up a Java JMS consumer that is using the MessageListener interface to consume messages. It will +extract a Order instance from the JMS Message it receives. + +Step 4: + +$ python receiveOrder.py + +This runs a very simple Python program to consume messages + +Step 5: +Use one of these three commands to post messages to the system. One of the receive clients will consume the message. + +$ mvn exec:java -Dexec.mainClass="JmsSend" + +A JMS client will create an Order object and send it to the queue. You'll see one of the 4 clients receive the message. +Notice that the REST clients automatically cause the Order object to be transformed on the server and passed as XML +to the REST client. + +$ mvn exec:java -Dexec.mainClass="RestSend" + +THis is a REST client that uses the Acknowledgement protocol to receive a message from the queue. + +$ python postOrder.py + +This is a Python client that posts one message to the queue RESTfully (of course ;) ) diff --git a/examples/jms/rest/jms-to-rest/pom.xml b/examples/jms/rest/jms-to-rest/pom.xml new file mode 100644 index 0000000000..7400b041db --- /dev/null +++ b/examples/jms/rest/jms-to-rest/pom.xml @@ -0,0 +1,141 @@ +
JMS Colocated Failover Shared Store Example
+ +This example demonstrates how you can configure a live server to scale down messages to another live server on shutdown. +
This example starts 2 live servers each one with a connector configured for the other live server.
+The second live server is killed and its messages are scaled down to the first server on shutdown.
+The following shows how to configure the live servers to scale down to one another.
+
+ <ha-policy template="NONE">
+ <scale-down>true</scale-down>
+ <scale-down-connectors>
+ <connector-ref>server1-connector</connector-ref>
+ </scale-down-connectors>
+
+
+
+ notice that we have used a template to set some sensible defaults but overridden the backup strategy so back ups + are full servers
+Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+
+ initialContext1 = getContext(1);
+ initialContext = getContext(0);
+
+
+
+
+
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+ ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+ ConnectionFactory connectionFactory1 = (ConnectionFactory)initialContext1.lookup("/ConnectionFactory");
+
+
+
+
+
+ connection = connectionFactory.createConnection();
+ connection1 = connectionFactory1.createConnection();
+
+
+
+
+
+ Session session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE);
+ Session session1 = connection1.createSession(false, Session.CLIENT_ACKNOWLEDGE);
+
+
+
+
+
+ MessageProducer producer = session.createProducer(queue);
+ MessageProducer producer1 = session1.createProducer(queue);
+
+
+
+
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session.createTextMessage("This is text message " + i);
+ producer.send(message);
+ System.out.println("Sent message: " + message.getText());
+ message = session1.createTextMessage("This is another text message " + i);
+ producer1.send(message);
+ System.out.println("Sent message: " + message.getText());
+ }
+
+
+
+
+
+ killServer(0);
+
+
+
+
+
+ connection.start();
+
+
+
+
+
+ MessageConsumer consumer = session.createConsumer(queue);
+
+
+
+
+
+ TextMessage message0 = null;
+ for (int i = 0; i < numMessages; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+ message0.acknowledge();
+
+
+
+
+
+ finally
+ {
+ if (connection != null)
+ {
+ connection.close();
+ }
+
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection1 != null)
+ {
+ connection1.close();
+ }
+
+ if (initialContext1 != null)
+ {
+ initialContext1.close();
+ }
+ }
+
+
+
+ JMS Scheduled Message Example
+ +This example shows you how to send a scheduled message to a JMS Queue using HornetQ.
+A Scheduled Message is a message that will be delivered at a time specified by the sender. To do this, + simply set a HDR_SCHEDULED_DELIVERY_TIME header property. The value of the property should be the time of + delivery in milliseconds.
+ +In this example, a message is created with the scheduled delivery time set to 5 seconds after the current time.
+ + +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer producer = session.createProducer(queue);
+
+
+
+ TextMessage message = session.createTextMessage("This is a scheduled message message which will be delivered in 5 sec.");
+
+
+
+
+ long time = System.currentTimeMillis();
+ time += 5000;
+ message.setLongProperty(MessageImpl.HDR_SCHEDULED_DELIVERY_TIME.toString(), time);
+
+
+
+
+ messageProducer.send(message);
+
+
+
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+
+
+ connection.start();
+
+
+
+ TextMessage messageReceived = (TextMessage) messageConsumer.receive();
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+ More information
+ +-
+
JMS Security Example
+ +This example shows how to configure and use security using HornetQ.
+ +With security properly configured, HornetQ can restrict client access to its resources, including + connection creation, message sending/receiving, etc. This is done by configuring users and roles as well as permissions in + the configuration files.
+ +HornetQ supports wild-card security configuration. This feature makes security configuration very + flexible and enables fine-grained control over permissions in an efficient way.
+ +For a full description of how to configure security with HornetQ, please consult the user + manual.
+ +This example demonstrates how to configure users/roles, how to configure topics with proper permissions using wild-card + expressions, and how they take effects in a simple program.
+ +First we need to configure users with roles. Users and Roles are configured in hornetq-users.xml. This example has four users
+ configured as below
+
+ <user name="bill" password="hornetq">
+ <role name="user"/>
+ </user>
+
+ <user name="andrew" password="hornetq1">
+ <role name="europe-user"/>
+ <role name="user"/>
+ </user>
+
+ <user name="frank" password="hornetq2">
+ <role name="us-user"/>
+ <role name="news-user"/>
+ <role name="user"/>
+ </user>
+
+ <user name="sam" password="hornetq3">
+ <role name="news-user"/>
+ <role name="user"/>
+ </user>
+
+
+
+ + Each user has three properties available: user name, password, and roles it belongs to. It should be noted that + a user can belong to more than one role. In the above configuration, all users belong to role 'user'. User 'andrew' also + belongs to role 'europe-user', user 'frank' also belongs to 'us-user' and 'news-user' and user 'sam' also belongs to 'news-user'. +
+
+ User name and password consists of a valid account that can be used to establish connections to a HornetQ server, while
+ roles are used in controlling the access privileges against HornetQ topics and queues. You can achieve this control by
+ configuring proper permissions in hornetq-configuration.xml, like the following
+
+ <security-settings>
+ <!-- any user can have full control of generic topics -->
+ <security-setting match="jms.topic.#">
+ <permission type="createDurableQueue" roles="user"/>
+ <permission type="deleteDurableQueue" roles="user"/>
+ <permission type="createNonDurableQueue" roles="user"/>
+ <permission type="deleteNonDurableQueue" roles="user"/>
+ <permission type="send" roles="user"/>
+ <permission type="consume" roles="user"/>
+ </security-setting>
+
+ <security-setting match="jms.topic.news.europe.#">
+ <permission type="createDurableQueue" roles="user"/>
+ <permission type="deleteDurableQueue" roles="user"/>
+ <permission type="createNonDurableQueue" roles="user"/>
+ <permission type="deleteNonDurableQueue" roles="user"/>
+ <permission type="send" roles="europe-user"/>
+ <permission type="consume" roles="news-user"/>
+ </security-setting>
+
+ <security-setting match="jms.topic.news.us.#">
+ <permission type="createDurableQueue" roles="user"/>
+ <permission type="deleteDurableQueue" roles="user"/>
+ <permission type="createNonDurableQueue" roles="user"/>
+ <permission type="deleteNonDurableQueue" roles="user"/>
+ <permission type="send" roles="us-user"/>
+ <permission type="consume" roles="news-user"/>
+ </security-setting>
+ </security-settings>
+ Permissions can be defined on any group of queues, by using a wildcard. You can easily specify + wildcards to apply certain permissions to a set of matching queues and topics. In the above configuration + we have created four sets of permissions, each set matches against a special group of targets, indicated by wild-card match attributes.
+ +You can provide a very broad permission control as a default and then add more strict control + over specific addresses. By the above we define the following access rules:
+ +To illustrate the effect of permissions, three topics are deployed. Topic 'genericTopic' matches 'jms.topic.#' wild-card, topic 'news.europe.europeTopic' matches + jms.topic.news.europe.#' wild-cards, and topic 'news.us.usTopic' matches 'jms.topic.news.us.#'.
+ +With HornetQ, the security manager is also configurable. You can use JAASSecurityManager or JBossASSecurityManager based on you need. Please
+ check out the hornetq-beans.xml for how to do. In this example we just use the basic HornetQSecurityManagerImpl which reads users/roles/passwords from the xml
+ file hornetq-users.xml.
+
+
+
Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+
+ InitialContext initialContext = getContext(0);
+
+
+
+
+
+ Topic genericTopic = (Topic) initialContext.lookup("/topic/genericTopic");
+ Topic europeTopic = (Topic) initialContext.lookup("/topic/europeTopic");
+ Topic usTopic = (Topic) initialContext.lookup("/topic/usTopic");
+
+
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+
+
+ try
+ {
+ cf.createConnection();
+ result = false;
+ }
+ catch (JMSSecurityException e)
+ {
+ System.out.println("Default user cannot get a connection. Details: " + e.getMessage());
+ }
+
+
+
+
+
+ billConnection = null;
+ try
+ {
+ billConnection = createConnection("bill", "hornetq1", cf);
+ result = false;
+ }
+ catch (JMSException e)
+ {
+ System.out.println("User bill failed to connect. Details: " + e.getMessage());
+ }
+
+
+
+
+
+ billConnection = createConnection("bill", "hornetq", cf);
+ billConnection.start();
+
+
+
+
+
+ andrewConnection = createConnection("andrew", "hornetq1", cf);
+ andrewConnection.start();
+
+
+
+
+
+ frankConnection = createConnection("frank", "hornetq2", cf);
+ frankConnection.start();
+
+
+
+
+
+ samConnection = createConnection("sam", "hornetq3", cf);
+ samConnection.start();
+
+
+
+
+
+ checkUserSendAndReceive(genericTopic, billConnection, "bill");
+ checkUserSendAndReceive(genericTopic, andrewConnection, "andrew");
+ checkUserSendAndReceive(genericTopic, frankConnection, "frank");
+ checkUserSendAndReceive(genericTopic, samConnection, "sam");
+
+
+
+
+
+ checkUserNoSendNoReceive(europeTopic, billConnection, "bill", andrewConnection, frankConnection);
+
+
+
+
+
+ checkUserSendNoReceive(europeTopic, andrewConnection, "andrew", frankConnection);
+
+
+
+
+
+ checkUserReceiveNoSend(europeTopic, frankConnection, "frank", andrewConnection);
+
+
+
+
+
+ checkUserReceiveNoSend(europeTopic, samConnection, "sam", andrewConnection);
+
+
+
+
+
+ checkUserNoSendNoReceive(usTopic, billConnection, "bill");
+
+
+
+
+
+ checkUserNoSendNoReceive(usTopic, andrewConnection, "andrew");
+
+
+
+
+
+ checkUserSendAndReceive(usTopic, frankConnection, "frank");
+
+
+
+
+
+ checkUserReceiveNoSend(usTopic, samConnection, "sam", frankConnection);
+
+
+
+
+
+ finally
+ {
+ if (billConnection != null)
+ {
+ billConnection.close();
+ }
+ if (andrewConnection != null)
+ {
+ andrewConnection.close();
+ }
+ if (frankConnection != null)
+ {
+ frankConnection.close();
+ }
+ if (samConnection != null)
+ {
+ samConnection.close();
+ }
+
+ // Also the initialContext
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ }
+
+
+ Asynchronous Send Acknowledgements Example
+ +Asynchronous Send Acknowledgements are an advanced feature of HornetQ which allow you to + receive acknowledgements that messages were successfully received at the server in a separate thread to the sending thread
+In this example we create a normal JMS session, then set a SendAcknowledgementHandler on the JMS + session's underlying core session. We send many messages to the server without blocking and asynchronously + receive send acknowledgements via the SendAcknowledgementHandler. + +
For more information on Asynchronous Send Acknowledgements please see the user manual
+Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+
+ class MySendAcknowledgementsHandler implements SendAcknowledgementHandler
+ {
+ int count = 0;
+
+ public void sendAcknowledged(final Message message)
+ {
+ System.out.println("Received send acknowledgement for message " + count++);
+ }
+ }
+
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+ ClientSession coreSession = ((HornetQSession)session).getCoreSession();
+
+ coreSession.setSendAcknowledgementHandler(new MySendAcknowledgementsHandler());
+
+
+
+
+
+
+ MessageProducer producer = session.createProducer(queue);
+
+ producer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
+
+
+
+
+
+ final int numMessages = 5000;
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ javax.jms.Message jmsMessage = session.createMessage();
+
+ producer.send(jmsMessage);
+
+ System.out.println("Sent message " + i);
+ }
+
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ HornetQ Spring Example
+ +This examples shows how to setup and run an embedded JMS server within a Spring ApplicationContext using HornetQ along with HornetQ configuration files.
+ +Example step-by-step
+YOU MUST DOWNLOAD THE SPRING LIBRARIES TO RUN THIS EXAMPLE!!! You must also modify the build.xml file to include the spring jars. You'll see the placeholder that is already there.
+To run the example, simply type mvn verify from this directory
JMS SSL Example
+ +This example shows you how to configure SSL with HornetQ to send and receive message.
+ +Using SSL can make your messaging applications interact with HornetQ securely. An application can + be secured transparently without extra coding effort. To secure your messaging application with SSL, you need to configure connector and acceptor as follows:
+ ++
+
+ <!-- Connector -->
+
+ <connector name="netty-ssl-connector">
+ <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>
+ <param key="hornetq.remoting.netty.host" value="localhost" type="String"/>
+ <param key="hornetq.remoting.netty.port" value="5500" type="Integer"/>
+ <param key="hornetq.remoting.netty.ssl-enabled" value="true" type="Boolean"/>
+ <param key="hornetq.remoting.netty.trust-store-path" value="server0/hornetq.example.truststore" type="String"/>
+ <param key="hornetq.remoting.netty.trust-store-password" value="hornetqexample" type="String"/>
+ </connector>
+
+ <!-- Acceptor -->
+
+ <acceptor name="netty-ssl-acceptor">
+ <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class>
+ <param key="hornetq.remoting.netty.host" value="localhost" type="String"/>
+ <param key="hornetq.remoting.netty.port" value="5500" type="Integer"/>
+ <param key="hornetq.remoting.netty.ssl-enabled" value="true" type="Boolean"/>
+ <param key="hornetq.remoting.netty.key-store-path" value="hornetq.example.keystore" type="String"/>
+ <param key="hornetq.remoting.netty.key-store-password" value="hornetqexample" type="String"/>
+ </acceptor>
+
+
+
+
+
+ In the configuration, the hornetq.example.keystore is the key store file holding the server's certificate. The hornetq.example.truststore + is the file holding the certificates which the client trusts (i.e. the server's certificate exported from hornetq.example.keystore). They are pre-generated for illustration purpose1.
+ + +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(topic);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+
+ messageProducer.send(message);
+
+
+
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+
+
+ connection.start();
+
+
+
+ TextMessage messageReceived = (TextMessage) messageConsumer.receive(5000);
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ + +
-
+
Static Message Selector Example
+ +This example shows you how to configure a JMS queue with static message selectors (filters).
+ +Static message selectors are HornetQ's extension to message selectors as defined in JMS spec 1.1. + Rather than specifying the selector in the application code, static message selectors are defined in one of + HornetQ's configuration files, hornetq-jms.xml, as an element called 'selector' inside each JMS queue + definition:
+ +
+ <queue name="selectorQueue">
+ <entry name="/queue/selectorQueue">
+ <selector string="color='red'"/>
+ </queue>
+ Once configured the queue selectorQueue only delivers messages that are
+ that match the selector; i.e. only the messages whose color property is equal to 'red' can be received by its consumers.
+ Those that don't match the selector will be dropped by the queue and therefore will never be delivered to any of its consumers.
In the example code, five messages with different color property values are sent to queue selectorQueue.
+ One consumer is created to receive messages from the queue. Of the five sent messages, two have a color property
+ set to 'red', one has it set to 'blue', another to 'green',
+ and one has not the color property at all. The result is that the consumer only gets the two messages
+ with the 'red' color.
Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/selectorQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ connection.start();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer producer = session.createProducer(queue);
+
+
+
+
+ MessageConsumer redConsumer = session.createConsumer(queue);
+ redConsumer.setMessageListener(new SimpleMessageListener("red"));
+
+
+
+
+
+ TextMessage redMessage1 = session.createTextMessage("Red-1");
+ redMessage1.setStringProperty("color", "red");
+ TextMessage redMessage2 = session.createTextMessage("Red-2");
+ redMessage2.setStringProperty("color", "red");
+ TextMessage greenMessage = session.createTextMessage("Green");
+ greenMessage.setStringProperty("color", "green");
+ TextMessage blueMessage = session.createTextMessage("Blue");
+ blueMessage.setStringProperty("color", "blue");
+ TextMessage normalMessage = session.createTextMessage("No color");
+
+
+
+
+
+ producer.send(redMessage1);
+ System.out.println("Message sent: " + redMessage1.getText());
+ producer.send(greenMessage);
+ System.out.println("Message sent: " + greenMessage.getText());
+ producer.send(blueMessage);
+ System.out.println("Message sent: " + blueMessage.getText());
+ producer.send(redMessage2);
+ System.out.println("Message sent: " + redMessage2.getText());
+ producer.send(normalMessage);
+ System.out.println("Message sent: " + normalMessage.getText());
+
+
+
+
+
+ Thread.sleep(5000);
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ Static Message Selector Example
+ +This example shows you how to configure a HornetQ queue with static message selectors (filters) + (to configure a static selector directly on a JMS queue, please see the + static-selector-jms example).
+ +Static message selectors are HornetQ's extension to message selectors as defined in JMS spec 1.1. + Rather than specifying the selector in the application code, static message selectors are defined in one of + HornetQ's configuration files, hornetq-configuration.xml, as an element called 'filter' inside each queue + definition, like
+ +
+ <queues>
+ <queue name="jms.queue.selectorQueue">
+ <address>jms.queue.selectorQueue</address>
+ <filter string="color='red'"/>
+ </queue>
+ </queues>
+ Once configured the queue 'selectorQueue' only delivers messages that are selected against the filter, i.e., + only the messages whose 'color' properties are of 'red' values can be received by its consumers. Those that don't match + the filter will be dropped by the queue and therefore will never be delivered to any of its consumers.
+ +In the example code, five messages with different 'color' property values are sent to queue 'selectorQueue'. One consumer + is created to receive messages from the queue. Of the five sent messages, two are of 'red' color properties, one is 'blue', + one is 'green' and one has not the 'color' propery at all. The result is that the consumer only gets the two 'red' messages.
+ + +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/selectorQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ connection.start();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer producer = session.createProducer(queue);
+
+
+
+
+ MessageConsumer redConsumer = session.createConsumer(queue);
+ redConsumer.setMessageListener(new SimpleMessageListener("red"));
+
+
+
+
+
+ TextMessage redMessage1 = session.createTextMessage("Red-1");
+ redMessage1.setStringProperty("color", "red");
+ TextMessage redMessage2 = session.createTextMessage("Red-2");
+ redMessage2.setStringProperty("color", "red");
+ TextMessage greenMessage = session.createTextMessage("Green");
+ greenMessage.setStringProperty("color", "green");
+ TextMessage blueMessage = session.createTextMessage("Blue");
+ blueMessage.setStringProperty("color", "blue");
+ TextMessage normalMessage = session.createTextMessage("No color");
+
+
+
+
+
+ producer.send(redMessage1);
+ System.out.println("Message sent: " + redMessage1.getText());
+ producer.send(greenMessage);
+ System.out.println("Message sent: " + greenMessage.getText());
+ producer.send(blueMessage);
+ System.out.println("Message sent: " + blueMessage.getText());
+ producer.send(redMessage2);
+ System.out.println("Message sent: " + redMessage2.getText());
+ producer.send(normalMessage);
+ System.out.println("Message sent: " + normalMessage.getText());
+
+
+
+
+
+ Thread.sleep(5000);
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ " + message.body + "
\n" ); + }; + + client.subscribe({ + address: destination, + callback: onsubscribe + }); + }; + + client.connect({ + login: loginName, + password: passcode, + onConnect: onconnect + }); + }); + + $( '#disconnect_form' ).submit( function ( e ) { + + e.preventDefault(); + + var ondisconnect = function () { + $( '#disconnect' ).fadeOut({ + duration: 'fast' + }); + $( '#unsubscribe' ).fadeOut({ + duration: 'fast' + }); + $( '#connect' ).fadeIn(); + $( '#send_form_input' ).attr( 'disabled', 'disabled' ); + $( '#messages' ).empty(); + $( '#debug' ).empty(); + }; + + client.disconnect( ondisconnect ); + }); + + $( '#unsubscribe_form' ).submit( function ( e ) { + + e.preventDefault(); + + client.unsubscribe( [{ address: destination }] ); + + $( '#unsubscribe' ).fadeOut({ + duration: 'fast' + }); + }); + + $( '#send_form' ).submit( function ( e ) { + + e.preventDefault(); + + var text = $( '#send_form_input' ).val(); + if (text) { + client.send( destination, text ); + $('#send_form_input').val( '' ); + } + }); + +}); diff --git a/examples/jms/stomp-websockets/aerogear-chat/aerogear-index.html b/examples/jms/stomp-websockets/aerogear-chat/aerogear-index.html new file mode 100644 index 0000000000..fdcbb56458 --- /dev/null +++ b/examples/jms/stomp-websockets/aerogear-chat/aerogear-index.html @@ -0,0 +1,78 @@ + + + + +
+
+
+
+ Use the form above to connect to the Stomp server and subscribe to the destination.
+Once connected, you can send messages to the destination with the text field at the bottom of this page
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/examples/jms/stomp-websockets/aerogear-chat/aerogear.min.js b/examples/jms/stomp-websockets/aerogear-chat/aerogear.min.js
new file mode 100644
index 0000000000..7c76b3f028
--- /dev/null
+++ b/examples/jms/stomp-websockets/aerogear-chat/aerogear.min.js
@@ -0,0 +1,19 @@
+/*! AeroGear JavaScript Library - v1.4.0-dev - 2014-01-19
+* https://github.com/aerogear/aerogear-js
+* JBoss, Home of Professional Open Source
+* Copyright Red Hat, Inc., and individual contributors
+*
+* Licensed under the Apache License, Version 2.0 (the "License");
+* you may not use this file except in compliance with the License.
+* You may obtain a copy of the License at
+* http://www.apache.org/licenses/LICENSE-2.0
+* Unless required by applicable law or agreed to in writing, software
+* distributed under the License is distributed on an "AS IS" BASIS,
+* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+* See the License for the specific language governing permissions and
+* limitations under the License.
+*/
+(function(e,t){function r(e,t,r){if(4!==t.length)throw new h.exception.invalid("invalid aes block size");var n=e.c[r],a=t[0]^n[0],i=t[r?3:1]^n[1],s=t[2]^n[2];t=t[r?1:3]^n[3];var o,c,u,f,l=n.length/4-2,d=4,p=[0,0,0,0];o=e.n[r],e=o[0];var g=o[1],m=o[2],y=o[3],b=o[4];for(f=0;l>f;f++)o=e[a>>>24]^g[255&i>>16]^m[255&s>>8]^y[255&t]^n[d],c=e[i>>>24]^g[255&s>>16]^m[255&t>>8]^y[255&a]^n[d+1],u=e[s>>>24]^g[255&t>>16]^m[255&a>>8]^y[255&i]^n[d+2],t=e[t>>>24]^g[255&a>>16]^m[255&i>>8]^y[255&s]^n[d+3],d+=4,a=o,i=c,s=u;for(f=0;4>f;f++)p[r?3&-f:f]=b[a>>>24]<<24^b[255&i>>16]<<16^b[255&s>>8]<<8^b[255&t]^n[d++],o=a,a=i,i=s,s=t,t=o;return p}function n(e,t){var r,n,a,i=t.slice(0),s=e.u,o=e.c,c=s[0],u=s[1],h=s[2],f=s[3],l=s[4],d=s[5],p=s[6],g=s[7];for(r=0;64>r;r++)16>r?n=i[r]:(n=i[15&r+1],a=i[15&r+14],n=i[15&r]=0|(n>>>7^n>>>18^n>>>3^n<<25^n<<14)+(a>>>17^a>>>19^a>>>10^a<<15^a<<13)+i[15&r]+i[15&r+9]),n=n+g+(l>>>6^l>>>11^l>>>25^l<<26^l<<21^l<<7)+(p^l&(d^p))+o[r],g=p,p=d,d=l,l=0|f+n,f=h,h=u,u=c,c=0|n+(u&h^f&(u^h))+(u>>>2^u>>>13^u>>>22^u<<30^u<<19^u<<10);s[0]=0|s[0]+c,s[1]=0|s[1]+u,s[2]=0|s[2]+h,s[3]=0|s[3]+f,s[4]=0|s[4]+l,s[5]=0|s[5]+d,s[6]=0|s[6]+p,s[7]=0|s[7]+g}function a(e,t){var r,n=h.random.F[e],a=[];for(r in n)n.hasOwnProperty(r)&&a.push(n[r]);for(r=0;a.length>r;r++)a[r](t)}function i(e){e.c=s(e).concat(s(e)),e.H=new h.cipher.aes(e.c)}function s(e){for(var t=0;4>t&&(e.h[t]=0|e.h[t]+1,!e.h[t]);t++);return e.H.encrypt(e.h)}this.AeroGear={},AeroGear.Core=function(){if(this instanceof AeroGear.Core)throw"Invalid instantiation of base class AeroGear.Core";this.add=function(e){var t,r,n=this[this.collectionName]||{};if(this[this.collectionName]=n,!e)return this;if("string"==typeof e)n[e]=AeroGear[this.lib].adapters[this.type](e,this.config);else if(AeroGear.isArray(e))for(t=0;e.length>t;t++)r=e[t],"string"==typeof r?n[r]=AeroGear[this.lib].adapters[this.type](r,this.config):r.name&&(r.settings=AeroGear.extend(r.settings||{},this.config),r.settings.recordId=r.settings.recordId||r.recordId,n[r.name]=AeroGear[this.lib].adapters[r.type||this.type](r.name,r.settings));else{if(!e.name)return this;e.settings=AeroGear.extend(e.settings||{},this.config),e.settings.recordId=e.settings.recordId||e.recordId,n[e.name]=AeroGear[this.lib].adapters[e.type||this.type](e.name,e.settings)}return this[this.collectionName]=n,this},this.remove=function(e){var t,r,n=this[this.collectionName]||{};if("string"==typeof e)delete n[e];else if(AeroGear.isArray(e))for(t=0;e.length>t;t++)r=e[t],"string"==typeof r?delete n[r]:delete n[r.name];else e&&delete n[e.name];return this[this.collectionName]=n,this}},AeroGear.isArray=function(e){return"[object Array]"==={}.toString.call(e)},AeroGear.extend=function(e,t){var r;for(r in t)e[r]=t[r];return e},function(){function e(e,t,r){var n=t&&r||0,a=0;for(t=t||[],e.toLowerCase().replace(/[0-9a-f]{2}/g,function(e){16>a&&(t[n+a++]=g[e])});16>a;)t[n+a++]=0;return t}function t(e,t){var r=t||0,n=p;return n[e[r++]]+n[e[r++]]+n[e[r++]]+n[e[r++]]+"-"+n[e[r++]]+n[e[r++]]+"-"+n[e[r++]]+n[e[r++]]+"-"+n[e[r++]]+n[e[r++]]+"-"+n[e[r++]]+n[e[r++]]+n[e[r++]]+n[e[r++]]+n[e[r++]]+n[e[r++]]}function r(e,r,n){var a=r&&n||0,i=r||[];e=e||{};var s=null!=e.clockseq?e.clockseq:v,o=null!=e.msecs?e.msecs:(new Date).getTime(),c=null!=e.nsecs?e.nsecs:x+1,u=o-A+(c-x)/1e4;if(0>u&&null==e.clockseq&&(s=16383&s+1),(0>u||o>A)&&null==e.nsecs&&(c=0),c>=1e4)throw Error("uuid.v1(): Can't create more than 10M uuids/sec");A=o,x=c,v=s,o+=122192928e5;var h=(1e4*(268435455&o)+c)%4294967296;i[a++]=255&h>>>24,i[a++]=255&h>>>16,i[a++]=255&h>>>8,i[a++]=255&h;var f=268435455&1e4*(o/4294967296);i[a++]=255&f>>>8,i[a++]=255&f,i[a++]=16|15&f>>>24,i[a++]=255&f>>>16,i[a++]=128|s>>>8,i[a++]=255&s;for(var l=e.node||b,d=0;6>d;d++)i[a+d]=l[d];return r?r:t(i)}function n(e,r,n){var a=r&&n||0;"string"==typeof e&&(r="binary"==e?new d(16):null,e=null),e=e||{};var i=e.random||(e.rng||l)();if(i[6]=64|15&i[6],i[8]=128|63&i[8],r)for(var s=0;16>s;s++)r[a+s]=i[s];return r||t(i)}var a,i,s,o=this,c=Array(16);if(a=function(){for(var e,e,t=c,r=0,r=0;16>r;r++)0==(3&r)&&(e=4294967296*Math.random()),t[r]=255&e>>>((3&r)<<3);return t},o.crypto&&crypto.getRandomValues){var u=new Uint32Array(4);s=function(){crypto.getRandomValues(u);for(var e=0;16>e;e++)c[e]=255&u[e>>2]>>>8*(3&e);return c}}try{var h=require("crypto").randomBytes;i=h&&function(){return h(16)}}catch(f){}for(var l=i||s||a,d="function"==typeof Buffer?Buffer:Array,p=[],g={},m=0;256>m;m++)p[m]=(m+256).toString(16).substr(1),g[p[m]]=m;var y=l(),b=[1|y[0],y[1],y[2],y[3],y[4],y[5]],v=16383&(y[6]<<8|y[7]),A=0,x=0,S=n;if(S.v1=r,S.v4=n,S.parse=e,S.unparse=t,S.BufferClass=d,S.mathRNG=a,S.nodeRNG=i,S.whatwgRNG=s,"undefined"!=typeof module)module.exports=S;else{var G=o.uuid;S.noConflict=function(){return o.uuid=G,S},o.uuid=S}}(),function(){var r=e!==t?e:exports,n="ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/=",a=function(){try{document.createElement("$")}catch(e){return e}}();r.btoa||(r.btoa=function(e){for(var t,r,i=0,s=n,o="";e.charAt(0|i)||(s="=",i%1);o+=s.charAt(63&t>>8-8*(i%1))){if(r=e.charCodeAt(i+=.75),r>255)throw a;t=t<<8|r}return o}),r.atob||(r.atob=function(e){if(e=e.replace(/=+$/,""),1==e.length%4)throw a;for(var t,r,i=0,s=0,o="";r=e.charAt(s++);~r&&(t=i%4?64*t+r:r,i++%4)?o+=String.fromCharCode(255&t>>(6&-2*i)):0)r=n.indexOf(r);return o})}();var o=void 0,c=!0,u=!1,h={cipher:{},hash:{},keyexchange:{},mode:{},misc:{},codec:{},exception:{corrupt:function(e){this.toString=function(){return"CORRUPT: "+this.message},this.message=e},invalid:function(e){this.toString=function(){return"INVALID: "+this.message},this.message=e},bug:function(e){this.toString=function(){return"BUG: "+this.message},this.message=e},notReady:function(e){this.toString=function(){return"NOT READY: "+this.message},this.message=e}}};"undefined"!=typeof module&&module.exports&&(module.exports=h),h.cipher.aes=function(e){this.n[0][0][0]||this.K();var t,r,n,a,i=this.n[0][4],s=this.n[1];t=e.length;var o=1;if(4!==t&&6!==t&&8!==t)throw new h.exception.invalid("invalid aes key size");for(this.c=[n=e.slice(0),a=[]],e=t;4*t+28>e;e++)r=n[e-1],(0===e%t||8===t&&4===e%t)&&(r=i[r>>>24]<<24^i[255&r>>16]<<16^i[255&r>>8]<<8^i[255&r],0===e%t&&(r=r<<8^r>>>24^o<<24,o=o<<1^283*(o>>7))),n[e]=n[e-t]^r;for(t=0;e;t++,e--)r=n[3&t?e:e-4],a[t]=4>=e||4>t?r:s[0][i[r>>>24]]^s[1][i[255&r>>16]]^s[2][i[255&r>>8]]^s[3][i[255&r]]},h.cipher.aes.prototype={encrypt:function(e){return r(this,e,0)},decrypt:function(e){return r(this,e,1)},n:[[[],[],[],[],[]],[[],[],[],[],[]]],K:function(){var e,t,r,n,a,i,s,o=this.n[0],c=this.n[1],u=o[4],h=c[4],f=[],l=[];for(e=0;256>e;e++)l[(f[e]=e<<1^283*(e>>7))^e]=e;for(t=r=0;!u[t];t^=n||1,r=l[r]||1)for(i=r^r<<1^r<<2^r<<3^r<<4,i=99^(i>>8^255&i),u[t]=i,h[i]=t,a=f[e=f[n=f[t]]],s=16843009*a^65537*e^257*n^16843008*t,a=257*f[i]^16843008*i,e=0;4>e;e++)o[e][t]=a=a<<24^a>>>8,c[e][i]=s=s<<24^s>>>8;for(e=0;5>e;e++)o[e]=o[e].slice(0),c[e]=c[e].slice(0)}},h.bitArray={bitSlice:function(e,t,r){return e=h.bitArray.U(e.slice(t/32),32-(31&t)).slice(1),r===o?e:h.bitArray.clamp(e,r-t)},extract:function(e,t,r){var n=Math.floor(31&-t-r);return(-32&(t+r-1^t)?e[0|t/32]<<32-n^e[0|t/32+1]>>>n:e[0|t/32]>>>n)&(1<" + message.body + "
\n"); + }); + }; + client.connect(login, passcode, onconnect); + + return false; + }); + + $('#disconnect_form').submit(function() { + client.disconnect(function() { + $('#disconnect').fadeOut({ duration: 'fast' }); + $('#connect').fadeIn(); + $('#send_form_input').addAttr('disabled'); + }); + return false; + }); + + $('#send_form').submit(function() { + var text = $('#send_form_input').val(); + if (text) { + client.send(destination, {foo: 1}, text); + $('#send_form_input').val(""); + } + return false; + }); + +}); \ No newline at end of file diff --git a/examples/jms/stomp-websockets/chat/index.html b/examples/jms/stomp-websockets/chat/index.html new file mode 100644 index 0000000000..b606aa05bb --- /dev/null +++ b/examples/jms/stomp-websockets/chat/index.html @@ -0,0 +1,54 @@ + + + +
+
+
+
+ Use the form above to connect to the Stomp server and subscribe to the destination.
+Once connected, you can send messages to the destination with the text field at the bottom of this page
+
+
+
+
+
+
+
+
+
+
diff --git a/examples/jms/stomp-websockets/chat/stomp.js b/examples/jms/stomp-websockets/chat/stomp.js
new file mode 100644
index 0000000000..46aa205480
--- /dev/null
+++ b/examples/jms/stomp-websockets/chat/stomp.js
@@ -0,0 +1,370 @@
+// Generated by CoffeeScript 1.3.3
+(function() {
+ var Byte, Client, Frame, Stomp,
+ __hasProp = {}.hasOwnProperty;
+
+ Byte = {
+ LF: '\x0A',
+ NULL: '\x00'
+ };
+
+ Frame = (function() {
+
+ function Frame(command, headers, body) {
+ this.command = command;
+ this.headers = headers != null ? headers : {};
+ this.body = body != null ? body : '';
+ }
+
+ Frame.prototype.toString = function() {
+ var lines, name, value, _ref;
+ lines = [this.command];
+ _ref = this.headers;
+ for (name in _ref) {
+ if (!__hasProp.call(_ref, name)) continue;
+ value = _ref[name];
+ lines.push("" + name + ":" + value);
+ }
+ if (this.body) {
+ lines.push("content-length:" + ('' + this.body).length);
+ }
+ lines.push(Byte.LF + this.body);
+ return lines.join(Byte.LF);
+ };
+
+ Frame._unmarshallSingle = function(data) {
+ var body, chr, command, divider, headerLines, headers, i, idx, len, line, start, trim, _i, _j, _ref, _ref1;
+ divider = data.search(RegExp("" + Byte.LF + Byte.LF));
+ headerLines = data.substring(0, divider).split(Byte.LF);
+ command = headerLines.shift();
+ headers = {};
+ trim = function(str) {
+ return str.replace(/^\s+|\s+$/g, '');
+ };
+ line = idx = null;
+ for (i = _i = 0, _ref = headerLines.length; 0 <= _ref ? _i < _ref : _i > _ref; i = 0 <= _ref ? ++_i : --_i) {
+ line = headerLines[i];
+ idx = line.indexOf(':');
+ headers[trim(line.substring(0, idx))] = trim(line.substring(idx + 1));
+ }
+ body = '';
+ start = divider + 2;
+ if (headers['content-length']) {
+ len = parseInt(headers['content-length']);
+ body = ('' + data).substring(start, start + len);
+ } else {
+ chr = null;
+ for (i = _j = start, _ref1 = data.length; start <= _ref1 ? _j < _ref1 : _j > _ref1; i = start <= _ref1 ? ++_j : --_j) {
+ chr = data.charAt(i);
+ if (chr === Byte.NULL) {
+ break;
+ }
+ body += chr;
+ }
+ }
+ return new Frame(command, headers, body);
+ };
+
+ Frame.unmarshall = function(datas) {
+ var data;
+ return (function() {
+ var _i, _len, _ref, _results;
+ _ref = datas.split(RegExp("" + Byte.NULL + Byte.LF + "*"));
+ _results = [];
+ for (_i = 0, _len = _ref.length; _i < _len; _i++) {
+ data = _ref[_i];
+ if ((data != null ? data.length : void 0) > 0) {
+ _results.push(Frame._unmarshallSingle(data));
+ }
+ }
+ return _results;
+ })();
+ };
+
+ Frame.marshall = function(command, headers, body) {
+ var frame;
+ frame = new Frame(command, headers, body);
+ return frame.toString() + Byte.NULL;
+ };
+
+ return Frame;
+
+ })();
+
+ Client = (function() {
+
+ function Client(ws) {
+ this.ws = ws;
+ this.ws.binaryType = "arraybuffer";
+ this.counter = 0;
+ this.connected = false;
+ this.heartbeat = {
+ outgoing: 10000,
+ incoming: 10000
+ };
+ this.subscriptions = {};
+ }
+
+ Client.prototype._transmit = function(command, headers, body) {
+ var out;
+ out = Frame.marshall(command, headers, body);
+ if (typeof this.debug === "function") {
+ this.debug(">>> " + out);
+ }
+ return this.ws.send(out);
+ };
+
+ Client.prototype._setupHeartbeat = function(headers) {
+ var serverIncoming, serverOutgoing, ttl, v, _ref, _ref1,
+ _this = this;
+ if ((_ref = headers.version) !== Stomp.VERSIONS.V1_1 && _ref !== Stomp.VERSIONS.V1_2) {
+ return;
+ }
+ _ref1 = (function() {
+ var _i, _len, _ref1, _results;
+ _ref1 = headers['heart-beat'].split(",");
+ _results = [];
+ for (_i = 0, _len = _ref1.length; _i < _len; _i++) {
+ v = _ref1[_i];
+ _results.push(parseInt(v));
+ }
+ return _results;
+ })(), serverOutgoing = _ref1[0], serverIncoming = _ref1[1];
+ if (!(this.heartbeat.outgoing === 0 || serverIncoming === 0)) {
+ ttl = Math.max(this.heartbeat.outgoing, serverIncoming);
+ if (typeof this.debug === "function") {
+ this.debug("send PING every " + ttl + "ms");
+ }
+ this.pinger = typeof window !== "undefined" && window !== null ? window.setInterval(function() {
+ _this.ws.send(Byte.LF);
+ return typeof _this.debug === "function" ? _this.debug(">>> PING") : void 0;
+ }, ttl) : void 0;
+ }
+ if (!(this.heartbeat.incoming === 0 || serverOutgoing === 0)) {
+ ttl = Math.max(this.heartbeat.incoming, serverOutgoing);
+ if (typeof this.debug === "function") {
+ this.debug("check PONG every " + ttl + "ms");
+ }
+ return this.ponger = typeof window !== "undefined" && window !== null ? window.setInterval(function() {
+ var delta;
+ delta = Date.now() - _this.serverActivity;
+ if (delta > ttl * 2) {
+ if (typeof _this.debug === "function") {
+ _this.debug("did not receive server activity for the last " + delta + "ms");
+ }
+ return _this._cleanUp();
+ }
+ }, ttl) : void 0;
+ }
+ };
+
+ Client.prototype.connect = function(login, passcode, connectCallback, errorCallback, vhost) {
+ var _this = this;
+ this.connectCallback = connectCallback;
+ if (typeof this.debug === "function") {
+ this.debug("Opening Web Socket...");
+ }
+ this.ws.onmessage = function(evt) {
+ var arr, c, data, frame, onreceive, _i, _len, _ref, _results;
+ data = typeof ArrayBuffer !== 'undefined' && evt.data instanceof ArrayBuffer ? (arr = new Uint8Array(evt.data), typeof _this.debug === "function" ? _this.debug("--- got data length: " + arr.length) : void 0, ((function() {
+ var _i, _len, _results;
+ _results = [];
+ for (_i = 0, _len = arr.length; _i < _len; _i++) {
+ c = arr[_i];
+ _results.push(String.fromCharCode(c));
+ }
+ return _results;
+ })()).join('')) : evt.data;
+ _this.serverActivity = Date.now();
+ if (data === Byte.LF) {
+ if (typeof _this.debug === "function") {
+ _this.debug("<<< PONG");
+ }
+ return;
+ }
+ if (typeof _this.debug === "function") {
+ _this.debug("<<< " + data);
+ }
+ _ref = Frame.unmarshall(data);
+ _results = [];
+ for (_i = 0, _len = _ref.length; _i < _len; _i++) {
+ frame = _ref[_i];
+ switch (frame.command) {
+ case "CONNECTED":
+ if (typeof _this.debug === "function") {
+ _this.debug("connected to server " + frame.headers.server);
+ }
+ _this.connected = true;
+ _this._setupHeartbeat(frame.headers);
+ _results.push(typeof _this.connectCallback === "function" ? _this.connectCallback(frame) : void 0);
+ break;
+ case "MESSAGE":
+ onreceive = _this.subscriptions[frame.headers.subscription];
+ _results.push(typeof onreceive === "function" ? onreceive(frame) : void 0);
+ break;
+ case "RECEIPT":
+ _results.push(typeof _this.onreceipt === "function" ? _this.onreceipt(frame) : void 0);
+ break;
+ case "ERROR":
+ _results.push(typeof errorCallback === "function" ? errorCallback(frame) : void 0);
+ break;
+ default:
+ _results.push(typeof _this.debug === "function" ? _this.debug("Unhandled frame: " + frame) : void 0);
+ }
+ }
+ return _results;
+ };
+ this.ws.onclose = function() {
+ var msg;
+ msg = "Whoops! Lost connection to " + _this.ws.url;
+ if (typeof _this.debug === "function") {
+ _this.debug(msg);
+ }
+ return typeof errorCallback === "function" ? errorCallback(msg) : void 0;
+ };
+ return this.ws.onopen = function() {
+ var headers;
+ if (typeof _this.debug === "function") {
+ _this.debug('Web Socket Opened...');
+ }
+ headers = {
+ "accept-version": Stomp.VERSIONS.supportedVersions(),
+ "heart-beat": [_this.heartbeat.outgoing, _this.heartbeat.incoming].join(',')
+ };
+ if (vhost) {
+ headers.host = vhost;
+ }
+ if (login) {
+ headers.login = login;
+ }
+ if (passcode) {
+ headers.passcode = passcode;
+ }
+ return _this._transmit("CONNECT", headers);
+ };
+ };
+
+ Client.prototype.disconnect = function(disconnectCallback) {
+ this._transmit("DISCONNECT");
+ this.ws.onclose = null;
+ this._cleanUp();
+ return typeof disconnectCallback === "function" ? disconnectCallback() : void 0;
+ };
+
+ Client.prototype._cleanUp = function() {
+ this.ws.close();
+ this.connected = false;
+ if (this.pinger) {
+ if (typeof window !== "undefined" && window !== null) {
+ window.clearInterval(this.pinger);
+ }
+ }
+ if (this.ponger) {
+ return typeof window !== "undefined" && window !== null ? window.clearInterval(this.ponger) : void 0;
+ }
+ };
+
+ Client.prototype.send = function(destination, headers, body) {
+ if (headers == null) {
+ headers = {};
+ }
+ if (body == null) {
+ body = '';
+ }
+ headers.destination = destination;
+ return this._transmit("SEND", headers, body);
+ };
+
+ Client.prototype.subscribe = function(destination, callback, headers) {
+ if (headers == null) {
+ headers = {};
+ }
+ if (!headers.id) {
+ headers.id = "sub-" + this.counter++;
+ }
+ headers.destination = destination;
+ this.subscriptions[headers.id] = callback;
+ this._transmit("SUBSCRIBE", headers);
+ return headers.id;
+ };
+
+ Client.prototype.unsubscribe = function(id) {
+ delete this.subscriptions[id];
+ return this._transmit("UNSUBSCRIBE", {
+ id: id
+ });
+ };
+
+ Client.prototype.begin = function(transaction) {
+ return this._transmit("BEGIN", {
+ transaction: transaction
+ });
+ };
+
+ Client.prototype.commit = function(transaction) {
+ return this._transmit("COMMIT", {
+ transaction: transaction
+ });
+ };
+
+ Client.prototype.abort = function(transaction) {
+ return this._transmit("ABORT", {
+ transaction: transaction
+ });
+ };
+
+ Client.prototype.ack = function(messageID, subscription, headers) {
+ if (headers == null) {
+ headers = {};
+ }
+ headers["message-id"] = messageID;
+ headers.subscription = subscription;
+ return this._transmit("ACK", headers);
+ };
+
+ Client.prototype.nack = function(messageID, subscription, headers) {
+ if (headers == null) {
+ headers = {};
+ }
+ headers["message-id"] = messageID;
+ headers.subscription = subscription;
+ return this._transmit("NACK", headers);
+ };
+
+ return Client;
+
+ })();
+
+ Stomp = {
+ libVersion: "2.0.0-next",
+ VERSIONS: {
+ V1_0: '1.0',
+ V1_1: '1.1',
+ V1_2: '1.2',
+ supportedVersions: function() {
+ return '1.1,1.0';
+ }
+ },
+ client: function(url, protocols) {
+ var klass, ws;
+ if (protocols == null) {
+ protocols = ['v10.stomp', 'v11.stomp'];
+ }
+ klass = Stomp.WebSocketClass || WebSocket;
+ ws = new klass(url, protocols);
+ return new Client(ws);
+ },
+ over: function(ws) {
+ return new Client(ws);
+ },
+ Frame: Frame
+ };
+
+ if (typeof window !== "undefined" && window !== null) {
+ window.Stomp = Stomp;
+ } else {
+ exports.Stomp = Stomp;
+ Stomp.WebSocketClass = require('./test/server.mock.js').StompServerMock;
+ }
+
+}).call(this);
diff --git a/examples/jms/stomp-websockets/pom.xml b/examples/jms/stomp-websockets/pom.xml
new file mode 100644
index 0000000000..6023eff6b0
--- /dev/null
+++ b/examples/jms/stomp-websockets/pom.xml
@@ -0,0 +1,130 @@
+Stomp WebSockets Example
+ +This example shows you how to configure HornetQ to send and receive Stomp messages from modern web browser using Web Sockets.
+ +The example will start a HornetQ server configured with Stomp over Web Sockets and JMS. Web browsers clients and + Java application will exchange message using a JMS Topic.
++<acceptor name="stomp-websocket"> + <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class> + <param key="port" value="61614"/> +</acceptor>+ +
Example step-by-step
+ +To run the example, simply type mvn verify from this directory
To subscribe to the topic from your web browser, open the Chat Example or the JBoss AeroGear STOMP notifier Chat Example from another tab.
+ The chat example is preconfigured to connect to the HornetQ server with the URL ws://localhost:61614/stomp and subscribe to the JMS Topic (through its core address
+ jms.topic.chat).
+
You can open as many Web clients as you want and they will all exchange messages through the topic
+If you run again the Java application (with ./build.sh), the web clients will also receive its message
Documentation
+A JavaScript library is used on the browser side to be able to use Stomp Over Web Sockets (please see its documentation + for a complete description).
+The JBoss AeroGear STOMP notifier Chat Example is using the AeroGear Notifier which is a collection of adapters that provide a unified or similar API for interacting with different messaging services and protocols. The STOMP adapter is used for communicating with STOMP over WebSockets. See more at: JBoss aerogear-js
+ + diff --git a/examples/jms/stomp-websockets/src/main/java/org/hornetq/jms/example/StompWebSocketExample.java b/examples/jms/stomp-websockets/src/main/java/org/hornetq/jms/example/StompWebSocketExample.java new file mode 100644 index 0000000000..e7c7473069 --- /dev/null +++ b/examples/jms/stomp-websockets/src/main/java/org/hornetq/jms/example/StompWebSocketExample.java @@ -0,0 +1,87 @@ +/* + * Copyright 2005-2014 Red Hat, Inc. + * Red Hat licenses this file to you under the Apache License, version + * 2.0 (the "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * http://www.apache.org/licenses/LICENSE-2.0 + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + * implied. See the License for the specific language governing + * permissions and limitations under the License. + */ +package org.hornetq.jms.example; + +import java.util.Date; + +import javax.jms.Connection; +import javax.jms.ConnectionFactory; +import javax.jms.MessageConsumer; +import javax.jms.MessageProducer; +import javax.jms.Session; +import javax.jms.TextMessage; +import javax.jms.Topic; +import javax.naming.InitialContext; + +import org.hornetq.common.example.HornetQExample; + +/** + * An example where a client will send a JMS message to a Topic. + * Browser clients connected using Web Sockets will be able to receive the message. + * + * @author Jeff Mesnil + */ +public class StompWebSocketExample extends HornetQExample +{ + public static void main(final String[] args) + { + new StompWebSocketExample().run(args); + } + + @Override + public boolean runExample() throws Exception + { + Connection connection = null; + InitialContext initialContext = null; + try + { + initialContext = getContext(0); + Topic topic = (Topic)initialContext.lookup("/topic/chat"); + ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory"); + connection = cf.createConnection(); + Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); + + MessageProducer producer = session.createProducer(topic); + MessageConsumer consumer = session.createConsumer(topic); + + // use JMS bytes message with UTF-8 String to send a text to Stomp clients + String text = "message sent from a Java application at " + new Date(); + //BytesMessage message = session.createBytesMessage(); + //message.writeBytes(text.getBytes("UTF-8")); + TextMessage message = session.createTextMessage(text); + System.out.println("Sent message: " + text); + System.out.println("Open up the chat/index.html file in a browser and press enter"); + System.in.read(); + producer.send(message); + + connection.start(); + + message = (TextMessage)consumer.receive(); + System.out.println("Received message: " + message.getText()); + + return true; + } + finally + { + if (connection != null) + { + connection.close(); + } + + if (initialContext != null) + { + initialContext.close(); + } + } + } +} \ No newline at end of file diff --git a/examples/jms/stomp-websockets/src/main/resources/hornetq/server0/hornetq-configuration.xml b/examples/jms/stomp-websockets/src/main/resources/hornetq/server0/hornetq-configuration.xml new file mode 100644 index 0000000000..d7f59232a8 --- /dev/null +++ b/examples/jms/stomp-websockets/src/main/resources/hornetq/server0/hornetq-configuration.xml @@ -0,0 +1,49 @@ +Stomp Example
+ +This example shows you how to configure HornetQ to send and receive Stomp messages.
+The example will start a HornetQ server configured with Stomp and JMS.
+The client will open a socket to send one Stomp message (using TCP directly). + The client will then consume a message from a JMS Queue and check it is the message sent with Stomp.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ String connectFrame = "CONNECT\n" + + "login: guest\n" + + "passcode: guest\n" + + "request-id: 1\n" + + "\n" + + Stomp.NULL; + sendFrame(socket, connectFrame); ++ +
+ String text = "Hello, world from Stomp!";
+ String message = "SEND\n" +
+ "destination: jms.queue.exampleQueue\n" +
+ "\n" +
+ text +
+ Stomp.NULL;
+ sendFrame(socket, message);
+ System.out.println("Sent Stomp message: " + text);
+
+
+ + String disconnectFrame = "DISCONNECT\n" + + "\n" + + Stomp.NULL; + sendFrame(socket, disconnectFrame); ++ +
+ socket.close(); ++ +
+ initialContext = getContext(0); ++ +
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+ + connection = cf.createConnection(); + Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); + MessageConsumer consumer = session.createConsumer(queue); ++ +
+ connection.start();
+
+
+
+ TextMessage messageReceived = (TextMessage)consumer.receive(5000);
+ System.out.println("Received JMS message: " + messageReceived.getText());
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ Stomp 1.1 Example
+ +This example shows you how to configure HornetQ to send and receive Stomp messages using Stomp 1.1 protocol.
+The example will start a HornetQ server configured with Stomp and JMS.
+The client will open a socket to initiate a Stomp 1.1 connection and then send one Stomp message (using TCP directly). + The client will then consume a message from a JMS Queue and check it is the message sent with Stomp.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ String connectFrame = "CONNECT\n" + + "accept-version:1.1\n" + + "host:localhost\n" + + "login:guest\n" + + "passcode:guest\n" + + "request-id:1\n" + + "\n" + + END_OF_FRAME; + sendFrame(socket, connectFrame); ++ +
+ String response = receiveFrame(socket);
+ System.out.println("response: " + response);
+
+
+
+ String text = "Hello World from Stomp 1.1 !";
+ String message = "SEND\n" +
+ "destination:jms.queue.exampleQueue\n" +
+ "\n" +
+ text +
+ END_OF_FRAME;
+ sendFrame(socket, message);
+ System.out.println("Sent Stomp message: " + text);
+
+
+ + String disconnectFrame = "DISCONNECT\n" + + "\n" + + Stomp.NULL; + sendFrame(socket, disconnectFrame); ++ +
+ socket.close(); ++ +
+ initialContext = getContext(0); ++ +
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+ + connection = cf.createConnection(); + Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); + MessageConsumer consumer = session.createConsumer(queue); ++ +
+ connection.start();
+
+
+
+ TextMessage messageReceived = (TextMessage)consumer.receive(5000);
+ System.out.println("Received JMS message: " + messageReceived.getText());
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ Stomp 1.2 Example
+ +This example shows you how to configure HornetQ to send and receive Stomp messages using Stomp 1.2 protocol.
+The example will start a HornetQ server configured with Stomp and JMS.
+The client will open a socket to initiate a Stomp 1.2 connection and then send one Stomp message (using TCP directly). + The client will then consume a message from a JMS Queue and check it is the message sent with Stomp.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ String connectFrame = "CONNECT\n" + + "accept-version:1.1\n" + + "host:localhost\n" + + "login:guest\n" + + "passcode:guest\n" + + "request-id:1\n" + + "\n" + + END_OF_FRAME; + sendFrame(socket, connectFrame); ++ +
+ String response = receiveFrame(socket);
+ System.out.println("response: " + response);
+
+
+
+ String text = "Hello World from Stomp 1.2 !";
+ String message = "SEND\n" +
+ "destination:jms.queue.exampleQueue\n" +
+ "\n" +
+ text +
+ END_OF_FRAME;
+ sendFrame(socket, message);
+ System.out.println("Sent Stomp message: " + text);
+
+
+ + String disconnectFrame = "DISCONNECT\n" + + "\n" + + Stomp.NULL; + sendFrame(socket, disconnectFrame); ++ +
+ socket.close(); ++ +
+ initialContext = getContext(0); ++ +
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+ + connection = cf.createConnection(); + Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); + MessageConsumer consumer = session.createConsumer(queue); ++ +
+ connection.start();
+
+
+
+ TextMessage messageReceived = (TextMessage)consumer.receive(5000);
+ System.out.println("Received JMS message: " + messageReceived.getText());
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ JMS Failover Without Transactions Example
+ +This example demonstrates two servers coupled as a live-backup pair for high availability (HA), and a client + connection failing over from live to backup when the live server is crashed.
+Failover behavior differs whether the JMS session is transacted or not.
+When a non-transacted JMS session is used, once and only once delivery is not guaranteed + and it is possible some messages will be lost or delivered twice, depending when the failover to the backup server occurs.
+It is up to the client to deal with such cases. To ensure once and only once delivery, the client must + use transacted JMS sessions (as shown in the example for failover with transactions).
+For more information on HornetQ failover and HA, and clustering in general, please see the clustering + section of the user manual.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
In this example, the live server is server 1, and the backup server is server 0
+The connection will initially be created to server1, server 1 will crash, and the client will carry on + seamlessly on server 0, the backup server.
+-
+
+ initialContext = getContext(1); ++ +
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+ ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+ + connection = connectionFactory.createConnection(); ++ +
+ Session session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE); ++ +
+ connection.start(); ++ +
+ MessageProducer producer = session.createProducer(queue); + MessageConsumer consumer = session.createConsumer(queue); ++ +
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message = session.createTextMessage("This is text message " + i);
+ producer.send(message);
+ System.out.println("Sent message: " + message.getText());
+ }
+
+
+
+ TextMessage message0 = null;
+ for (int i = 0; i < numMessages / 2; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+ message0.acknowledge();
+
+
+
+ for (int i = numMessages / 2; i < numMessages; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+
+
+ + killServer(1); + Thread.sleep(2000); ++ +
+ try
+ {
+ message0.acknowledge();
+ }
+ catch (JMSException e)
+ {
+ System.err.println("Got exception while acknowledging message: " + e.getMessage());
+ }
+
+
+
+ for (int i = numMessages / 2; i < numMessages; i++)
+ {
+ message0 = (TextMessage)consumer.receive(5000);
+ System.out.printf("Got message: %s (redelivered?: %s)\n", message0.getText(), message0.getJMSRedelivered());
+ }
+ message0.acknowledge();
+
+
+
+ finally
+ {
+ if (connection != null)
+ {
+ connection.close();
+ }
+
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ }
+
+
+ JMS Symmetric Cluster Example
+ +This examples demonstrates a symmetric cluster set-up with HornetQ.
+HornetQ has extremely flexible clustering which allows you to set-up servers in + many different topologies.
+The most common topology that you'll perhaps be familiar with if you are used to application + server clustering is a symmetric cluster.
+With a symmetric cluster, the cluster is homogeneous, i.e. each node is configured the same + as every other node, and every node is connected to every other node in the cluster.
+By connecting node in such a way, we can, from a JMS point of view, give the impression of distributed + JMS queues and topics.
+The configuration used in this example is very similar to the configuration used by HornetQ + when installed as a clustered profile in JBoss Application Server.
+To set up HornetQ to form a symmetric cluster we simply need to mark each server as clustered
+ and we need to define a cluster-connection in hornetq-configuration.xml.
The cluster-connection tells the nodes what other nodes to make connections to.
+ With a cluster-connection each node that we connect to can either be specified
+ indivually, or we can use UDP discovery to find out what other nodes are in the cluster.
Using UDP discovery makes configuration simpler since we don't have to know what nodes are + available at any one time.
+Here's the relevant snippet from the server configuration, which tells the server to form a cluster + with the other nodes:
+
+
+ <cluster-connection name="my-cluster">
+ <address>jms</address>
+ <connector-ref>netty-connector</connector-ref>
+ <retry-interval>500</retry-interval>
+ <use-duplicate-detection>true</use-duplicate-detection>
+ <forward-when-no-consumers>true</forward-when-no-consumers>
+ <max-hops>1</max-hops>
+ <discovery-group-ref discovery-group-name="my-discovery-group"/>
+ </cluster-connection>
+
+
+ In this example we create a symmetric cluster of six live nodes, and we also pair each live node + with it's own backup node. (A backup node is not strictly necessary for a symmetric cluster).
+In this example will we will demonstrate this by deploying a JMS topic and Queue on all nodes of the cluster + , sending messages to the queue and topic from different nodes, and verifying messages are received correctly + by consumers on different nodes.
+For more information on configuring HornetQ clustering in general, please see the clustering + section of the user manual.
+Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+
+ ConnectionFactory cf = HornetQJMSClient.createConnectionFactoryWithHA("231.7.7.7", 9876);
+
+
+
+
+
+ Queue queue = new HornetQQueue("exampleQueue");
+
+ Topic topic = HornetQJMSClient.createHornetQTopic("exampleTopic");
+
+
+
+
+
+ connection0 = cf.createConnection();
+
+ connection1 = cf.createConnection();
+
+ connection2 = cf.createConnection();
+
+ connection3 = cf.createConnection();
+
+ connection4 = cf.createConnection();
+
+ connection5 = cf.createConnection();
+
+ connection0.start();
+
+ connection1.start();
+
+ connection2.start();
+
+ connection3.start();
+
+ connection4.start();
+
+ connection5.start();
+
+
+
+
+
+ Session session0 = connection0.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+ Session session1 = connection1.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+ Session session2 = connection2.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+ Session session3 = connection0.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+ Session session4 = connection1.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+ Session session5 = connection2.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+
+ MessageConsumer subscriber0 = session0.createConsumer(topic);
+
+ MessageConsumer subscriber1 = session1.createConsumer(topic);
+
+ MessageConsumer subscriber2 = session2.createConsumer(topic);
+
+ MessageConsumer subscriber3 = session3.createConsumer(topic);
+
+ MessageConsumer subscriber4 = session4.createConsumer(topic);
+
+ MessageConsumer subscriber5 = session5.createConsumer(topic);
+
+
+
+
+
+ MessageConsumer consumer0 = session0.createConsumer(queue);
+
+
+
+
+
+ MessageProducer producer2 = session2.createProducer(null);
+
+
+
+
+
+ final int numMessages = 500;
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message1 = session2.createTextMessage("Topic message 1");
+
+ producer2.send(topic, message1);
+
+ TextMessage message2 = session2.createTextMessage("Queue message 1");
+
+ producer2.send(queue, message2);
+ }
+
+
+
+
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage received0 = (TextMessage)subscriber0.receive(5000);
+
+ if (received0 == null)
+ {
+ return false;
+ }
+
+ TextMessage received1 = (TextMessage)subscriber1.receive(5000);
+
+ if (received1 == null)
+ {
+ return false;
+ }
+
+ TextMessage received2 = (TextMessage)subscriber2.receive(5000);
+
+ if (received2 == null)
+ {
+ return false;
+ }
+
+ TextMessage received3 = (TextMessage)subscriber3.receive(5000);
+
+ if (received3 == null)
+ {
+ return false;
+ }
+
+ TextMessage received4 = (TextMessage)subscriber4.receive(5000);
+
+ if (received4 == null)
+ {
+ return false;
+ }
+
+ TextMessage received5 = (TextMessage)subscriber5.receive(5000);
+
+ if (received5 == null)
+ {
+ return false;
+ }
+
+ TextMessage received6 = (TextMessage)consumer0.receive(5000);
+
+ if (received6 == null)
+ {
+ return false;
+ }
+ }
+
+
+
+
+
+ finally
+ {
+ if (connection0 != null)
+ {
+ connection0.close();
+ }
+
+ if (connection1 != null)
+ {
+ connection1.close();
+ }
+
+ if (connection2 != null)
+ {
+ connection2.close();
+ }
+ }
+
+
+
+ + * This is probably the most obvious clustering topology and the one most people will be familiar + * with from using clustering in an app server, where every node has pretty much identical + * configuration to every other node. + *
+ * By clustering nodes symmetrically, HornetQ can give the impression of clustered queues, topics + * and durable subscriptions. + *
+ * In this example we send some messages to a distributed queue and topic and kill all the live + * servers at different times, and verify that they transparently fail over onto their backup + * servers. + *
+ * Please see the readme.html file for more information.
+ * @author
+
+
+
+ This example shows you how to use a TemporaryQueue with HornetQ. First a temporary queue is created to send and receive a message and then deleted.
+ Then another temporary queue is created and used after its connection is closed to illustrate its scope. A TemporaryQueue is a JMS queue that exists only within the lifetime of its connection. It is often used in request-reply
+ type messaging where the reply is sent through a temporary destination. The temporary queue is often created as
+ a server resource, so after using, the user should call delete() method to release the resources.
+ Please consult the JMS 1.1 specification for full details. To run the example, simply type JMS Temporary Queue Example
+
+ Example step-by-step
+ mvn verify from this directory
+
+
+
diff --git a/examples/jms/temp-queue/src/main/java/org/hornetq/jms/example/TemporaryQueueExample.java b/examples/jms/temp-queue/src/main/java/org/hornetq/jms/example/TemporaryQueueExample.java
new file mode 100644
index 0000000000..d70ad1c430
--- /dev/null
+++ b/examples/jms/temp-queue/src/main/java/org/hornetq/jms/example/TemporaryQueueExample.java
@@ -0,0 +1,133 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+package org.hornetq.jms.example;
+
+import javax.jms.Connection;
+import javax.jms.ConnectionFactory;
+import javax.jms.JMSException;
+import javax.jms.MessageConsumer;
+import javax.jms.MessageProducer;
+import javax.jms.Session;
+import javax.jms.TemporaryQueue;
+import javax.jms.TextMessage;
+import javax.naming.InitialContext;
+
+import org.hornetq.common.example.HornetQExample;
+
+/**
+ * A simple JMS example that shows how to use temporary queues.
+ *
+ * @author Howard Gao
+ */
+public class TemporaryQueueExample extends HornetQExample
+{
+ public static void main(final String[] args)
+ {
+ new TemporaryQueueExample().run(args);
+ }
+
+ @Override
+ public boolean runExample() throws Exception
+ {
+ Connection connection = null;
+ InitialContext initialContext = null;
+ try
+ {
+ // Step 1. Create an initial context to perform the JNDI lookup.
+ initialContext = getContext(0);
+
+ // Step 2. Look-up the JMS connection factory
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+ // Step 3. Create a JMS Connection
+ connection = cf.createConnection();
+
+ // Step 4. Start the connection
+ connection.start();
+
+ // Step 5. Create a JMS session with AUTO_ACKNOWLEDGE mode
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+ // Step 6. Create a Temporary Queue
+ TemporaryQueue tempQueue = session.createTemporaryQueue();
+
+ System.out.println("Temporary queue is created: " + tempQueue);
+
+ // Step 7. Create a JMS message producer
+ MessageProducer messageProducer = session.createProducer(tempQueue);
+
+ // Step 8. Create a text message
+ TextMessage message = session.createTextMessage("This is a text message");
+
+ // Step 9. Send the text message to the queue
+ messageProducer.send(message);
+
+ System.out.println("Sent message: " + message.getText());
+
+ // Step 11. Create a message consumer
+ MessageConsumer messageConsumer = session.createConsumer(tempQueue);
+
+ // Step 12. Receive the message from the queue
+ message = (TextMessage)messageConsumer.receive(5000);
+
+ System.out.println("Received message: " + message.getText());
+
+ // Step 13. Close the consumer and producer
+ messageConsumer.close();
+ messageProducer.close();
+
+ // Step 14. Delete the temporary queue
+ tempQueue.delete();
+
+ // Step 15. Create another temporary queue.
+ TemporaryQueue tempQueue2 = session.createTemporaryQueue();
+
+ System.out.println("Another temporary queue is created: " + tempQueue2);
+
+ // Step 16. Close the connection.
+ connection.close();
+
+ // Step 17. Create a new connection.
+ connection = cf.createConnection();
+
+ // Step 18. Create a new session.
+ session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+ // Step 19. Try to access the tempQueue2 outside its lifetime
+ try
+ {
+ messageConsumer = session.createConsumer(tempQueue2);
+ throw new Exception("Temporary queue cannot be accessed outside its lifecycle!");
+ }
+ catch (JMSException e)
+ {
+ System.out.println("Exception got when trying to access a temp queue outside its scope: " + e);
+ }
+
+ return true;
+ }
+ finally
+ {
+ if (connection != null)
+ {
+ // Step 20. Be sure to close our JMS resources!
+ connection.close();
+ }
+ if (initialContext != null)
+ {
+ // Step 21. Also close the initialContext!
+ initialContext.close();
+ }
+ }
+ }
+}
diff --git a/examples/jms/temp-queue/src/main/resources/hornetq/server0/hornetq-configuration.xml b/examples/jms/temp-queue/src/main/resources/hornetq/server0/hornetq-configuration.xml
new file mode 100644
index 0000000000..10a15fd02d
--- /dev/null
+++ b/examples/jms/temp-queue/src/main/resources/hornetq/server0/hornetq-configuration.xml
@@ -0,0 +1,50 @@
+
+
+
+ initialContext = getContext();
+
+
+
+ ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ connection.start();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ Queue tempQueue = session.createTemporaryQueue();
+
+
+
+ MessageProducer messageProducer = session.createProducer(tempQueue);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+
+ messageProducer.send(message);
+
+
+
+ MessageConsumer messageConsumer = session.createConsumer(tempQueue);
+
+
+
+ message = (TextMessage) messageConsumer.receive(5000);
+
+
+
+ messageConsumer.close();
+ messageProducer.close();
+
+
+
+ tempQueue.delete();
+
+
+
+ TemporaryQueue tempQueue2 = session.createTemporaryQueue();
+
+
+
+ connection.close();
+
+
+
+ connection = cf.createConnection();
+
+
+
+ session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+ try
+ {
+ messageConsumer = session.createConsumer(tempQueue2);
+ throw new Exception("Temporary queue cannot be accessed outside its lifecycle!");
+ }
+ catch (InvalidDestinationException e)
+ {
+ System.out.println("Exception got when trying to access a temp queue outside its scope: " + e);
+ }
+
+
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
Topic Hierarchy Example
+ +HornetQ supports topic hierarchies. With a topic hierarchy you can register a subscriber with a wild-card + and that subscriber will receive any messages routed to an address that match the wildcard.
+HornetQ wild-cards can use the character '#' which means "match any number of words", and + the character '*' which means "match a single word". Words are delimited by the character "."
+For example if I subscribe using the wild-card "news.europe.#", then that would match messages sent to the addresses + "news.europe", "news.europe.sport" and "news.europe.entertainment", but it does not match messages sent to the + address "news.usa.wrestling"
+For more information on the wild-card syntax please consult the user manual.
+Example step-by-step
+To run the example, simply type mvn verify from this directory
In this example we will define a hierarchy of topics in the file hornetq-jms.xml
+
+ <topic name="news">
+ <entry name="/topic/news"/>
+ </topic>
+
+ <topic name="news.usa">
+ <entry name="/topic/news.usa"/>
+ </topic>
+
+ <topic name="news.usa.wrestling">
+ <entry name="/topic/news.wrestling"/>
+ </topic>
+
+ <topic name="news.europe">
+ <entry name="/topic/news.europe"/>
+ </topic>
+
+ <topic name="news.europe.sport">
+ <entry name="/topic/news.europe.sport"/>
+ </topic>
+
+ <topic name="news.europe.entertainment">
+ <entry name="/topic/news.europe.entertainment"/>
+ </topic>
+
+
+ Then we will create a subscriber using the wildcard "news.europe.#".
+We will then send three messages: one to the address news.usa.wrestling, one to the address news.europe.sport, + and one to the address news.europe.entertainment.
+We will verify that the message sent to news.usa.wrestling does not get received since it does not match, + but the messages sent to the other two addresses do get received since they match.
+ +-
+
+ initialContext = getContext(0);
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ Topic topicSubscribe = HornetQJMSClient.createHornetQTopic("news.europe.#");
+
+
+
+ MessageConsumer messageConsumer = session.createConsumer(topicSubscribe);
+
+
+
+ MessageProducer producer = session.createProducer(null);
+
+
+
+
+ Topic topicNewsUsaWrestling = HornetQJMSClient.createHornetQTopic("news.usa.wrestling");
+
+ Topic topicNewsEuropeSport = HornetQJMSClient.createHornetQTopic("news.europe.sport");
+
+ Topic topicNewsEuropeEntertainment = HornetQJMSClient.createHornetQTopic("news.europe.entertainment");
+
+
+
+
+ TextMessage messageWrestlingNews = session.createTextMessage("Hulk Hogan starts ballet classes");
+
+ producer.send(topicNewsUsaWrestling, messageWrestlingNews);
+
+
+
+
+
+ TextMessage messageEuropeSport = session.createTextMessage("Lewis Hamilton joins European synchronized swimming team");
+
+ producer.send(topicNewsEuropeSport, messageEuropeSport);
+
+
+
+
+
+ TextMessage messageEuropeEntertainment = session.createTextMessage("John Lennon resurrected from dead");
+
+ producer.send(topicNewsEuropeEntertainment, messageEuropeEntertainment);
+
+
+
+
+
+ connection.start();
+
+
+
+
+
+ TextMessage messageReceived1 = (TextMessage)messageConsumer.receive(5000);
+
+ System.out.println("Received message: " + messageReceived1.getText());
+
+ TextMessage messageReceived2 = (TextMessage)messageConsumer.receive(5000);
+
+ System.out.println("Received message: " + messageReceived2.getText());
+
+ Message message = messageConsumer.receive(1000);
+
+ if (message != null)
+ {
+ return false;
+ }
+
+ System.out.println("Didn't received any more message: " + message);
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ JMS Topic Selector Example 1
+ +This example shows how messages can be consumed from a topic using Message Selectors.
+Consumers (or Subscribers) will only consume messages routed to a topic that match the provided selector
+Topics and selectors are a standard part of JMS, please consult the JMS 1.1 specification for full details.
+ + +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ initialContext = getContext();
+
+
+
+ Topic topic = (Topic) initialContext.lookup("/topic/exampleTopic");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(topic);
+
+
+
+ MessageConsumer messageConsumer1 = session.createConsumer(topic, "someID=1", false);
+
+
+
+ MessageConsumer messageConsumer2 = session.createConsumer(topic, "someID=2", false);
+
+
+
+ MessageConsumer messageConsumer3 = session.createConsumer(topic, "someID=2", false);
+
+
+
+ for (int i = 1; i < 10; i++)
+ {
+ for (int someID = 1; someID <= 2; someID++)
+ {
+ TextMessage message1 = session.createTextMessage("This is a text message " + i +
+ " sent for someID=" +
+ someID);
+
+ message1.setIntProperty("someID", someID);
+
+ producer.send(message1);
+
+ System.out.println("Sent message: " + message1.getText());
+ }
+ } connection.start();
+
+
+
+
+ for (;;)
+ {
+ TextMessage messageReceivedA = (TextMessage)messageConsumer1.receive(1000);
+ if (messageReceivedA == null)
+ {
+ break;
+ }
+
+ System.out.println("messageConsumer1 received " + messageReceivedA.getText() +
+ " someID = " +
+ messageReceivedA.getIntProperty("someID"));
+ }
+ for (;;)
+ {
+ TextMessage messageReceivedB = (TextMessage)messageConsumer2.receive(1000);
+ if (messageReceivedB == null)
+ {
+ break;
+ }
+
+ System.out.println("messageConsumer2 received " + messageReceivedB.getText() +
+ " someID = " +
+ messageReceivedB.getIntProperty("someID"));
+ }
+ for (;;)
+ {
+ TextMessage messageReceivedC = (TextMessage)messageConsumer3.receive(1000);
+ if (messageReceivedC == null)
+ {
+ break;
+ }
+ System.out.println("messageConsumer3 received " + messageReceivedC.getText() +
+ " someID = " +
+ messageReceivedC.getIntProperty("someID"));
+ }subscriberA.close();subscriberB.close();session.unsubscribe("sub-a1");session.unsubscribe("sub-a2");
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ JMS Topic Selector Example 2
+ +This example shows you how to selectively consume messages using message selectors with topic consumers.
+ +Message selectors are strings with special syntax that can be used in creating consumers. Message consumers + that are thus created only receive messages that match its selector. On message delivering, the HornetQ + Server evaluates the corresponding message headers of the messages against each selector, if any, and then delivers + the 'matched' messages to its consumer. Please consult the JMS 1.1 specification for full details.
+ +In this example, three message consumers are created on a topic. The first consumer is created with selector
+ 'color=red', it only receives messages that
+ have a 'color' string property of 'red' value; the second is created with selector 'color=green', it
+ only receives messages who have a 'color' string property of
+ 'green' value; and the third without a selector, which means it receives all messages. To illustrate, three messages
+ with different 'color' property values are created and sent.
Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Topic topic = (Topic) initialContext.lookup("/topic/exampleTopic");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ connection.start();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(topic);
+
+
+
+
+ String redSelector = "color='red'";
+ String greenSelector = "color='green'";
+
+
+
+
+
+ MessageConsumer redConsumer = session.createConsumer(topic, redSelector);
+ redConsumer.setMessageListener(new SimpleMessageListener("red"));
+
+
+
+
+
+ MessageConsumer greenConsumer = session.createConsumer(topic, greenSelector);
+ greenConsumer.setMessageListener(new SimpleMessageListener("green"));
+
+
+
+
+
+ MessageConsumer allConsumer = session.createConsumer(topic);
+ allConsumer.setMessageListener(new SimpleMessageListener("all"));
+
+
+
+
+
+ TextMessage redMessage = session.createTextMessage("Red");
+ redMessage.setStringProperty("color", "red");
+ TextMessage greenMessage = session.createTextMessage("Green");
+ greenMessage.setStringProperty("color", "green");
+ TextMessage blueMessage = session.createTextMessage("Blue");
+ blueMessage.setStringProperty("color", "blue");
+
+
+
+
+
+ producer.send(redMessage);
+ System.out.println("Message sent: " + redMessage.getText());
+ producer.send(greenMessage);
+ System.out.println("Message sent: " + greenMessage.getText());
+ producer.send(blueMessage);
+ System.out.println("Message sent: " + blueMessage.getText());
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+ JMS Topic Example
+ +This example shows you how to send and receive a message to a JMS Topic with HornetQ.
+Topics are a standard part of JMS, please consult the JMS 1.1 specification for full details.
+A Topic is used to send messages using the publish-subscribe model, from a producer to 1 or more consumers.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext();
+
+
+
+ Topic topic = (Topic) initialContext.lookup("/topic/exampleTopic");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+ MessageProducer messageProducer = session.createProducer(topic);
+
+
+
+ MessageConsumer messageConsumer = session.createConsumer(topic);
+
+
+
+ MessageConsumer messageConsumer2 = session.createConsumer(topic);
+
+
+
+ TextMessage message = session.createTextMessage("This is a text message");
+
+
+
+ messageProducer.send(message);
+
+
+
+ connection.start();
+
+
+
+ TextMessage messageReceived = (TextMessage) messageConsumer1.receive();
+
+
+
+ messageReceived = (TextMessage) messageConsumer2.receive();
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+
+
+ JMS Failover With Transaction Example
+ +This example demonstrates two servers coupled as a live-backup pair for high availability (HA), and a client + connection failing over from live to backup when the live server is crashed.
+Failover behavior differs whether the JMS session is transacter or not.
+When a transacted JMS session is used, once-and-only once delivery is guaranteed.
+-
+
HornetQ also provides an example for non-transaction failover.
+For more information on HornetQ failover and HA, and clustering in general, please see the clustering + section of the user manual.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
In this example, the live server is server 1, and the backup server is server 0
+The connection will initially be created to server1, server 1 will crash, and the client will carry on + seamlessly on server 0, the backup server.
+ +-
+
+ initialContext = getContext(1); ++ +
+ Queue queue = (Queue)initialContext.lookup("/queue/exampleQueue");
+ ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
+
+
+ + connection = connectionFactory.createConnection(); ++ +
+ Session session = connection.createSession(true, 0); ++ +
+ connection.start(); ++ +
+ MessageProducer producer = session.createProducer(queue); ++ +
+ MessageConsumer consumer = session.createConsumer(queue); ++ +
+ sendMessages(session, producer, numMessages, true); ++ +
When server #1 crashes, the client automatically detects the failure and automatically + fails over from server #1 to server #0 (in your real program you wouldn't need to sleep). +
+ +
+ try
+ {
+ session.commit();
+ } catch (TransactionRolledBackException e)
+ {
+ System.err.println("transaction has been rolled back: " + e.getMessage());
+ }
+
+
+ + sendMessages(session, producer, numMessages, false); ++ +
+ session.commit(); ++ + +
+ for (int i = 0; i < numMessages; i++)
+ {
+ TextMessage message0 = (TextMessage)consumer.receive(5000);
+ System.out.println("Got message: " + message0.getText());
+ }
+ session.commit();
+ System.out.println("Other message on the server? " + consumer.receive(5000));
+
+
+
+ finally
+ {
+ if (connection != null)
+ {
+ connection.close();
+ }
+
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ }
+
+
+ JMS Transactional Session Example
+ +This example shows you how to use a transacted Session with HornetQ.
+Firstly 2 messages are sent via the transacted sending session before being committed. This ensures that both message + are sent
+Secondly the receiving session receives the messages firstly demonstrating a message being redelivered after the session + being rolled back and then acknowledging receipt of the messages via the commit method.
+ + +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ initialContext = getContext();
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ ConnectionFactory cf = (ConnectionFactory) initialContext.lookup("/ConnectionFactory");
+
+
+
+ connection = cf.createConnection();
+
+
+
+ connection.start();
+
+
+
+ Session session = connection.createSession(true, Session.SESSION_TRANSACTED);
+
+
+
+ MessageProducer messageProducer = session.createProducer(queue);
+
+
+
+ MessageConsumer messageConsumer = session.createConsumer(queue);
+
+
+ ++ +TextMessage message1 = session.createTextMessage("This is a text message1");+TextMessage message2 = session.createTextMessage("This is a text message2");+
++ +messageProducer.send(message1);+messageProducer.send(message2);+
+ TextMessage receivedMessage = (TextMessage) messageConsumer.receive(5000);
+
+
+
+ session.commit();
+
+
+
+ receivedMessage = (TextMessage) messageConsumer.receive(5000);
+
+
+
+ session.rollback();
+
+
+ ++ +receivedMessage = (TextMessage) messageConsumer.receive(5000);+receivedMessage = (TextMessage) messageConsumer.receive(5000);+
+ session.commit();
+
+
+
+ receivedMessage = (TextMessage) messageConsumer.receive(5000);
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+
+ JMS XA Heuristic Example
+This example shows you how to make an XA heuristic decision through the HornetQ Management Interface.
+ +A heuristic decision is a unilateral decision to commit or rollback an XA transaction branch after it has + been prepared.
+ +In this example we simulate a transaction manager to control the transactions. First we create an XASession + and enlist it in a transaction through its XAResource. We then send a text message, 'hello' and end/prepare the transaction + on the XAResource, but neither commit nor roll back the transaction. Another transaction is created and + associated with the same XAResource, and a second message, 'world' is sent on behalf of the second transaction. Again we leave + the second transaction in prepare state. + Then we get the MBeanServerConnection object to manipulate the prepared transactions. To illustrate, we roll back the first + transaction but commit the second. This will result in that only the message 'world' is received.
+ +This example uses JMX to manipulate transactions in a HornetQ Server. For details on JMX facilities with HornetQ, + please look at the JMX Example.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext(0);
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ XAConnectionFactory cf = (XAConnectionFactory) initialContext.lookup("/XAConnectionFactory");
+
+
+
+ connection = cf.createXAConnection();
+
+
+
+ connection.start();
+
+
+
+ XASession xaSession = connection.createXASession();
+
+
+
+ Session normalSession = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+ MessageConsumer normalConsumer = normalSession.createConsumer(queue);
+ normalConsumer.setMessageListener(new SimpleMessageListener());
+
+
+
+
+ Session session = xaSession.getSession();
+
+
+
+ MessageProducer producer = session.createProducer(queue);
+
+
+
+
+ TextMessage helloMessage = session.createTextMessage("hello");
+ TextMessage worldMessage = session.createTextMessage("world");
+
+
+
+
+ Xid xid1 = new XidImpl("xa-example1".getBytes(), 1, UUIDGenerator.getInstance().generateStringUUID().getBytes());
+
+
+
+ XAResource xaRes = xaSession.getXAResource();
+
+
+
+ xaRes.start(xid1, XAResource.TMNOFLAGS);
+
+
+
+
+ normalProducer.send(helloMessage);
+
+
+
+
+ xaRes.end(xid1, XAResource.TMSUCCESS);
+
+
+
+ xaRes.prepare(xid1);
+
+
+
+ checkNoMessageReceived();
+
+
+
+ Xid xid2 = new XidImpl("xa-example2".getBytes(), 1, UUIDGenerator.getInstance().generateStringUUID().getBytes());
+
+
+
+ xaRes.start(xid2, XAResource.TMNOFLAGS);
+
+
+
+ producer.send(worldMessage);
+
+
+
+ xaRes.end(xid2, XAResource.TMSUCCESS);
+
+
+
+ xaRes.prepare(xid2);
+
+
+
+ checkNoMessageReceived();
+
+
+
+
+ JMXConnector connector = JMXConnectorFactory.connect(new JMXServiceURL(JMX_URL), new HashMap());
+
+
+
+
+ MBeanServerConnection mbsc = connector.getMBeanServerConnection();
+
+
+
+
+ ObjectName serverObject = ObjectNameBuilder.DEFAULT.getMessagingServerObjectName();
+ String[] infos = (String[])mbsc.invoke(serverObject, "listPreparedTransactions", null, null);
+
+ System.out.println("Prepared transactions: ");
+ for (String i : infos)
+ {
+ System.out.println(i);
+ }
+
+
+
+
+ mbsc.invoke(serverObject, "rollbackPreparedTransaction", new String[] {XidImpl.toBase64String(xid1)}, new String[]{"java.lang.String"});
+
+
+
+ mbsc.invoke(serverObject, "commitPreparedTransaction", new String[] {XidImpl.toBase64String(xid2)}, new String[]{"java.lang.String"});
+
+
+
+ checkMessageReceived("world");
+
+
+
+
+ infos = (String[])mbsc.invoke(serverObject, "listPreparedTransactions", null, null);
+ System.out.println("No. of prepared transactions now: " + infos.length);
+
+
+
+
+ connector.close();
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ JMS XA Receive Example
+This example demonstrates receiving a message within the scope of an XA transaction. When using an XA transaction + the message will only be acknowledged and removed from the queue when the transaction is committed. + If the transaction is not committed the message maybe redelivered after rollback or during XA recovery.
+ +HornetQ is JTA aware, meaning you can use HornetQ in an XA transactional environment + and participate in XA transactions. It provides the javax.transaction.xa.XAResource interface for that + purpose. Users can get a XAConnectionFactory to create XAConnections and XASessions.
+ +In this example we simulate a transaction manager to control the transactions. First we create an XASession + for receiving and a normal session for sending. Then we start a new xa transaction and enlist the receiving + XASession through its XAResource. We then send two words, 'hello' and 'world', receive them, and let the + transaction roll back. The received messages are cancelled back to the queue. Next we start + a new transaction with the same XAResource enlisted, but this time we commit the transaction after receiving the + messages. Then we check that no more messages are to be received.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext(0);
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ XAConnectionFactory cf = (XAConnectionFactory) initialContext.lookup("/XAConnectionFactory");
+
+
+
+ connection = cf.createXAConnection();
+
+
+
+ connection.start();
+
+
+
+ XASession xaSession = connection.createXASession();
+
+
+
+ Session normalSession = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+ MessageProducer normalProducer = normalSession.createProducer(queue);
+
+
+
+
+ Session session = xaSession.getSession();
+
+
+
+ MessageConsumer xaConsumer = session.createConsumer(queue);
+
+
+
+
+ TextMessage helloMessage = session.createTextMessage("hello");
+ TextMessage worldMessage = session.createTextMessage("world");
+
+
+
+
+ Xid xid1 = new XidImpl("xa-example1".getBytes(), 1, UUIDGenerator.getInstance().generateStringUUID().getBytes());
+
+
+
+ XAResource xaRes = xaSession.getXAResource();
+
+
+
+ xaRes.start(xid1, XAResource.TMNOFLAGS);
+
+
+
+
+ normalProducer.send(helloMessage);
+ normalProducer.send(worldMessage);
+
+
+
+
+
+ TextMessage rm1 = (TextMessage)xaConsumer.receive();
+ System.out.println("Message received: " + rm1.getText());
+ TextMessage rm2 = (TextMessage)xaConsumer.receive();
+ System.out.println("Message received: " + rm2.getText());
+
+
+
+
+ xaRes.end(xid1, XAResource.TMSUCCESS);
+
+
+
+ xaRes.prepare(xid1);
+
+
+
+ xaRes.rollback(xid1);
+
+
+
+ Xid xid2 = new XidImpl("xa-example2".getBytes(), 1, UUIDGenerator.getInstance().generateStringUUID().getBytes());
+
+
+
+ xaRes.start(xid2, XAResource.TMNOFLAGS);
+
+
+
+
+ rm1 = (TextMessage)xaConsumer.receive();
+ System.out.println("Message received again: " + rm1.getText());
+ rm2 = (TextMessage)xaConsumer.receive();
+ System.out.println("Message received again: " + rm2.getText());
+
+
+
+
+ xaRes.end(xid2, XAResource.TMSUCCESS);
+
+
+
+ xaRes.prepare(xid2);
+
+
+
+ xaRes.commit(xid2, false);
+
+
+
+
+ TextMessage rm3 = (TextMessage)xaConsumer.receive(2000);
+ if (rm3 == null)
+ {
+ System.out.println("No message received after commit.");
+ }
+ else
+ {
+ result = false;
+ }
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ JMS XA Send Example
+This example shows you how message sending behaves in an XA transaction in HornetQ. When a message is sent within + the scope of an XA transaction, it will only reach the queue once the transaction is committed. + If the transaction is rolled back the sent messages will be discarded by the server.
+ +HornetQ is JTA aware, meaning you can use HornetQ in a XA transactional environment + and participate in XA transactions. It provides the javax.transaction.xa.XAResource interface for that + purpose. Users can get a XAConnectionFactory to create XAConnections and XASessions.
+ +In this example we simulate a transaction manager to control the transactions. First we create an XASession + and enlist it in a transaction through its XAResource. We then send two words, 'hello' and 'world', with + the session, let the transaction roll back. The messages are discarded and never be received. Next we start + a new transaction with the same XAResource, but this time we commit the transaction. Both messages are received.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory
-
+
+ InitialContext initialContext = getContext(0);
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ XAConnectionFactory cf = (XAConnectionFactory) initialContext.lookup("/XAConnectionFactory");
+
+
+
+ connection = cf.createXAConnection();
+
+
+
+ connection.start();
+
+
+
+ XASession xaSession = connection.createXASession();
+
+
+
+ Session normalSession = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+ MessageConsumer normalConsumer = normalSession.createConsumer(queue);
+ normalConsumer.setMessageListener(new SimpleMessageListener());
+
+
+
+
+ Session session = xaSession.getSession();
+
+
+
+ MessageProducer producer = session.createProducer(queue);
+
+
+
+
+ TextMessage helloMessage = session.createTextMessage("hello");
+ TextMessage worldMessage = session.createTextMessage("world");
+
+
+
+
+ Xid xid1 = new XidImpl("xa-example1".getBytes(), 1, UUIDGenerator.getInstance().generateStringUUID().getBytes());
+
+
+
+ XAResource xaRes = xaSession.getXAResource();
+
+
+
+ xaRes.start(xid1, XAResource.TMNOFLAGS);
+
+
+
+
+ producer.send(helloMessage);
+ producer.send(worldMessage);
+
+
+
+
+ checkNoMessageReceived();
+
+
+
+ xaRes.end(xid1, XAResource.TMSUCCESS);
+
+
+
+ xaRes.prepare(xid1);
+
+
+
+ xaRes.rollback(xid1);
+
+
+
+ checkNoMessageReceived();
+
+
+
+ Xid xid2 = new XidImpl("xa-example2".getBytes(), 1, UUIDGenerator.getInstance().generateStringUUID().getBytes());
+
+
+
+ xaRes.start(xid2, XAResource.TMNOFLAGS);
+
+
+
+
+ producer.send(helloMessage);
+ producer.send(worldMessage);
+
+
+
+
+ xaRes.end(xid2, XAResource.TMSUCCESS);
+
+
+
+ xaRes.prepare(xid2);
+
+
+
+ checkNoMessageReceived();
+
+
+
+ xaRes.commit(xid2, false);
+
+
+
+ checkAllMessageReceived();
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ JMS XA with JTA Example
+ +This example shows you how to use JTA interfaces to control transactions with HornetQ. JTA provides + facilities to start and stop a transaction and enlist XA resources into a transaction.
+ +HornetQ is JTA aware, meaning you can use HornetQ in a XA transactional environment + and participate in XA transactions. It provides the javax.transaction.xa.XAResource interface for that + purpose. Users can get a XAConnectionFactory to create XAConnections and XASessions.
+ +In this example we get a transaction manager from JBoss JTA to control the transactions. First we create an XASession + for receiving and a normal session for sending. Then we start a new xa transaction and enlist the receiving + XASession through its XAResource. We then send two words, 'hello' and 'world', receive them, and let the + transaction roll back. The received messages are cancelled back to the queue. Next we start + a new transaction with the same XAResource enlisted, but this time we commit the transaction after receiving the + messages. Then we check that no more messages are to be received. In each transaction a dummy XAResource is also + enlisted to show the transaction processing information.
+ +Example step-by-step
+To run the example, simply type mvn verify from this directory. It will download the JBoss JTA jars before
+ it launches the example.
-
+
+ InitialContext initialContext = getContext(0);
+
+
+
+ Queue queue = (Queue) initialContext.lookup("/queue/exampleQueue");
+
+
+
+ XAConnectionFactory cf = (XAConnectionFactory) initialContext.lookup("/XAConnectionFactory");
+
+
+
+ connection = cf.createXAConnection();
+
+
+
+ connection.start();
+
+
+
+ XASession xaSession = connection.createXASession();
+
+
+
+ Session normalSession = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
+
+
+
+
+ MessageProducer normalProducer = normalSession.createProducer(queue);
+
+
+
+
+ Session session = xaSession.getSession();
+
+
+
+ MessageConsumer xaConsumer = session.createConsumer(queue);
+
+
+
+
+ TextMessage helloMessage = session.createTextMessage("hello");
+ TextMessage worldMessage = session.createTextMessage("world");
+
+
+
+
+ javax.transaction.TransactionManager txMgr = TransactionManager.transactionManager();
+
+
+
+ txMgr.begin();
+
+
+
+ XAResource xaRes = xaSession.getXAResource();
+
+
+
+
+ Transaction transaction = txMgr.getTransaction();
+ transaction.enlistResource(new DummyXAResource());
+ transaction.enlistResource(xaRes);
+
+
+
+
+
+ normalProducer.send(helloMessage);
+ normalProducer.send(worldMessage);
+
+
+
+
+
+ TextMessage rm1 = (TextMessage)xaConsumer.receive();
+ System.out.println("Message received: " + rm1.getText());
+ TextMessage rm2 = (TextMessage)xaConsumer.receive();
+ System.out.println("Message received: " + rm2.getText());
+
+
+
+
+ txMgr.rollback();
+
+
+
+
+ txMgr.begin();
+ transaction = txMgr.getTransaction();
+
+
+
+
+
+ transaction.enlistResource(new DummyXAResource());
+ transaction.enlistResource(xaRes);
+
+
+
+
+
+ rm1 = (TextMessage)xaConsumer.receive();
+ System.out.println("Message received again: " + rm1.getText());
+ rm2 = (TextMessage)xaConsumer.receive();
+ System.out.println("Message received again: " + rm2.getText());
+
+
+
+
+ txMgr.commit();
+
+
+
+
+ TextMessage rm3 = (TextMessage)xaConsumer.receive(2000);
+ if (rm3 == null)
+ {
+ System.out.println("No message received after commit.");
+ }
+ else
+ {
+ result = false;
+ }
+
+
+
+
+ finally
+ {
+ if (initialContext != null)
+ {
+ initialContext.close();
+ }
+ if (connection != null)
+ {
+ connection.close();
+ }
+ }
+
+ + * Instances of it can be obtained from {@link HornetQBuffers} factory. + *
+ * Much of it derived from Netty ChannelBuffer by Trustin Lee + * @author Tim Fox + * @see HornetQBuffers + */ +public interface HornetQBuffer +{ + /** + * Returns the underlying Netty's ByteBuf + * + * @return the underlying Netty's ByteBuf + */ + ByteBuf byteBuf(); + + /** + * Returns the number of bytes this buffer can contain. + */ + int capacity(); + + /** + * Returns the {@code readerIndex} of this buffer. + */ + int readerIndex(); + + /** + * Sets the {@code readerIndex} of this buffer. + * + * @throws IndexOutOfBoundsException + * if the specified {@code readerIndex} is + * less than {@code 0} or + * greater than {@code this.writerIndex} + */ + void readerIndex(int readerIndex); + + /** + * Returns the {@code writerIndex} of this buffer. + */ + int writerIndex(); + + /** + * Sets the {@code writerIndex} of this buffer. + * + * @throws IndexOutOfBoundsException + * if the specified {@code writerIndex} is + * less than {@code this.readerIndex} or + * greater than {@code this.capacity} + */ + void writerIndex(int writerIndex); + + /** + * Sets the {@code readerIndex} and {@code writerIndex} of this buffer + * in one shot. This method is useful when you have to worry about the + * invocation order of {@link #readerIndex(int)} and {@link #writerIndex(int)} + * methods. For example, the following code will fail: + * + *
+ * // Create a buffer whose readerIndex, writerIndex and capacity are + * // 0, 0 and 8 respectively. + * ChannelBuffer buf = ChannelBuffers.buffer(8); + * + * // IndexOutOfBoundsException is thrown because the specified + * // readerIndex (2) cannot be greater than the current writerIndex (0). + * buf.readerIndex(2); + * buf.writerIndex(4); + *+ * + * The following code will also fail: + * + *
+ * // Create a buffer whose readerIndex, writerIndex and capacity are + * // 0, 8 and 8 respectively. + * ChannelBuffer buf = ChannelBuffers.wrappedBuffer(new byte[8]); + * + * // readerIndex becomes 8. + * buf.readLong(); + * + * // IndexOutOfBoundsException is thrown because the specified + * // writerIndex (4) cannot be less than the current readerIndex (8). + * buf.writerIndex(4); + * buf.readerIndex(2); + *+ * + * By contrast, {@link #setIndex(int, int)} guarantees that it never + * throws an {@link IndexOutOfBoundsException} as long as the specified + * indexes meet basic constraints, regardless what the current index + * values of the buffer are: + * + *
+ * // No matter what the current state of the buffer is, the following + * // call always succeeds as long as the capacity of the buffer is not + * // less than 4. + * buf.setIndex(2, 4); + *+ * + * @throws IndexOutOfBoundsException + * if the specified {@code readerIndex} is less than 0, + * if the specified {@code writerIndex} is less than the specified + * {@code readerIndex} or if the specified {@code writerIndex} is + * greater than {@code this.capacity} + */ + void setIndex(int readerIndex, int writerIndex); + + /** + * Returns the number of readable bytes which is equal to + * {@code (this.writerIndex - this.readerIndex)}. + */ + int readableBytes(); + + /** + * Returns the number of writable bytes which is equal to + * {@code (this.capacity - this.writerIndex)}. + */ + int writableBytes(); + + /** + * Returns {@code true} + * if and only if {@code (this.writerIndex - this.readerIndex)} is greater + * than {@code 0}. + */ + boolean readable(); + + /** + * Returns {@code true} + * if and only if {@code (this.capacity - this.writerIndex)} is greater + * than {@code 0}. + */ + boolean writable(); + + /** + * Sets the {@code readerIndex} and {@code writerIndex} of this buffer to + * {@code 0}. + * This method is identical to {@link #setIndex(int, int) setIndex(0, 0)}. + *
+ * Please note that the behavior of this method is different + * from that of NIO buffer, which sets the {@code limit} to + * the {@code capacity} of the buffer. + */ + void clear(); + + /** + * Marks the current {@code readerIndex} in this buffer. You can + * reposition the current {@code readerIndex} to the marked + * {@code readerIndex} by calling {@link #resetReaderIndex()}. + * The initial value of the marked {@code readerIndex} is {@code 0}. + */ + void markReaderIndex(); + + /** + * Repositions the current {@code readerIndex} to the marked + * {@code readerIndex} in this buffer. + * + * @throws IndexOutOfBoundsException + * if the current {@code writerIndex} is less than the marked + * {@code readerIndex} + */ + void resetReaderIndex(); + + /** + * Marks the current {@code writerIndex} in this buffer. You can + * reposition the current {@code writerIndex} to the marked + * {@code writerIndex} by calling {@link #resetWriterIndex()}. + * The initial value of the marked {@code writerIndex} is {@code 0}. + */ + void markWriterIndex(); + + /** + * Repositions the current {@code writerIndex} to the marked + * {@code writerIndex} in this buffer. + * + * @throws IndexOutOfBoundsException + * if the current {@code readerIndex} is greater than the marked + * {@code writerIndex} + */ + void resetWriterIndex(); + + /** + * Discards the bytes between the 0th index and {@code readerIndex}. + * It moves the bytes between {@code readerIndex} and {@code writerIndex} + * to the 0th index, and sets {@code readerIndex} and {@code writerIndex} + * to {@code 0} and {@code oldWriterIndex - oldReaderIndex} respectively. + *
+ * Please refer to the class documentation for more detailed explanation.
+ */
+ void discardReadBytes();
+
+ /**
+ * Gets a byte at the specified absolute {@code index} in this buffer.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 1} is greater than {@code this.capacity}
+ */
+ byte getByte(int index);
+
+ /**
+ * Gets an unsigned byte at the specified absolute {@code index} in this
+ * buffer. This method does not modify {@code readerIndex} or
+ * {@code writerIndex} of this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 1} is greater than {@code this.capacity}
+ */
+ short getUnsignedByte(int index);
+
+ /**
+ * Gets a 16-bit short integer at the specified absolute {@code index} in
+ * this buffer. This method does not modify {@code readerIndex} or
+ * {@code writerIndex} of this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 2} is greater than {@code this.capacity}
+ */
+ short getShort(int index);
+
+ /**
+ * Gets an unsigned 16-bit short integer at the specified absolute
+ * {@code index} in this buffer. This method does not modify
+ * {@code readerIndex} or {@code writerIndex} of this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 2} is greater than {@code this.capacity}
+ */
+ int getUnsignedShort(int index);
+
+ /**
+ * Gets a 32-bit integer at the specified absolute {@code index} in
+ * this buffer. This method does not modify {@code readerIndex} or
+ * {@code writerIndex} of this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 4} is greater than {@code this.capacity}
+ */
+ int getInt(int index);
+
+ /**
+ * Gets an unsigned 32-bit integer at the specified absolute {@code index}
+ * in this buffer. This method does not modify {@code readerIndex} or
+ * {@code writerIndex} of this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 4} is greater than {@code this.capacity}
+ */
+ long getUnsignedInt(int index);
+
+ /**
+ * Gets a 64-bit long integer at the specified absolute {@code index} in
+ * this buffer. This method does not modify {@code readerIndex} or
+ * {@code writerIndex} of this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 8} is greater than {@code this.capacity}
+ */
+ long getLong(int index);
+
+ /**
+ * Transfers this buffer's data to the specified destination starting at
+ * the specified absolute {@code index} until the destination becomes
+ * non-writable. This method is basically same with
+ * {@link #getBytes(int, HornetQBuffer, int, int)}, except that this
+ * method increases the {@code writerIndex} of the destination by the
+ * number of the transferred bytes while
+ * {@link #getBytes(int, HornetQBuffer, int, int)} does not.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * the source buffer (i.e. {@code this}).
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * if {@code index + dst.writableBytes} is greater than
+ * {@code this.capacity}
+ */
+ void getBytes(int index, HornetQBuffer dst);
+
+ /**
+ * Transfers this buffer's data to the specified destination starting at
+ * the specified absolute {@code index}. This method is basically same
+ * with {@link #getBytes(int, HornetQBuffer, int, int)}, except that this
+ * method increases the {@code writerIndex} of the destination by the
+ * number of the transferred bytes while
+ * {@link #getBytes(int, HornetQBuffer, int, int)} does not.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * the source buffer (i.e. {@code this}).
+ *
+ * @param length the number of bytes to transfer
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0},
+ * if {@code index + length} is greater than
+ * {@code this.capacity}, or
+ * if {@code length} is greater than {@code dst.writableBytes}
+ */
+ void getBytes(int index, HornetQBuffer dst, int length);
+
+ /**
+ * Transfers this buffer's data to the specified destination starting at
+ * the specified absolute {@code index}.
+ * This method does not modify {@code readerIndex} or {@code writerIndex}
+ * of both the source (i.e. {@code this}) and the destination.
+ *
+ * @param dstIndex the first index of the destination
+ * @param length the number of bytes to transfer
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0},
+ * if the specified {@code dstIndex} is less than {@code 0},
+ * if {@code index + length} is greater than
+ * {@code this.capacity}, or
+ * if {@code dstIndex + length} is greater than
+ * {@code dst.capacity}
+ */
+ void getBytes(int index, HornetQBuffer dst, int dstIndex, int length);
+
+ /**
+ * Transfers this buffer's data to the specified destination starting at
+ * the specified absolute {@code index}.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * if {@code index + dst.length} is greater than
+ * {@code this.capacity}
+ */
+ void getBytes(int index, byte[] dst);
+
+ /**
+ * Transfers this buffer's data to the specified destination starting at
+ * the specified absolute {@code index}.
+ * This method does not modify {@code readerIndex} or {@code writerIndex}
+ * of this buffer.
+ *
+ * @param dstIndex the first index of the destination
+ * @param length the number of bytes to transfer
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0},
+ * if the specified {@code dstIndex} is less than {@code 0},
+ * if {@code index + length} is greater than
+ * {@code this.capacity}, or
+ * if {@code dstIndex + length} is greater than
+ * {@code dst.length}
+ */
+ void getBytes(int index, byte[] dst, int dstIndex, int length);
+
+ /**
+ * Transfers this buffer's data to the specified destination starting at
+ * the specified absolute {@code index} until the destination's position
+ * reaches its limit.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer while the destination's {@code position} will be increased.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * if {@code index + dst.remaining()} is greater than
+ * {@code this.capacity}
+ */
+ void getBytes(int index, ByteBuffer dst);
+
+ /**
+ * Gets a char at the specified absolute {@code index} in
+ * this buffer. This method does not modify {@code readerIndex} or
+ * {@code writerIndex} of this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 2} is greater than {@code this.capacity}
+ */
+ char getChar(int index);
+
+ /**
+ * Gets a float at the specified absolute {@code index} in
+ * this buffer. This method does not modify {@code readerIndex} or
+ * {@code writerIndex} of this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 4} is greater than {@code this.capacity}
+ */
+ float getFloat(int index);
+
+ /**
+ * Gets a double at the specified absolute {@code index} in
+ * this buffer. This method does not modify {@code readerIndex} or
+ * {@code writerIndex} of this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 8} is greater than {@code this.capacity}
+ */
+ double getDouble(int index);
+
+ /**
+ * Sets the specified byte at the specified absolute {@code index} in this
+ * buffer.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 1} is greater than {@code this.capacity}
+ */
+ void setByte(int index, byte value);
+
+ /**
+ * Sets the specified 16-bit short integer at the specified absolute
+ * {@code index} in this buffer.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 2} is greater than {@code this.capacity}
+ */
+ void setShort(int index, short value);
+
+ /**
+ * Sets the specified 32-bit integer at the specified absolute
+ * {@code index} in this buffer.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 4} is greater than {@code this.capacity}
+ */
+ void setInt(int index, int value);
+
+ /**
+ * Sets the specified 64-bit long integer at the specified absolute
+ * {@code index} in this buffer.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 8} is greater than {@code this.capacity}
+ */
+ void setLong(int index, long value);
+
+ /**
+ * Transfers the specified source buffer's data to this buffer starting at
+ * the specified absolute {@code index} until the destination becomes
+ * unreadable. This method is basically same with
+ * {@link #setBytes(int, HornetQBuffer, int, int)}, except that this
+ * method increases the {@code readerIndex} of the source buffer by
+ * the number of the transferred bytes while
+ * {@link #getBytes(int, HornetQBuffer, int, int)} does not.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * the source buffer (i.e. {@code this}).
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * if {@code index + src.readableBytes} is greater than
+ * {@code this.capacity}
+ */
+ void setBytes(int index, HornetQBuffer src);
+
+ /**
+ * Transfers the specified source buffer's data to this buffer starting at
+ * the specified absolute {@code index}. This method is basically same
+ * with {@link #setBytes(int, HornetQBuffer, int, int)}, except that this
+ * method increases the {@code readerIndex} of the source buffer by
+ * the number of the transferred bytes while
+ * {@link #getBytes(int, HornetQBuffer, int, int)} does not.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * the source buffer (i.e. {@code this}).
+ *
+ * @param length the number of bytes to transfer
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0},
+ * if {@code index + length} is greater than
+ * {@code this.capacity}, or
+ * if {@code length} is greater than {@code src.readableBytes}
+ */
+ void setBytes(int index, HornetQBuffer src, int length);
+
+ /**
+ * Transfers the specified source buffer's data to this buffer starting at
+ * the specified absolute {@code index}.
+ * This method does not modify {@code readerIndex} or {@code writerIndex}
+ * of both the source (i.e. {@code this}) and the destination.
+ *
+ * @param srcIndex the first index of the source
+ * @param length the number of bytes to transfer
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0},
+ * if the specified {@code srcIndex} is less than {@code 0},
+ * if {@code index + length} is greater than
+ * {@code this.capacity}, or
+ * if {@code srcIndex + length} is greater than
+ * {@code src.capacity}
+ */
+ void setBytes(int index, HornetQBuffer src, int srcIndex, int length);
+
+ /**
+ * Transfers the specified source array's data to this buffer starting at
+ * the specified absolute {@code index}.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * if {@code index + src.length} is greater than
+ * {@code this.capacity}
+ */
+ void setBytes(int index, byte[] src);
+
+ /**
+ * Transfers the specified source array's data to this buffer starting at
+ * the specified absolute {@code index}.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0},
+ * if the specified {@code srcIndex} is less than {@code 0},
+ * if {@code index + length} is greater than
+ * {@code this.capacity}, or
+ * if {@code srcIndex + length} is greater than {@code src.length}
+ */
+ void setBytes(int index, byte[] src, int srcIndex, int length);
+
+ /**
+ * Transfers the specified source buffer's data to this buffer starting at
+ * the specified absolute {@code index} until the source buffer's position
+ * reaches its limit.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * if {@code index + src.remaining()} is greater than
+ * {@code this.capacity}
+ */
+ void setBytes(int index, ByteBuffer src);
+
+ /**
+ * Sets the specified char at the specified absolute
+ * {@code index} in this buffer.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 2} is greater than {@code this.capacity}
+ */
+ void setChar(int index, char value);
+
+ /**
+ * Sets the specified float at the specified absolute
+ * {@code index} in this buffer.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 4} is greater than {@code this.capacity}
+ */
+ void setFloat(int index, float value);
+
+ /**
+ * Sets the specified double at the specified absolute
+ * {@code index} in this buffer.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code index} is less than {@code 0} or
+ * {@code index + 8} is greater than {@code this.capacity}
+ */
+ void setDouble(int index, double value);
+
+ /**
+ * Gets a byte at the current {@code readerIndex} and increases
+ * the {@code readerIndex} by {@code 1} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.readableBytes} is less than {@code 1}
+ */
+ byte readByte();
+
+ /**
+ * Gets an unsigned byte at the current {@code readerIndex} and increases
+ * the {@code readerIndex} by {@code 1} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.readableBytes} is less than {@code 1}
+ */
+ short readUnsignedByte();
+
+ /**
+ * Gets a 16-bit short integer at the current {@code readerIndex}
+ * and increases the {@code readerIndex} by {@code 2} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.readableBytes} is less than {@code 2}
+ */
+ short readShort();
+
+ /**
+ * Gets an unsigned 16-bit short integer at the current {@code readerIndex}
+ * and increases the {@code readerIndex} by {@code 2} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.readableBytes} is less than {@code 2}
+ */
+ int readUnsignedShort();
+
+ /**
+ * Gets a 32-bit integer at the current {@code readerIndex}
+ * and increases the {@code readerIndex} by {@code 4} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.readableBytes} is less than {@code 4}
+ */
+ int readInt();
+
+ /**
+ * Gets an unsigned 32-bit integer at the current {@code readerIndex}
+ * and increases the {@code readerIndex} by {@code 4} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.readableBytes} is less than {@code 4}
+ */
+ long readUnsignedInt();
+
+ /**
+ * Gets a 64-bit integer at the current {@code readerIndex}
+ * and increases the {@code readerIndex} by {@code 8} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.readableBytes} is less than {@code 8}
+ */
+ long readLong();
+
+ /**
+ * Gets a char at the current {@code readerIndex}
+ * and increases the {@code readerIndex} by {@code 2} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.readableBytes} is less than {@code 2}
+ */
+ char readChar();
+
+ /**
+ * Gets a float at the current {@code readerIndex}
+ * and increases the {@code readerIndex} by {@code 4} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.readableBytes} is less than {@code 4}
+ */
+ float readFloat();
+
+ /**
+ * Gets a double at the current {@code readerIndex}
+ * and increases the {@code readerIndex} by {@code 8} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.readableBytes} is less than {@code 8}
+ */
+ double readDouble();
+
+ /**
+ * Gets a boolean at the current {@code readerIndex}
+ * and increases the {@code readerIndex} by {@code 1} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.readableBytes} is less than {@code 1}
+ */
+ boolean readBoolean();
+
+ /**
+ * Gets a SimpleString (potentially {@code null}) at the current {@code readerIndex}
+ */
+ SimpleString readNullableSimpleString();
+
+ /**
+ * Gets a String (potentially {@code null}) at the current {@code readerIndex}
+ */
+ String readNullableString();
+
+ /**
+ * Gets a non-null SimpleString at the current {@code readerIndex}
+ */
+ SimpleString readSimpleString();
+
+ /**
+ * Gets a non-null String at the current {@code readerIndex}
+ */
+ String readString();
+
+ /**
+ * Gets a UTF-8 String at the current {@code readerIndex}
+ */
+ String readUTF();
+
+ /**
+ * Transfers this buffer's data to a newly created buffer starting at
+ * the current {@code readerIndex} and increases the {@code readerIndex}
+ * by the number of the transferred bytes (= {@code length}).
+ * The returned buffer's {@code readerIndex} and {@code writerIndex} are
+ * {@code 0} and {@code length} respectively.
+ *
+ * @param length the number of bytes to transfer
+ *
+ * @return the newly created buffer which contains the transferred bytes
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code length} is greater than {@code this.readableBytes}
+ */
+ HornetQBuffer readBytes(int length);
+
+ /**
+ * Returns a new slice of this buffer's sub-region starting at the current
+ * {@code readerIndex} and increases the {@code readerIndex} by the size
+ * of the new slice (= {@code length}).
+ *
+ * @param length the size of the new slice
+ *
+ * @return the newly created slice
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code length} is greater than {@code this.readableBytes}
+ */
+ HornetQBuffer readSlice(int length);
+
+ /**
+ * Transfers this buffer's data to the specified destination starting at
+ * the current {@code readerIndex} until the destination becomes
+ * non-writable, and increases the {@code readerIndex} by the number of the
+ * transferred bytes. This method is basically same with
+ * {@link #readBytes(HornetQBuffer, int, int)}, except that this method
+ * increases the {@code writerIndex} of the destination by the number of
+ * the transferred bytes while {@link #readBytes(HornetQBuffer, int, int)}
+ * does not.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code dst.writableBytes} is greater than
+ * {@code this.readableBytes}
+ */
+ void readBytes(HornetQBuffer dst);
+
+ /**
+ * Transfers this buffer's data to the specified destination starting at
+ * the current {@code readerIndex} and increases the {@code readerIndex}
+ * by the number of the transferred bytes (= {@code length}). This method
+ * is basically same with {@link #readBytes(HornetQBuffer, int, int)},
+ * except that this method increases the {@code writerIndex} of the
+ * destination by the number of the transferred bytes (= {@code length})
+ * while {@link #readBytes(HornetQBuffer, int, int)} does not.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code length} is greater than {@code this.readableBytes} or
+ * if {@code length} is greater than {@code dst.writableBytes}
+ */
+ void readBytes(HornetQBuffer dst, int length);
+
+ /**
+ * Transfers this buffer's data to the specified destination starting at
+ * the current {@code readerIndex} and increases the {@code readerIndex}
+ * by the number of the transferred bytes (= {@code length}).
+ *
+ * @param dstIndex the first index of the destination
+ * @param length the number of bytes to transfer
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code dstIndex} is less than {@code 0},
+ * if {@code length} is greater than {@code this.readableBytes}, or
+ * if {@code dstIndex + length} is greater than
+ * {@code dst.capacity}
+ */
+ void readBytes(HornetQBuffer dst, int dstIndex, int length);
+
+ /**
+ * Transfers this buffer's data to the specified destination starting at
+ * the current {@code readerIndex} and increases the {@code readerIndex}
+ * by the number of the transferred bytes (= {@code dst.length}).
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code dst.length} is greater than {@code this.readableBytes}
+ */
+ void readBytes(byte[] dst);
+
+ /**
+ * Transfers this buffer's data to the specified destination starting at
+ * the current {@code readerIndex} and increases the {@code readerIndex}
+ * by the number of the transferred bytes (= {@code length}).
+ *
+ * @param dstIndex the first index of the destination
+ * @param length the number of bytes to transfer
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code dstIndex} is less than {@code 0},
+ * if {@code length} is greater than {@code this.readableBytes}, or
+ * if {@code dstIndex + length} is greater than {@code dst.length}
+ */
+ void readBytes(byte[] dst, int dstIndex, int length);
+
+ /**
+ * Transfers this buffer's data to the specified destination starting at
+ * the current {@code readerIndex} until the destination's position
+ * reaches its limit, and increases the {@code readerIndex} by the
+ * number of the transferred bytes.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code dst.remaining()} is greater than
+ * {@code this.readableBytes}
+ */
+ void readBytes(ByteBuffer dst);
+
+ /**
+ * Increases the current {@code readerIndex} by the specified
+ * {@code length} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code length} is greater than {@code this.readableBytes}
+ */
+ void skipBytes(int length);
+
+ /**
+ * Sets the specified byte at the current {@code writerIndex}
+ * and increases the {@code writerIndex} by {@code 1} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.writableBytes} is less than {@code 1}
+ */
+ void writeByte(byte value);
+
+ /**
+ * Sets the specified 16-bit short integer at the current
+ * {@code writerIndex} and increases the {@code writerIndex} by {@code 2}
+ * in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.writableBytes} is less than {@code 2}
+ */
+ void writeShort(short value);
+
+ /**
+ * Sets the specified 32-bit integer at the current {@code writerIndex}
+ * and increases the {@code writerIndex} by {@code 4} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.writableBytes} is less than {@code 4}
+ */
+ void writeInt(int value);
+
+ /**
+ * Sets the specified 64-bit long integer at the current
+ * {@code writerIndex} and increases the {@code writerIndex} by {@code 8}
+ * in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.writableBytes} is less than {@code 8}
+ */
+ void writeLong(long value);
+
+ /**
+ * Sets the specified char at the current {@code writerIndex}
+ * and increases the {@code writerIndex} by {@code 2} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.writableBytes} is less than {@code 2}
+ */
+ void writeChar(char chr);
+
+ /**
+ * Sets the specified float at the current {@code writerIndex}
+ * and increases the {@code writerIndex} by {@code 4} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.writableBytes} is less than {@code 4}
+ */
+ void writeFloat(float value);
+
+ /**
+ * Sets the specified double at the current {@code writerIndex}
+ * and increases the {@code writerIndex} by {@code 8} in this buffer.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code this.writableBytes} is less than {@code 8}
+ */
+ void writeDouble(double value);
+
+ /**
+ * Sets the specified boolean at the current {@code writerIndex}
+ */
+ void writeBoolean(boolean val);
+
+ /**
+ * Sets the specified SimpleString (potentially {@code null}) at the current {@code writerIndex}
+ */
+ void writeNullableSimpleString(SimpleString val);
+
+ /**
+ * Sets the specified String (potentially {@code null}) at the current {@code writerIndex}
+ */
+ void writeNullableString(String val);
+
+ /**
+ * Sets the specified non-null SimpleString at the current {@code writerIndex}
+ */
+ void writeSimpleString(SimpleString val);
+
+ /**
+ * Sets the specified non-null String at the current {@code writerIndex}
+ */
+ void writeString(String val);
+
+ /**
+ * Sets the specified UTF-8 String at the current {@code writerIndex}
+ */
+
+ void writeUTF(String utf);
+
+ /**
+ * Transfers the specified source buffer's data to this buffer starting at
+ * the current {@code writerIndex} and increases the {@code writerIndex}
+ * by the number of the transferred bytes (= {@code length}). This method
+ * is basically same with {@link #writeBytes(HornetQBuffer, int, int)},
+ * except that this method increases the {@code readerIndex} of the source
+ * buffer by the number of the transferred bytes (= {@code length}) while
+ * {@link #writeBytes(HornetQBuffer, int, int)} does not.
+ *
+ * @param length the number of bytes to transfer
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code length} is greater than {@code this.writableBytes} or
+ * if {@code length} is greater then {@code src.readableBytes}
+ */
+ void writeBytes(HornetQBuffer src, int length);
+
+ /**
+ * Transfers the specified source buffer's data to this buffer starting at
+ * the current {@code writerIndex} and increases the {@code writerIndex}
+ * by the number of the transferred bytes (= {@code length}).
+ *
+ * @param srcIndex the first index of the source
+ * @param length the number of bytes to transfer
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code srcIndex} is less than {@code 0},
+ * if {@code srcIndex + length} is greater than
+ * {@code src.capacity}, or
+ * if {@code length} is greater than {@code this.writableBytes}
+ */
+ void writeBytes(HornetQBuffer src, int srcIndex, int length);
+
+ /**
+ * Transfers the specified source array's data to this buffer starting at
+ * the current {@code writerIndex} and increases the {@code writerIndex}
+ * by the number of the transferred bytes (= {@code src.length}).
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code src.length} is greater than {@code this.writableBytes}
+ */
+ void writeBytes(byte[] src);
+
+ /**
+ * Transfers the specified source array's data to this buffer starting at
+ * the current {@code writerIndex} and increases the {@code writerIndex}
+ * by the number of the transferred bytes (= {@code length}).
+ *
+ * @param srcIndex the first index of the source
+ * @param length the number of bytes to transfer
+ *
+ * @throws IndexOutOfBoundsException
+ * if the specified {@code srcIndex} is less than {@code 0},
+ * if {@code srcIndex + length} is greater than
+ * {@code src.length}, or
+ * if {@code length} is greater than {@code this.writableBytes}
+ */
+ void writeBytes(byte[] src, int srcIndex, int length);
+
+ /**
+ * Transfers the specified source buffer's data to this buffer starting at
+ * the current {@code writerIndex} until the source buffer's position
+ * reaches its limit, and increases the {@code writerIndex} by the
+ * number of the transferred bytes.
+ *
+ * @throws IndexOutOfBoundsException
+ * if {@code src.remaining()} is greater than
+ * {@code this.writableBytes}
+ */
+ void writeBytes(ByteBuffer src);
+
+ /**
+ * Returns a copy of this buffer's readable bytes. Modifying the content
+ * of the returned buffer or this buffer does not affect each other at all.
+ * This method is identical to {@code buf.copy(buf.readerIndex(), buf.readableBytes())}.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ *
+ */
+ HornetQBuffer copy();
+
+ /**
+ * Returns a copy of this buffer's sub-region. Modifying the content of
+ * the returned buffer or this buffer does not affect each other at all.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ */
+ HornetQBuffer copy(int index, int length);
+
+ /**
+ * Returns a slice of this buffer's readable bytes. Modifying the content
+ * of the returned buffer or this buffer affects each other's content
+ * while they maintain separate indexes and marks. This method is
+ * identical to {@code buf.slice(buf.readerIndex(), buf.readableBytes())}.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ */
+ HornetQBuffer slice();
+
+ /**
+ * Returns a slice of this buffer's sub-region. Modifying the content of
+ * the returned buffer or this buffer affects each other's content while
+ * they maintain separate indexes and marks.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ */
+ HornetQBuffer slice(int index, int length);
+
+ /**
+ * Returns a buffer which shares the whole region of this buffer.
+ * Modifying the content of the returned buffer or this buffer affects
+ * each other's content while they maintain separate indexes and marks.
+ * This method is identical to {@code buf.slice(0, buf.capacity())}.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ */
+ HornetQBuffer duplicate();
+
+ /**
+ * Converts this buffer's readable bytes into a NIO buffer. The returned
+ * buffer might or might not share the content with this buffer, while
+ * they have separate indexes and marks. This method is identical to
+ * {@code buf.toByteBuffer(buf.readerIndex(), buf.readableBytes())}.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ */
+ ByteBuffer toByteBuffer();
+
+ /**
+ * Converts this buffer's sub-region into a NIO buffer. The returned
+ * buffer might or might not share the content with this buffer, while
+ * they have separate indexes and marks.
+ * This method does not modify {@code readerIndex} or {@code writerIndex} of
+ * this buffer.
+ */
+ ByteBuffer toByteBuffer(int index, int length);
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQBuffers.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQBuffers.java
new file mode 100644
index 0000000000..2f63d261df
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQBuffers.java
@@ -0,0 +1,96 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import java.nio.ByteBuffer;
+
+import io.netty.buffer.Unpooled;
+import org.hornetq.core.buffers.impl.ChannelBufferWrapper;
+
+/**
+ * Factory class to create instances of {@link HornetQBuffer}.
+ * @author Tim Fox
+ */
+public final class HornetQBuffers
+{
+ /**
+ * Creates a self-expanding HornetQBuffer with the given initial size
+ *
+ * @param size the initial size of the created HornetQBuffer
+ * @return a self-expanding HornetQBuffer starting with the given size
+ */
+ public static HornetQBuffer dynamicBuffer(final int size)
+ {
+ return new ChannelBufferWrapper(Unpooled.buffer(size));
+ }
+
+ /**
+ * Creates a self-expanding HornetQBuffer filled with the given byte array
+ *
+ * @param bytes the created buffer will be initially filled with this byte array
+ * @return a self-expanding HornetQBuffer filled with the given byte array
+ */
+ public static HornetQBuffer dynamicBuffer(final byte[] bytes)
+ {
+ HornetQBuffer buff = dynamicBuffer(bytes.length);
+
+ buff.writeBytes(bytes);
+
+ return buff;
+ }
+
+ /**
+ * Creates a HornetQBuffer wrapping an underlying NIO ByteBuffer
+ *
+ * The position on this buffer won't affect the position on the inner buffer
+ *
+ * @param underlying the underlying NIO ByteBuffer
+ * @return a HornetQBuffer wrapping the underlying NIO ByteBuffer
+ */
+ public static HornetQBuffer wrappedBuffer(final ByteBuffer underlying)
+ {
+ HornetQBuffer buff = new ChannelBufferWrapper(Unpooled.wrappedBuffer(underlying));
+
+ buff.clear();
+
+ return buff;
+ }
+
+ /**
+ * Creates a HornetQBuffer wrapping an underlying byte array
+ *
+ * @param underlying the underlying byte array
+ * @return a HornetQBuffer wrapping the underlying byte array
+ */
+ public static HornetQBuffer wrappedBuffer(final byte[] underlying)
+ {
+ return new ChannelBufferWrapper(Unpooled.wrappedBuffer(underlying));
+ }
+
+ /**
+ * Creates a fixed HornetQBuffer of the given size
+ *
+ * @param size the size of the created HornetQBuffer
+ * @return a fixed HornetQBuffer with the given size
+ */
+ public static HornetQBuffer fixedBuffer(final int size)
+ {
+ return new ChannelBufferWrapper(Unpooled.buffer(size, size));
+ }
+
+ private HornetQBuffers()
+ {
+ // Utility class
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQClusterSecurityException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQClusterSecurityException.java
new file mode 100644
index 0000000000..34b523fa65
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQClusterSecurityException.java
@@ -0,0 +1,32 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+/**
+ * Security exception thrown when the cluster user fails authentication.
+ */
+public final class HornetQClusterSecurityException extends HornetQException
+{
+ private static final long serialVersionUID = -5890578849781297933L;
+
+ public HornetQClusterSecurityException()
+ {
+ super(HornetQExceptionType.CLUSTER_SECURITY_EXCEPTION);
+ }
+
+ public HornetQClusterSecurityException(final String msg)
+ {
+ super(HornetQExceptionType.CLUSTER_SECURITY_EXCEPTION, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQConnectionTimedOutException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQConnectionTimedOutException.java
new file mode 100644
index 0000000000..d52457f907
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQConnectionTimedOutException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.CONNECTION_TIMEDOUT;
+
+/**
+ * A client timed out will connecting to HornetQ server.
+ * @author Andy Taylor 4/30/12
+ */
+public final class HornetQConnectionTimedOutException extends HornetQException
+{
+ private static final long serialVersionUID = 3244233758084830372L;
+
+ public HornetQConnectionTimedOutException()
+ {
+ super(CONNECTION_TIMEDOUT);
+ }
+
+ public HornetQConnectionTimedOutException(String msg)
+ {
+ super(CONNECTION_TIMEDOUT, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQDisconnectedException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQDisconnectedException.java
new file mode 100644
index 0000000000..54536c0cdc
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQDisconnectedException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.DISCONNECTED;
+
+/**
+ * A client was disconnected from HornetQ server when the server has shut down.
+ * @author Andy Taylor 4/30/12
+ */
+public final class HornetQDisconnectedException extends HornetQException
+{
+ private static final long serialVersionUID = 7414966383933311627L;
+
+ public HornetQDisconnectedException()
+ {
+ super(DISCONNECTED);
+ }
+
+ public HornetQDisconnectedException(String message)
+ {
+ super(DISCONNECTED, message);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQDuplicateIdException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQDuplicateIdException.java
new file mode 100644
index 0000000000..cc9d176d33
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQDuplicateIdException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.DUPLICATE_ID_REJECTED;
+
+/**
+ * A DuplicateID was rejected.
+ * @author Andy Taylor 5/2/12
+ */
+public final class HornetQDuplicateIdException extends HornetQException
+{
+ private static final long serialVersionUID = -4302979339865777119L;
+
+ public HornetQDuplicateIdException()
+ {
+ super(DUPLICATE_ID_REJECTED);
+ }
+
+ public HornetQDuplicateIdException(String message)
+ {
+ super(DUPLICATE_ID_REJECTED, message);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQDuplicateMetaDataException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQDuplicateMetaDataException.java
new file mode 100644
index 0000000000..f1549fe3ad
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQDuplicateMetaDataException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.DUPLICATE_METADATA;
+
+/**
+ * A Session Metadata was set in duplication
+ * @author Andy Taylor 5/2/12
+ */
+public final class HornetQDuplicateMetaDataException extends HornetQException
+{
+ private static final long serialVersionUID = 7877182872143004058L;
+
+ public HornetQDuplicateMetaDataException()
+ {
+ super(DUPLICATE_METADATA);
+ }
+
+ public HornetQDuplicateMetaDataException(String msg)
+ {
+ super(DUPLICATE_METADATA, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQException.java
new file mode 100644
index 0000000000..26a7f543ea
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQException.java
@@ -0,0 +1,76 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+package org.hornetq.api.core;
+
+/**
+ * HornetQException is the root exception for the HornetQ API.
+ * @author Tim Fox
+ * @author Andy Taylor
+ */
+public class HornetQException extends Exception
+{
+ private static final long serialVersionUID = -4802014152804997417L;
+
+ private final HornetQExceptionType type;
+
+ public HornetQException()
+ {
+ type = HornetQExceptionType.GENERIC_EXCEPTION;
+ }
+
+ public HornetQException(final String msg)
+ {
+ super(msg);
+ type = HornetQExceptionType.GENERIC_EXCEPTION;
+ }
+
+ /*
+ * This constructor is needed only for the native layer
+ */
+ public HornetQException(int code, String msg)
+ {
+ super(msg);
+
+ this.type = HornetQExceptionType.getType(code);
+ }
+
+ public HornetQException(HornetQExceptionType type, String msg)
+ {
+ super(msg);
+
+ this.type = type;
+ }
+
+ public HornetQException(HornetQExceptionType type)
+ {
+ this.type = type;
+ }
+
+ public HornetQException(HornetQExceptionType type, String message, Throwable t)
+ {
+ super(message, t);
+ this.type = type;
+ }
+
+ public HornetQExceptionType getType()
+ {
+ return type;
+ }
+
+ @Override
+ public String toString()
+ {
+ return this.getClass().getSimpleName() + "[errorType=" + type + " message=" + getMessage() + "]";
+ }
+
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQExceptionType.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQExceptionType.java
new file mode 100644
index 0000000000..830fa1c9f2
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQExceptionType.java
@@ -0,0 +1,298 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+package org.hornetq.api.core;
+
+import java.util.Collections;
+import java.util.EnumSet;
+import java.util.HashMap;
+import java.util.Map;
+
+/**
+ * Defines all {@link HornetQException} types and their codes.
+ */
+public enum HornetQExceptionType
+{
+
+ // Error codes -------------------------------------------------
+
+ INTERNAL_ERROR(000)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQInternalErrorException(msg);
+ }
+ },
+ UNSUPPORTED_PACKET(001)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQUnsupportedPacketException(msg);
+ }
+ },
+ NOT_CONNECTED(002)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQNotConnectedException(msg);
+ }
+ },
+ CONNECTION_TIMEDOUT(003)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQConnectionTimedOutException(msg);
+ }
+ },
+ DISCONNECTED(004)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQDisconnectedException(msg);
+ }
+ },
+ UNBLOCKED(005)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQUnBlockedException(msg);
+ }
+ },
+ IO_ERROR(006)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQIOErrorException(msg);
+ }
+ },
+ QUEUE_DOES_NOT_EXIST(100)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQNonExistentQueueException(msg);
+ }
+ },
+ QUEUE_EXISTS(101)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQQueueExistsException(msg);
+ }
+ },
+ OBJECT_CLOSED(102)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQObjectClosedException(msg);
+ }
+ },
+ INVALID_FILTER_EXPRESSION(103)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQInvalidFilterExpressionException(msg);
+ }
+ },
+ ILLEGAL_STATE(104)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQIllegalStateException(msg);
+ }
+ },
+ SECURITY_EXCEPTION(105)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQSecurityException(msg);
+ }
+ },
+ ADDRESS_EXISTS(107)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQAddressExistsException(msg);
+ }
+ },
+ INCOMPATIBLE_CLIENT_SERVER_VERSIONS(108)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQIncompatibleClientServerException(msg);
+ }
+ },
+ LARGE_MESSAGE_ERROR_BODY(110)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQLargeMessageException(msg);
+ }
+ },
+ TRANSACTION_ROLLED_BACK(111)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQTransactionRolledBackException(msg);
+ }
+ },
+ SESSION_CREATION_REJECTED(112)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQSessionCreationException(msg);
+ }
+ },
+ DUPLICATE_ID_REJECTED(113)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQDuplicateIdException(msg);
+ }
+ },
+ DUPLICATE_METADATA(114)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQDuplicateMetaDataException(msg);
+ }
+ },
+ TRANSACTION_OUTCOME_UNKNOWN(115)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQTransactionOutcomeUnknownException(msg);
+ }
+ },
+ ALREADY_REPLICATING(116)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQAlreadyReplicatingException(msg);
+ }
+ },
+ INTERCEPTOR_REJECTED_PACKET(117)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQInterceptorRejectedPacketException(msg);
+ }
+ },
+ INVALID_TRANSIENT_QUEUE_USE(118)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQInvalidTransientQueueUseException(msg);
+ }
+ },
+
+ GENERIC_EXCEPTION(999),
+ NATIVE_ERROR_INTERNAL(200),
+ NATIVE_ERROR_INVALID_BUFFER(201),
+ NATIVE_ERROR_NOT_ALIGNED(202),
+ NATIVE_ERROR_CANT_INITIALIZE_AIO(203),
+ NATIVE_ERROR_CANT_RELEASE_AIO(204),
+ NATIVE_ERROR_CANT_OPEN_CLOSE_FILE(205),
+ NATIVE_ERROR_CANT_ALLOCATE_QUEUE(206),
+ NATIVE_ERROR_PREALLOCATE_FILE(208),
+ NATIVE_ERROR_ALLOCATE_MEMORY(209),
+ ADDRESS_FULL(210)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQAddressFullException(msg);
+ }
+ },
+ LARGE_MESSAGE_INTERRUPTED(211)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQLargeMessageInterruptedException(msg);
+ }
+ },
+ CLUSTER_SECURITY_EXCEPTION(212)
+ {
+ @Override
+ public HornetQException createException(String msg)
+ {
+ return new HornetQClusterSecurityException(msg);
+ }
+
+ };
+
+ private static final Map
+ * Normally this means you are trying to use a newer client on an older server.
+ * @author Andy Taylor
+ */
+public final class HornetQIncompatibleClientServerException extends HornetQException
+{
+ private static final long serialVersionUID = -1662999230291452298L;
+
+ public HornetQIncompatibleClientServerException()
+ {
+ super(INCOMPATIBLE_CLIENT_SERVER_VERSIONS);
+ }
+
+ public HornetQIncompatibleClientServerException(String msg)
+ {
+ super(INCOMPATIBLE_CLIENT_SERVER_VERSIONS, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInterceptorRejectedPacketException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInterceptorRejectedPacketException.java
new file mode 100644
index 0000000000..dccc16f028
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInterceptorRejectedPacketException.java
@@ -0,0 +1,37 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.INTERCEPTOR_REJECTED_PACKET;
+
+/**
+ * An outgoing interceptor returned false.
+ * @see org.hornetq.api.core.client.ServerLocator#addOutgoingInterceptor(org.hornetq.api.core.Interceptor)
+ * @author Justin Bertram
+ */
+// XXX I doubt any reader will make much sense of this Javadoc's text.
+public final class HornetQInterceptorRejectedPacketException extends HornetQException
+{
+ private static final long serialVersionUID = -5798841227645281815L;
+
+ public HornetQInterceptorRejectedPacketException()
+ {
+ super(INTERCEPTOR_REJECTED_PACKET);
+ }
+
+ public HornetQInterceptorRejectedPacketException(String msg)
+ {
+ super(INTERCEPTOR_REJECTED_PACKET, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInternalErrorException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInternalErrorException.java
new file mode 100644
index 0000000000..fc0930927a
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInternalErrorException.java
@@ -0,0 +1,45 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.INTERNAL_ERROR;
+
+/**
+ * Internal error which prevented HornetQ from performing an important operation.
+ * @author Andy Taylor 4/30/12
+ */
+public final class HornetQInternalErrorException extends HornetQException
+{
+ private static final long serialVersionUID = -5987814047521530695L;
+
+ public HornetQInternalErrorException()
+ {
+ super(INTERNAL_ERROR);
+ }
+
+ public HornetQInternalErrorException(String msg)
+ {
+ super(INTERNAL_ERROR, msg);
+ }
+
+ public HornetQInternalErrorException(String message, Exception e)
+ {
+ super(INTERNAL_ERROR, message, e);
+ }
+
+ public HornetQInternalErrorException(String message, Throwable t)
+ {
+ super(INTERNAL_ERROR, message, t);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInterruptedException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInterruptedException.java
new file mode 100644
index 0000000000..9fb95d7533
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInterruptedException.java
@@ -0,0 +1,27 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+package org.hornetq.api.core;
+
+/**
+ * When an interruption happens, we will just throw a non-checked exception.
+ * @author clebertsuconic
+ */
+public final class HornetQInterruptedException extends RuntimeException
+{
+ private static final long serialVersionUID = -5744690023549671221L;
+
+ public HornetQInterruptedException(Throwable cause)
+ {
+ super(cause);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInvalidFilterExpressionException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInvalidFilterExpressionException.java
new file mode 100644
index 0000000000..0dac654549
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInvalidFilterExpressionException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.INVALID_FILTER_EXPRESSION;
+
+/**
+ * A filter expression was found to be invalid.
+ * @author Andy Taylor 4/30/12
+ */
+public final class HornetQInvalidFilterExpressionException extends HornetQException
+{
+ private static final long serialVersionUID = 7188625553939665128L;
+
+ public HornetQInvalidFilterExpressionException()
+ {
+ super(INVALID_FILTER_EXPRESSION);
+ }
+
+ public HornetQInvalidFilterExpressionException(String msg)
+ {
+ super(INVALID_FILTER_EXPRESSION, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInvalidTransientQueueUseException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInvalidTransientQueueUseException.java
new file mode 100644
index 0000000000..302e7c2496
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQInvalidTransientQueueUseException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.INVALID_TRANSIENT_QUEUE_USE;
+
+/**
+ * An operation failed because a queue exists on the server.
+ * @author Andy Taylor 4/30/12
+ */
+public final class HornetQInvalidTransientQueueUseException extends HornetQException
+{
+ private static final long serialVersionUID = -405552292451883063L;
+
+ public HornetQInvalidTransientQueueUseException()
+ {
+ super(INVALID_TRANSIENT_QUEUE_USE);
+ }
+
+ public HornetQInvalidTransientQueueUseException(String msg)
+ {
+ super(INVALID_TRANSIENT_QUEUE_USE, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQLargeMessageException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQLargeMessageException.java
new file mode 100644
index 0000000000..626dada3d2
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQLargeMessageException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.LARGE_MESSAGE_ERROR_BODY;
+
+/**
+ * A problem occurred while manipulating the body of a large message.
+ * @author Andy Taylor 5/2/12
+ */
+public final class HornetQLargeMessageException extends HornetQException
+{
+ private static final long serialVersionUID = 1087867463974768491L;
+
+ public HornetQLargeMessageException()
+ {
+ super(LARGE_MESSAGE_ERROR_BODY);
+ }
+
+ public HornetQLargeMessageException(String msg)
+ {
+ super(LARGE_MESSAGE_ERROR_BODY, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQLargeMessageInterruptedException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQLargeMessageInterruptedException.java
new file mode 100644
index 0000000000..6ce19d8317
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQLargeMessageInterruptedException.java
@@ -0,0 +1,36 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+
+import static org.hornetq.api.core.HornetQExceptionType.LARGE_MESSAGE_INTERRUPTED;
+
+/**
+ * @author Clebert
+ */
+// XXX
+public class HornetQLargeMessageInterruptedException extends HornetQException
+{
+ private static final long serialVersionUID = 0;
+
+ public HornetQLargeMessageInterruptedException(String message)
+ {
+ super(LARGE_MESSAGE_INTERRUPTED, message);
+ }
+
+ public HornetQLargeMessageInterruptedException()
+ {
+ super(LARGE_MESSAGE_INTERRUPTED);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQNativeIOError.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQNativeIOError.java
new file mode 100644
index 0000000000..e7c24cf8d9
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQNativeIOError.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+
+/**
+ * An error has happened at HornetQ's native (non-Java) code used in reading and writing data.
+ * @author Andy Taylor 5/4/12
+ */
+// XXX
+public final class HornetQNativeIOError extends HornetQException
+{
+ private static final long serialVersionUID = 2355120980683293085L;
+
+ public HornetQNativeIOError()
+ {
+ super(HornetQExceptionType.NATIVE_ERROR_CANT_INITIALIZE_AIO);
+ }
+
+ public HornetQNativeIOError(String msg)
+ {
+ super(HornetQExceptionType.NATIVE_ERROR_CANT_INITIALIZE_AIO, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQNonExistentQueueException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQNonExistentQueueException.java
new file mode 100644
index 0000000000..b2924910d2
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQNonExistentQueueException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.QUEUE_DOES_NOT_EXIST;
+
+/**
+ * An operation failed because a queue does not exist on the server.
+ * @author Andy Taylor 4/30/12
+ */
+public final class HornetQNonExistentQueueException extends HornetQException
+{
+ private static final long serialVersionUID = -8199298881947523607L;
+
+ public HornetQNonExistentQueueException()
+ {
+ super(QUEUE_DOES_NOT_EXIST);
+ }
+
+ public HornetQNonExistentQueueException(String msg)
+ {
+ super(QUEUE_DOES_NOT_EXIST, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQNotConnectedException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQNotConnectedException.java
new file mode 100644
index 0000000000..f6329ff17a
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQNotConnectedException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.NOT_CONNECTED;
+
+/**
+ * A client is not able to connect to HornetQ server.
+ * @author Andy Taylor 4/30/12
+ */
+public final class HornetQNotConnectedException extends HornetQException
+{
+ private static final long serialVersionUID = -3489189971813613325L;
+
+ public HornetQNotConnectedException(String message)
+ {
+ super(NOT_CONNECTED, message);
+ }
+
+ public HornetQNotConnectedException()
+ {
+ super(NOT_CONNECTED);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQObjectClosedException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQObjectClosedException.java
new file mode 100644
index 0000000000..bfc8c6be9e
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQObjectClosedException.java
@@ -0,0 +1,36 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.OBJECT_CLOSED;
+
+/**
+ * A client operation failed because the calling resource (ClientSession, ClientProducer, etc.) is
+ * closed.
+ * @author Andy Taylor 4/30/12
+ */
+public final class HornetQObjectClosedException extends HornetQException
+{
+ private static final long serialVersionUID = 809024052184914812L;
+
+ public HornetQObjectClosedException()
+ {
+ super(OBJECT_CLOSED);
+ }
+
+ public HornetQObjectClosedException(String msg)
+ {
+ super(OBJECT_CLOSED, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQPropertyConversionException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQPropertyConversionException.java
new file mode 100644
index 0000000000..f56ac51d10
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQPropertyConversionException.java
@@ -0,0 +1,30 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+package org.hornetq.api.core;
+
+/**
+ * A PropertyConversionException is thrown by {@code org.hornetq.api.core.Message} methods when a
+ * property can not be converted to the expected type.
+ * @author Jeff Mesnil
+ * @see org.hornetq.api.core.Message
+ */
+public final class HornetQPropertyConversionException extends RuntimeException
+{
+
+ private static final long serialVersionUID = -3010008708334904332L;
+
+ public HornetQPropertyConversionException(final String message)
+ {
+ super(message);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQQueueExistsException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQQueueExistsException.java
new file mode 100644
index 0000000000..8e9343824e
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQQueueExistsException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.QUEUE_EXISTS;
+
+/**
+ * An operation failed because a queue exists on the server.
+ * @author Andy Taylor 4/30/12
+ */
+public final class HornetQQueueExistsException extends HornetQException
+{
+ private static final long serialVersionUID = -405552292451883063L;
+
+ public HornetQQueueExistsException()
+ {
+ super(QUEUE_EXISTS);
+ }
+
+ public HornetQQueueExistsException(String msg)
+ {
+ super(QUEUE_EXISTS, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQSecurityException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQSecurityException.java
new file mode 100644
index 0000000000..ae3f0efb13
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQSecurityException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.SECURITY_EXCEPTION;
+
+/**
+ * A security problem occurred (authentication issues, permission issues,...)
+ * @author Andy Taylor 5/2/12
+ */
+public final class HornetQSecurityException extends HornetQException
+{
+ private static final long serialVersionUID = 3291210307590756881L;
+
+ public HornetQSecurityException()
+ {
+ super(SECURITY_EXCEPTION);
+ }
+
+ public HornetQSecurityException(String msg)
+ {
+ super(SECURITY_EXCEPTION, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQSessionCreationException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQSessionCreationException.java
new file mode 100644
index 0000000000..e42b2728cc
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQSessionCreationException.java
@@ -0,0 +1,36 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.SESSION_CREATION_REJECTED;
+
+/**
+ * The creation of a session was rejected by the server (e.g. if the server is starting and has not
+ * finish to be initialized.
+ * @author Andy Taylor 5/2/12
+ */
+public final class HornetQSessionCreationException extends HornetQException
+{
+ private static final long serialVersionUID = -4486139158452585895L;
+
+ public HornetQSessionCreationException()
+ {
+ super(SESSION_CREATION_REJECTED);
+ }
+
+ public HornetQSessionCreationException(String msg)
+ {
+ super(SESSION_CREATION_REJECTED, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQTransactionOutcomeUnknownException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQTransactionOutcomeUnknownException.java
new file mode 100644
index 0000000000..83587a25ed
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQTransactionOutcomeUnknownException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.TRANSACTION_OUTCOME_UNKNOWN;
+
+/**
+ * The outcome of a transaction is unknown.
+ * @author Andy Taylor 5/2/12
+ */
+public final class HornetQTransactionOutcomeUnknownException extends HornetQException
+{
+ private static final long serialVersionUID = 7940794286427650558L;
+
+ public HornetQTransactionOutcomeUnknownException()
+ {
+ super(TRANSACTION_OUTCOME_UNKNOWN);
+ }
+
+ public HornetQTransactionOutcomeUnknownException(String msg)
+ {
+ super(TRANSACTION_OUTCOME_UNKNOWN, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQTransactionRolledBackException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQTransactionRolledBackException.java
new file mode 100644
index 0000000000..818702b83f
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQTransactionRolledBackException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.TRANSACTION_ROLLED_BACK;
+
+/**
+ * A transaction was rolled back.
+ * @author Andy Taylor 5/2/12
+ */
+public final class HornetQTransactionRolledBackException extends HornetQException
+{
+ private static final long serialVersionUID = 5823412198677126300L;
+
+ public HornetQTransactionRolledBackException()
+ {
+ super(TRANSACTION_ROLLED_BACK);
+ }
+
+ public HornetQTransactionRolledBackException(String msg)
+ {
+ super(TRANSACTION_ROLLED_BACK, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQUnBlockedException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQUnBlockedException.java
new file mode 100644
index 0000000000..dc9ab1a72d
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQUnBlockedException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.UNBLOCKED;
+
+/**
+ * A blocking call from a client was unblocked during failover.
+ * @author Andy Taylor 4/30/12
+ */
+public final class HornetQUnBlockedException extends HornetQException
+{
+ private static final long serialVersionUID = -4507889261891160608L;
+
+ public HornetQUnBlockedException()
+ {
+ super(UNBLOCKED);
+ }
+
+ public HornetQUnBlockedException(String msg)
+ {
+ super(UNBLOCKED, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQUnsupportedPacketException.java b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQUnsupportedPacketException.java
new file mode 100644
index 0000000000..f0dfc06f86
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/HornetQUnsupportedPacketException.java
@@ -0,0 +1,35 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import static org.hornetq.api.core.HornetQExceptionType.UNSUPPORTED_PACKET;
+
+/**
+ * A packet of unsupported type was received by HornetQ PacketHandler.
+ * @author Andy Taylor 4/30/12
+ */
+public final class HornetQUnsupportedPacketException extends HornetQException
+{
+ private static final long serialVersionUID = -7074681529482463675L;
+
+ public HornetQUnsupportedPacketException()
+ {
+ super(UNSUPPORTED_PACKET);
+ }
+
+ public HornetQUnsupportedPacketException(String msg)
+ {
+ super(UNSUPPORTED_PACKET, msg);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/api/core/Pair.java b/hornetq-commons/src/main/java/org/hornetq/api/core/Pair.java
new file mode 100644
index 0000000000..9cf8f72fbe
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/api/core/Pair.java
@@ -0,0 +1,105 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+
+package org.hornetq.api.core;
+
+import java.io.Serializable;
+
+/**
+ * A Pair is a holder for 2 objects.
+ *
+ * This is a utility class.
+ * @author Tim Fox
+ */
+public final class Pair
+ * This object is used heavily throughout HornetQ for performance reasons.
+ *
+ * @author Tim Fox
+ */
+public final class SimpleString implements CharSequence, Serializable, Comparable
+ * If {@code string} is {@code null}, the return value will be {@code null} too.
+ *
+ * @param string String used to instantiate a SimpleString.
+ */
+ public static SimpleString toSimpleString(final String string)
+ {
+ if (string == null)
+ {
+ return null;
+ }
+ return new SimpleString(string);
+ }
+
+ // Constructors
+ // ----------------------------------------------------------------------
+
+ /**
+ * creates a SimpleString from a conventional String
+ *
+ * @param string the string to transform
+ */
+ public SimpleString(final String string)
+ {
+ int len = string.length();
+
+ data = new byte[len << 1];
+
+ int j = 0;
+
+ for (int i = 0; i < len; i++)
+ {
+ char c = string.charAt(i);
+
+ byte low = (byte) (c & 0xFF); // low byte
+
+ data[j++] = low;
+
+ byte high = (byte) (c >> 8 & 0xFF); // high byte
+
+ data[j++] = high;
+ }
+
+ str = string;
+ }
+
+ /**
+ * creates a SimpleString from a byte array
+ *
+ * @param data the byte array to use
+ */
+ public SimpleString(final byte[] data)
+ {
+ this.data = data;
+ }
+
+ // CharSequence implementation
+ // ---------------------------------------------------------------------------
+
+ public int length()
+ {
+ return data.length >> 1;
+ }
+
+ public char charAt(int pos)
+ {
+ if (pos < 0 || pos >= data.length >> 1)
+ {
+ throw new IndexOutOfBoundsException();
+ }
+ pos <<= 1;
+
+ return (char) ((data[pos] & 0xFF) | (data[pos + 1] << 8) & 0xFF00);
+ }
+
+ public CharSequence subSequence(final int start, final int end)
+ {
+ int len = data.length >> 1;
+
+ if (end < start || start < 0 || end > len)
+ {
+ throw new IndexOutOfBoundsException();
+ }
+ else
+ {
+ int newlen = end - start << 1;
+ byte[] bytes = new byte[newlen];
+
+ System.arraycopy(data, start << 1, bytes, 0, newlen);
+
+ return new SimpleString(bytes);
+ }
+ }
+
+ // Comparable implementation -------------------------------------
+
+ public int compareTo(final SimpleString o)
+ {
+ return toString().compareTo(o.toString());
+ }
+
+ // Public
+ // ---------------------------------------------------------------------------
+
+ /**
+ * returns the underlying byte array of this SimpleString
+ *
+ * @return the byte array
+ */
+ public byte[] getData()
+ {
+ return data;
+ }
+
+ /**
+ * returns true if the SimpleString parameter starts with the same data as this one. false if not.
+ *
+ * @param other the SimpleString to look for
+ * @return true if this SimpleString starts with the same data
+ */
+ public boolean startsWith(final SimpleString other)
+ {
+ byte[] otherdata = other.data;
+
+ if (otherdata.length > data.length)
+ {
+ return false;
+ }
+
+ for (int i = 0; i < otherdata.length; i++)
+ {
+ if (data[i] != otherdata[i])
+ {
+ return false;
+ }
+ }
+
+ return true;
+ }
+
+ @Override
+ public String toString()
+ {
+ if (str == null)
+ {
+ int len = data.length >> 1;
+
+ char[] chars = new char[len];
+
+ int j = 0;
+
+ for (int i = 0; i < len; i++)
+ {
+ int low = data[j++] & 0xFF;
+
+ int high = data[j++] << 8 & 0xFF00;
+
+ chars[i] = (char) (low | high);
+ }
+
+ str = new String(chars);
+ }
+
+ return str;
+ }
+
+ @Override
+ public boolean equals(final Object other)
+ {
+ if (this == other)
+ {
+ return true;
+ }
+
+ if (other instanceof SimpleString)
+ {
+ SimpleString s = (SimpleString) other;
+
+ if (data.length != s.data.length)
+ {
+ return false;
+ }
+
+ for (int i = 0; i < data.length; i++)
+ {
+ if (data[i] != s.data[i])
+ {
+ return false;
+ }
+ }
+
+ return true;
+ }
+ else
+ {
+ return false;
+ }
+ }
+
+ @Override
+ public int hashCode()
+ {
+ if (hash == 0)
+ {
+ int tmphash = 0;
+ for (byte element : data)
+ {
+ tmphash = (tmphash << 5) - tmphash + element; // (hash << 5) - hash is same as hash * 31
+ }
+ hash = tmphash;
+ }
+
+ return hash;
+ }
+
+ /**
+ * Splits this SimpleString into an array of SimpleString using the char param as the delimiter.
+ * i.e. "a.b" would return "a" and "b" if . was the delimiter
+ *
+ * @param delim
+ */
+ public SimpleString[] split(final char delim)
+ {
+ List Encodes and decodes to and from Base64 notation. Homepage: http://iharder.net/base64. The options parameter, which appears in a few places, is used to pass
+ * several pieces of information to the encoder. In the "higher level" methods such as
+ * encodeBytes( bytes, options ) the options parameter can be used to indicate such
+ * things as first gzipping the bytes before encoding them, not inserting linefeeds
+ * (though that breaks strict Base64 compatibility), and encoding using the URL-safe
+ * and Ordered dialects. The constants defined in Base64 can be OR-ed together to combine options, so you
+ * might make a call like this:
+ * to compress the data before encoding it and then making the output have no newline characters.
+ * Change Log:
+ *
+ * I am placing this code in the Public Domain. Do with it as you will.
+ * This software comes with no guarantees or warranties but with
+ * plenty of well-wishing instead!
+ * Please visit http://iharder.net/base64
+ * periodically to check for updates or to contribute improvements.
+ * Encodes up to three bytes of the array source
+ * and writes the resulting four Base64 bytes to destination.
+ * The source and destination arrays can be manipulated
+ * anywhere along their length by specifying
+ * srcOffset and destOffset.
+ * This method does not check to make sure your arrays
+ * are large enough to accommodate srcOffset + 3 for
+ * the source array or destOffset + 4 for
+ * the destination array.
+ * The actual number of significant bytes in your array is
+ * given by numSigBytes. This is the lowest level of the encoding methods with
+ * all possible parameters.
+ * Valid options:
+ * Example:
+ * Example:
+ * Valid options:
+ * Example:
+ * Example:
+ * Valid options:
+ * Example:
+ * Example: This is the lowest level of the decoding methods with
+ * all possible parameters.
+ * Valid options:
+ * Example:
+ * Valid options:
+ * Example:
+ * Is't required to use a Security Block on any calls to this class.
+ *
+ * @author Howard Gao
+ */
+
+public final class ClassloadingUtil
+{
+ private static final String INSTANTIATION_EXCEPTION_MESSAGE =
+ "Your class must have a constructor without arguments. If it is an inner class, it must be static!";
+
+ public static Object newInstanceFromClassLoader(final String className)
+ {
+ ClassLoader loader = ClassloadingUtil.class.getClassLoader();
+ try
+ {
+ Class clazz = loader.loadClass(className);
+ return clazz.newInstance();
+ }
+ catch (Throwable t)
+ {
+ if (t instanceof InstantiationException)
+ {
+ System.out.println(INSTANTIATION_EXCEPTION_MESSAGE);
+ }
+ loader = Thread.currentThread().getContextClassLoader();
+ if (loader == null)
+ throw new RuntimeException("No local context classloader", t);
+
+ try
+ {
+ return loader.loadClass(className).newInstance();
+ }
+ catch (InstantiationException e)
+ {
+ throw new RuntimeException(INSTANTIATION_EXCEPTION_MESSAGE + " " + className, e);
+ }
+ catch (ClassNotFoundException e)
+ {
+ throw new IllegalStateException(e);
+ }
+ catch (IllegalAccessException e)
+ {
+ throw new RuntimeException(e);
+ }
+ }
+ }
+
+ public static Object newInstanceFromClassLoader(final String className, Object... objs)
+ {
+ ClassLoader loader = ClassloadingUtil.class.getClassLoader();
+ try
+ {
+ Class[] parametersType = new Class[objs.length];
+ for (int i = 0; i < objs.length; i++)
+ {
+ parametersType[i] = objs[i].getClass();
+ }
+ Class clazz = loader.loadClass(className);
+ return clazz.getConstructor(parametersType).newInstance(objs);
+ }
+ catch (Throwable t)
+ {
+ if (t instanceof InstantiationException)
+ {
+ System.out.println(INSTANTIATION_EXCEPTION_MESSAGE);
+ }
+ loader = Thread.currentThread().getContextClassLoader();
+ if (loader == null)
+ throw new RuntimeException("No local context classloader", t);
+
+ try
+ {
+ return loader.loadClass(className).newInstance();
+ }
+ catch (InstantiationException e)
+ {
+ throw new RuntimeException(INSTANTIATION_EXCEPTION_MESSAGE + " " + className, e);
+ }
+ catch (ClassNotFoundException e)
+ {
+ throw new IllegalStateException(e);
+ }
+ catch (IllegalAccessException e)
+ {
+ throw new RuntimeException(e);
+ }
+ }
+ }
+
+ public static URL findResource(final String resourceName)
+ {
+ ClassLoader loader = ClassloadingUtil.class.getClassLoader();
+ try
+ {
+ URL resource = loader.getResource(resourceName);
+ if (resource != null)
+ return resource;
+ }
+ catch (Throwable t)
+ {
+ }
+
+ loader = Thread.currentThread().getContextClassLoader();
+ if (loader == null)
+ return null;
+
+ return loader.getResource(resourceName);
+ }
+}
diff --git a/hornetq-commons/src/main/java/org/hornetq/utils/ConcurrentHashSet.java b/hornetq-commons/src/main/java/org/hornetq/utils/ConcurrentHashSet.java
new file mode 100644
index 0000000000..fe6545accd
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/utils/ConcurrentHashSet.java
@@ -0,0 +1,90 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+package org.hornetq.utils;
+
+import java.util.AbstractSet;
+import java.util.Iterator;
+import java.util.concurrent.ConcurrentHashMap;
+import java.util.concurrent.ConcurrentMap;
+
+/**
+ *
+ * A ConcurrentHashSet.
+ *
+ * Offers same concurrency as ConcurrentHashMap but for a Set
+ *
+ * @author Tim Fox
+ * @version $Revision: 1935 $
+ *
+ */
+public class ConcurrentHashSetString encoded = Base64.encodeBytes( mybytes, Base64.GZIP | Base64.DONT_BREAK_LINES );
+ *
+ *
+ *
+ * GZIP: gzip-compresses object before encoding it.
+ * DONT_BREAK_LINES: don't break lines at 76 characters
+ * Note: Technically, this makes your encoding non-compliant.
+ *
+ * encodeObject( myObj, Base64.GZIP ) or
+ * encodeObject( myObj, Base64.GZIP | Base64.DONT_BREAK_LINES )
+ *
+ * @param serializableObject The object to encode
+ * @param options Specified options
+ * @return The Base64-encoded object
+ * @see Base64#GZIP
+ * @see Base64#DONT_BREAK_LINES
+ * @since 2.0
+ */
+ public static String encodeObject(final java.io.Serializable serializableObject, final int options)
+ {
+ // Streams
+ java.io.ByteArrayOutputStream baos = null;
+ java.io.OutputStream b64os = null;
+ java.io.ObjectOutputStream oos = null;
+ java.util.zip.GZIPOutputStream gzos = null;
+
+ // Isolate options
+ int gzip = options & Base64.GZIP;
+
+ try
+ {
+ // ObjectOutputStream -> (GZIP) -> Base64 -> ByteArrayOutputStream
+ baos = new java.io.ByteArrayOutputStream();
+ b64os = new Base64.OutputStream(baos, Base64.ENCODE | options);
+
+ // GZip?
+ if (gzip == Base64.GZIP)
+ {
+ gzos = new java.util.zip.GZIPOutputStream(b64os);
+ oos = new java.io.ObjectOutputStream(gzos);
+ } // end if: gzip
+ else
+ {
+ oos = new java.io.ObjectOutputStream(b64os);
+ }
+
+ oos.writeObject(serializableObject);
+ } // end try
+ catch (java.io.IOException e)
+ {
+ e.printStackTrace();
+ return null;
+ } // end catch
+ finally
+ {
+ try
+ {
+ oos.close();
+ }
+ catch (Exception e)
+ {
+ }
+ try
+ {
+ gzos.close();
+ }
+ catch (Exception e)
+ {
+ }
+ try
+ {
+ b64os.close();
+ }
+ catch (Exception e)
+ {
+ }
+ try
+ {
+ baos.close();
+ }
+ catch (Exception e)
+ {
+ }
+ } // end finally
+
+ // Return value according to relevant encoding.
+ return new String(baos.toByteArray(), Base64.PREFERRED_ENCODING);
+
+ } // end encode
+
+ /**
+ * Encodes a byte array into Base64 notation.
+ * Does not GZip-compress data.
+ *
+ * @param source The data to convert
+ * @since 1.4
+ */
+ public static String encodeBytes(final byte[] source)
+ {
+ return Base64.encodeBytes(source, 0, source.length, Base64.NO_OPTIONS);
+ } // end encodeBytes
+
+ /**
+ * Encodes a byte array into Base64 notation.
+ *
+ * GZIP: gzip-compresses object before encoding it.
+ * DONT_BREAK_LINES: don't break lines at 76 characters
+ * Note: Technically, this makes your encoding non-compliant.
+ *
+ * encodeBytes( myData, Base64.GZIP ) or
+ * encodeBytes( myData, Base64.GZIP | Base64.DONT_BREAK_LINES )
+ *
+ * @param source The data to convert
+ * @param options Specified options
+ * @see Base64#GZIP
+ * @see Base64#DONT_BREAK_LINES
+ * @since 2.0
+ */
+ public static String encodeBytes(final byte[] source, final int options)
+ {
+ return Base64.encodeBytes(source, 0, source.length, options);
+ } // end encodeBytes
+
+ /**
+ * Encodes a byte array into Base64 notation.
+ * Does not GZip-compress data.
+ *
+ * @param source The data to convert
+ * @param off Offset in array where conversion should begin
+ * @param len Length of data to convert
+ * @since 1.4
+ */
+ public static String encodeBytes(final byte[] source, final int off, final int len)
+ {
+ return Base64.encodeBytes(source, off, len, Base64.NO_OPTIONS);
+ } // end encodeBytes
+
+ /**
+ * Encodes a byte array into Base64 notation.
+ *
+ * GZIP: gzip-compresses object before encoding it.
+ * DONT_BREAK_LINES: don't break lines at 76 characters
+ * Note: Technically, this makes your encoding non-compliant.
+ *
+ * encodeBytes( myData, Base64.GZIP ) or
+ * encodeBytes( myData, Base64.GZIP | Base64.DONT_BREAK_LINES )
+ *
+ * @param source The data to convert
+ * @param off Offset in array where conversion should begin
+ * @param len Length of data to convert
+ * @param options options alphabet type is pulled from this (standard, url-safe, ordered)
+ * @see Base64#GZIP
+ * @see Base64#DONT_BREAK_LINES
+ * @since 2.0
+ */
+ public static String encodeBytes(final byte[] source, final int off, final int len, final int options)
+ {
+ // Isolate options
+ int dontBreakLines = options & Base64.DONT_BREAK_LINES;
+ int gzip = options & Base64.GZIP;
+
+ // Compress?
+ if (gzip == Base64.GZIP)
+ {
+ java.io.ByteArrayOutputStream baos = null;
+ java.util.zip.GZIPOutputStream gzos = null;
+ Base64.OutputStream b64os = null;
+
+ try
+ {
+ // GZip -> Base64 -> ByteArray
+ baos = new java.io.ByteArrayOutputStream();
+ b64os = new Base64.OutputStream(baos, Base64.ENCODE | options);
+ gzos = new java.util.zip.GZIPOutputStream(b64os);
+
+ gzos.write(source, off, len);
+ gzos.close();
+ } // end try
+ catch (java.io.IOException e)
+ {
+ e.printStackTrace();
+ return null;
+ } // end catch
+ finally
+ {
+ try
+ {
+ gzos.close();
+ }
+ catch (Exception e)
+ {
+ }
+ try
+ {
+ b64os.close();
+ }
+ catch (Exception e)
+ {
+ }
+ try
+ {
+ baos.close();
+ }
+ catch (Exception e)
+ {
+ }
+ } // end finally
+
+ // Return value according to relevant encoding.
+ return new String(baos.toByteArray(), Base64.PREFERRED_ENCODING);
+ } // end if: compress
+
+ // Else, don't compress. Better not to use streams at all then.
+ else
+ {
+ // Convert option to boolean in way that code likes it.
+ boolean breakLines = dontBreakLines == 0;
+
+ int len43 = len * 4 / 3;
+ byte[] outBuff = new byte[len43 + (len % 3 > 0 ? 4 : 0) // Account for padding
+ +
+ (breakLines ? len43 / Base64.MAX_LINE_LENGTH : 0)]; // New lines
+ int d = 0;
+ int e = 0;
+ int len2 = len - 2;
+ int lineLength = 0;
+ for (; d < len2; d += 3, e += 4)
+ {
+ Base64.encode3to4(source, d + off, 3, outBuff, e, options);
+
+ lineLength += 4;
+ if (breakLines && lineLength == Base64.MAX_LINE_LENGTH)
+ {
+ outBuff[e + 4] = Base64.NEW_LINE;
+ e++;
+ lineLength = 0;
+ } // end if: end of line
+ } // en dfor: each piece of array
+
+ if (d < len)
+ {
+ Base64.encode3to4(source, d + off, len - d, outBuff, e, options);
+ e += 4;
+ } // end if: some padding needed
+
+ // Return value according to relevant encoding.
+ return new String(outBuff, 0, e, Base64.PREFERRED_ENCODING);
+
+ } // end else: don't compress
+
+ } // end encodeBytes
+
+ /* ******** D E C O D I N G M E T H O D S ******** */
+
+ /**
+ * Decodes four bytes from array source
+ * and writes the resulting bytes (up to three of them)
+ * to destination.
+ * The source and destination arrays can be manipulated
+ * anywhere along their length by specifying
+ * srcOffset and destOffset.
+ * This method does not check to make sure your arrays
+ * are large enough to accommodate srcOffset + 4 for
+ * the source array or destOffset + 3 for
+ * the destination array.
+ * This method returns the actual number of bytes that
+ * were converted from the Base64 encoding.
+ *
+ * ENCODE or DECODE: Encode or Decode as data is read.
+ * DONT_BREAK_LINES: don't break lines at 76 characters
+ * (only meaningful when encoding)
+ * Note: Technically, this makes your encoding non-compliant.
+ *
+ * new Base64.InputStream( in, Base64.DECODE )
+ *
+ * @param in the java.io.InputStream from which to read data.
+ * @param options Specified options
+ * @see Base64#ENCODE
+ * @see Base64#DECODE
+ * @see Base64#DONT_BREAK_LINES
+ * @since 2.0
+ */
+ public InputStream(final java.io.InputStream in, final int options)
+ {
+ super(in);
+ breakLines = (options & Base64.DONT_BREAK_LINES) != Base64.DONT_BREAK_LINES;
+ encode = (options & Base64.ENCODE) == Base64.ENCODE;
+ bufferLength = encode ? 4 : 3;
+ buffer = new byte[bufferLength];
+ position = -1;
+ lineLength = 0;
+ this.options = options; // Record for later, mostly to determine which alphabet to use
+ alphabet = Base64.getAlphabet(options);
+ decodabet = Base64.getDecodabet(options);
+ } // end constructor
+
+ /**
+ * Reads enough of the input stream to convert
+ * to/from Base64 and returns the next byte.
+ *
+ * @return next byte
+ * @since 1.3
+ */
+ @Override
+ public int read() throws java.io.IOException
+ {
+ // Do we need to get data?
+ if (position < 0)
+ {
+ if (encode)
+ {
+ byte[] b3 = new byte[3];
+ int numBinaryBytes = 0;
+ for (int i = 0; i < 3; i++)
+ {
+ try
+ {
+ int b = in.read();
+
+ // If end of stream, b is -1.
+ if (b >= 0)
+ {
+ b3[i] = (byte) b;
+ numBinaryBytes++;
+ } // end if: not end of stream
+
+ } // end try: read
+ catch (java.io.IOException e)
+ {
+ // Only a problem if we got no data at all.
+ if (i == 0)
+ {
+ throw e;
+ }
+
+ } // end catch
+ } // end for: each needed input byte
+
+ if (numBinaryBytes > 0)
+ {
+ Base64.encode3to4(b3, 0, numBinaryBytes, buffer, 0, options);
+ position = 0;
+ numSigBytes = 4;
+ } // end if: got data
+ else
+ {
+ return -1;
+ }
+ } // end if: encoding
+
+ // Else decoding
+ else
+ {
+ byte[] b4 = new byte[4];
+ int i = 0;
+ for (i = 0; i < 4; i++)
+ {
+ // Read four "meaningful" bytes:
+ int b = 0;
+ do
+ {
+ b = in.read();
+ }
+ while (b >= 0 && decodabet[b & 0x7f] <= Base64.WHITE_SPACE_ENC);
+
+ if (b < 0)
+ {
+ break; // Reads a -1 if end of stream
+ }
+
+ b4[i] = (byte) b;
+ } // end for: each needed input byte
+
+ if (i == 4)
+ {
+ numSigBytes = Base64.decode4to3(b4, 0, buffer, 0, options);
+ position = 0;
+ } // end if: got four characters
+ else if (i == 0)
+ {
+ return -1;
+ }
+ else
+ {
+ // Must have broken out from above.
+ throw new java.io.IOException("Improperly padded Base64 input.");
+ }
+
+ } // end else: decode
+ } // end else: get data
+
+ // Got data?
+ if (position >= 0)
+ {
+ // End of relevant data?
+ if ( /*!encode &&*/position >= numSigBytes)
+ {
+ return -1;
+ }
+
+ if (encode && breakLines && lineLength >= Base64.MAX_LINE_LENGTH)
+ {
+ lineLength = 0;
+ return '\n';
+ } // end if
+ else
+ {
+ lineLength++; // This isn't important when decoding
+ // but throwing an extra "if" seems
+ // just as wasteful.
+
+ int b = buffer[position++];
+
+ if (position >= bufferLength)
+ {
+ position = -1;
+ }
+
+ return b & 0xFF; // This is how you "cast" a byte that's
+ // intended to be unsigned.
+ } // end else
+ } // end if: position >= 0
+ else
+ {
+ // When JDK1.4 is more accepted, use an assertion here.
+ throw new java.io.IOException("Error in Base64 code reading stream.");
+ }
+ } // end read
+
+ /**
+ * Calls {@link #read()} repeatedly until the end of stream
+ * is reached or len bytes are read.
+ * Returns number of bytes read into array or -1 if
+ * end of stream is encountered.
+ *
+ * @param dest array to hold values
+ * @param off offset for array
+ * @param len max number of bytes to read into array
+ * @return bytes read into array or -1 if end of stream is encountered.
+ * @since 1.3
+ */
+ @Override
+ public int read(final byte[] dest, final int off, final int len) throws java.io.IOException
+ {
+ int i;
+ int b;
+ for (i = 0; i < len; i++)
+ {
+ b = read();
+
+ // if( b < 0 && i == 0 )
+ // return -1;
+
+ if (b >= 0)
+ {
+ dest[off + i] = (byte) b;
+ }
+ else if (i == 0)
+ {
+ return -1;
+ }
+ else
+ {
+ break; // Out of 'for' loop
+ }
+ } // end for: each byte read
+ return i;
+ } // end read
+
+ } // end inner class InputStream
+
+ /* ******** I N N E R C L A S S O U T P U T S T R E A M ******** */
+
+ /**
+ * A {@link Base64.OutputStream} will write data to another
+ * java.io.OutputStream, given in the constructor,
+ * and encode/decode to/from Base64 notation on the fly.
+ *
+ * @see Base64
+ * @since 1.3
+ */
+ public static class OutputStream extends java.io.FilterOutputStream
+ {
+ private final boolean encode;
+
+ private int position;
+
+ private byte[] buffer;
+
+ private final int bufferLength;
+
+ private int lineLength;
+
+ private final boolean breakLines;
+
+ private final byte[] b4; // Scratch used in a few places
+
+ private boolean suspendEncoding;
+
+ private final int options; // Record for later
+
+ private final byte[] alphabet; // Local copies to avoid extra method calls
+
+ private final byte[] decodabet; // Local copies to avoid extra method calls
+
+ /**
+ * Constructs a {@link Base64.OutputStream} in ENCODE mode.
+ *
+ * @param out the java.io.OutputStream to which data will be written.
+ * @since 1.3
+ */
+ public OutputStream(final java.io.OutputStream out)
+ {
+ this(out, Base64.ENCODE);
+ } // end constructor
+
+ /**
+ * Constructs a {@link Base64.OutputStream} in
+ * either ENCODE or DECODE mode.
+ *
+ * ENCODE or DECODE: Encode or Decode as data is read.
+ * DONT_BREAK_LINES: don't break lines at 76 characters
+ * (only meaningful when encoding)
+ * Note: Technically, this makes your encoding non-compliant.
+ *
+ * new Base64.OutputStream( out, Base64.ENCODE )
+ *
+ * @param out the java.io.OutputStream to which data will be written.
+ * @param options Specified options.
+ * @see Base64#ENCODE
+ * @see Base64#DECODE
+ * @see Base64#DONT_BREAK_LINES
+ * @since 1.3
+ */
+ public OutputStream(final java.io.OutputStream out, final int options)
+ {
+ super(out);
+ breakLines = (options & Base64.DONT_BREAK_LINES) != Base64.DONT_BREAK_LINES;
+ encode = (options & Base64.ENCODE) == Base64.ENCODE;
+ bufferLength = encode ? 3 : 4;
+ buffer = new byte[bufferLength];
+ position = 0;
+ lineLength = 0;
+ suspendEncoding = false;
+ b4 = new byte[4];
+ this.options = options;
+ alphabet = Base64.getAlphabet(options);
+ decodabet = Base64.getDecodabet(options);
+ } // end constructor
+
+ /**
+ * Writes the byte to the output stream after
+ * converting to/from Base64 notation.
+ * When encoding, bytes are buffered three
+ * at a time before the output stream actually
+ * gets a write() call.
+ * When decoding, bytes are buffered four
+ * at a time.
+ *
+ * @param theByte the byte to write
+ * @since 1.3
+ */
+ @Override
+ public void write(final int theByte) throws java.io.IOException
+ {
+ // Encoding suspended?
+ if (suspendEncoding)
+ {
+ super.out.write(theByte);
+ return;
+ } // end if: supsended
+
+ // Encode?
+ if (encode)
+ {
+ buffer[position++] = (byte) theByte;
+ if (position >= bufferLength) // Enough to encode.
+ {
+ out.write(Base64.encode3to4(b4, buffer, bufferLength, options));
+
+ lineLength += 4;
+ if (breakLines && lineLength >= Base64.MAX_LINE_LENGTH)
+ {
+ out.write(Base64.NEW_LINE);
+ lineLength = 0;
+ } // end if: end of line
+
+ position = 0;
+ } // end if: enough to output
+ } // end if: encoding
+
+ // Else, Decoding
+ else
+ {
+ // Meaningful Base64 character?
+ if (decodabet[theByte & 0x7f] > Base64.WHITE_SPACE_ENC)
+ {
+ buffer[position++] = (byte) theByte;
+ if (position >= bufferLength) // Enough to output.
+ {
+ int len = Base64.decode4to3(buffer, 0, b4, 0, options);
+ out.write(b4, 0, len);
+ // out.write( Base64.decode4to3( buffer ) );
+ position = 0;
+ } // end if: enough to output
+ } // end if: meaningful base64 character
+ else if (decodabet[theByte & 0x7f] != Base64.WHITE_SPACE_ENC)
+ {
+ throw new java.io.IOException("Invalid character in Base64 data.");
+ }
+ } // end else: decoding
+ } // end write
+
+ /**
+ * Calls {@link #write(int)} repeatedly until len
+ * bytes are written.
+ *
+ * @param theBytes array from which to read bytes
+ * @param off offset for array
+ * @param len max number of bytes to read into array
+ * @since 1.3
+ */
+ @Override
+ public void write(final byte[] theBytes, final int off, final int len) throws java.io.IOException
+ {
+ // Encoding suspended?
+ if (suspendEncoding)
+ {
+ super.out.write(theBytes, off, len);
+ return;
+ } // end if: supsended
+
+ for (int i = 0; i < len; i++)
+ {
+ write(theBytes[off + i]);
+ } // end for: each byte written
+
+ } // end write
+
+ /**
+ * Method added by PHIL. [Thanks, PHIL. -Rob]
+ * This pads the buffer without closing the stream.
+ */
+ public void flushBase64() throws java.io.IOException
+ {
+ if (position > 0)
+ {
+ if (encode)
+ {
+ out.write(Base64.encode3to4(b4, buffer, position, options));
+ position = 0;
+ } // end if: encoding
+ else
+ {
+ throw new java.io.IOException("Base64 input not properly padded.");
+ }
+ } // end if: buffer partially full
+
+ } // end flush
+
+ /**
+ * Flushes and closes (I think, in the superclass) the stream.
+ *
+ * @since 1.3
+ */
+ @Override
+ public void close() throws java.io.IOException
+ {
+ // 1. Ensure that pending characters are written
+ flushBase64();
+
+ // 2. Actually close the stream
+ // Base class both flushes and closes.
+ super.close();
+
+ buffer = null;
+ out = null;
+ } // end close
+
+ /**
+ * Suspends encoding of the stream.
+ * May be helpful if you need to embed a piece of
+ * base640-encoded data in a stream.
+ *
+ * @since 1.5.1
+ */
+ public void suspendEncoding() throws java.io.IOException
+ {
+ flushBase64();
+ suspendEncoding = true;
+ } // end suspendEncoding
+
+ /**
+ * Resumes encoding of the stream.
+ * May be helpful if you need to embed a piece of
+ * base640-encoded data in a stream.
+ *
+ * @since 1.5.1
+ */
+ public void resumeEncoding()
+ {
+ suspendEncoding = false;
+ } // end resumeEncoding
+
+ } // end inner class OutputStream
+
+} // end class Base64
diff --git a/hornetq-commons/src/main/java/org/hornetq/utils/ClassloadingUtil.java b/hornetq-commons/src/main/java/org/hornetq/utils/ClassloadingUtil.java
new file mode 100644
index 0000000000..fb6665b6b0
--- /dev/null
+++ b/hornetq-commons/src/main/java/org/hornetq/utils/ClassloadingUtil.java
@@ -0,0 +1,129 @@
+/*
+ * Copyright 2005-2014 Red Hat, Inc.
+ * Red Hat licenses this file to you under the Apache License, version
+ * 2.0 (the "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ * implied. See the License for the specific language governing
+ * permissions and limitations under the License.
+ */
+package org.hornetq.utils;
+
+import java.net.URL;
+
+/**
+ * This class will be used to perform generic class-loader operations,
+ * such as load a class first using TCCL, and then the classLoader used by HornetQ (ClassloadingUtil.getClass().getClassLoader()).
+ *