Changes introduced by Messaging 1.0.1.SP1

1. Messaging uses Remoting 2.2.0.Alpha3

The remoting dependency has been upgraded to 2.2.0.Alpha3

2. Configurable maximum delivery attempts and DLQ

SP1 allows you to configure an arbitrary DLQ where messages will sent after a number of failed delivery attempts. The queue name can be specified using ServerPeer's DLQName attribute. The number of delivery attempts can be specified using ServerPeer's MaxDeliveryAttempts attribute.

Both attributes are part of ServerPeer service configuration, found in messaging-service.xml:

   <mbean code="org.jboss.jms.server.ServerPeer"
      name="jboss.messaging:service=ServerPeer"
      xmbean-dd="xmdesc/ServerPeer-xmbean.xml">

      ...

      <attribute name="MaxDeliveryAttempts">10</attribute>
      <attribute name="DLQName">DLQ</attribute>
   </mbean>

The queue to be used as DLQ must be declared in destinations-service.xml, so it will be deployed at boot.

3. Remoting configuration changes

The remoting-service.xml needs to be changed, by adding the following two new attributes (result of fixing http://jira.jboss.org/jira/browse/JBMESSAGING-644):

<attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
<attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>

to the Connector's configuration.

Example:

   <mbean code="org.jboss.remoting.transport.Connector"
          name="jboss.messaging:service=Connector,transport=socket"
          display-name="Socket transport Connector">
      <attribute name="Configuration">
         <config>
            <invoker transport="socket">
               ...
               <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
               <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
               ...
            </invoker>
         </config>
      </attribute>
   </mbean>

In case you use an SSL connector, the same attributes must be added to the SSL Connector's configuration.

4. Database schema changes

The number of delivery attempts is now recorded in the database. For this reason, SP1 has introduced a database schema change. 1.0.1.GA-created tables are incompatible with 1.0.1.SP1, so in order to use SP1, you need to drop the old tables and recreate them.

Referenced by: