Chapter 6. JBoss Messaging Clustered Installation

Chapter 6. JBoss Messaging Clustered Installation
Prev		Next

Note

You need Apache ant 1.7.0 or newer pre-installed on your system and available in you path in order to be able to perform the installation process described below.

Use the release-admin.xml ant script shipped with the release to create individual cluster node configurations.

The typical usage is:

cd util
ant -f release-admin.xml [-Did=node-id] [-Dports=port-config-label]
[-Ddatabase=db-name] cluster-node

where:

node-id is the unique node ID, an integer that must be unique per cluster. If not specified, it defaults to 0.
port-config-label is a binding manager server configuration label. The short story behind this parameter is the following: multiple application servers running on the same physical machine need to use different service port ranges to avoid port conflicts. You can configure the whole port range used by a server instance by enabling a special service, the binding management service, and specifiying a "server" configuration in the binding manager's configuration file, which will determine specific port values to use when starting that instance. The Messaging installation script can enable the service binding manager and performs all configuration changes automatically. You only need to specify the "server" configuration you want to use, as 'port-config-label'. If you plan to run your clustering nodes on different physical machines, this parameter is irrelevant, and you should not use it. However, if you install two (or more) nodes of your cluster on the same physical machine, you need to give the value corresponding to a specific "server" configurations in the binding manager configuration file. JBoss AS ships "out-of-the-box" with several pre-configured port ranges: 'ports-default', 'ports-01', 'ports-02', 'ports-03'. Use one of these. If -Dports is not specified, the clustered instance created this way will fall over to the default port range for a JBoss instace. More details about the binding management service can be found in the Application Server documentation, at the following address http://docs.jboss.com/jbossas/guides/j2eeguide/r2/en/html_single/#ch10.bindingmanager
db-name is the name of the database you want to create the configurations for. Supported database names are: mysql, oracle, postgresql, mssql, and sybase. Notice that if you create database configuration to any database other than MySQL, you will still need to manually install the database JDBC drivers (MySQL drivers are provided as part of the distribution).

Notice that you should have environment variable JBOSS_HOME correctly set to point to your JBoss AS distribution directory before executing any of the scripts.

For example, in order to create the configuration for a four-node cluster intended to run on the same physical machine, use the following sequence:

ant -f release-admin.xml cluster-node
ant -f release-admin.xml -Did=1 -Dports=ports-01 cluster-node
ant -f release-admin.xml -Did=2 -Dports=ports-02 cluster-node
ant -f release-admin.xml -Did=3 -Dports=ports-03 cluster-node

The sequence will create four cluster node configurations ("messaging-node0", "messaging-node1", "messaging-node2" and "messaging-node3").

The first command will create a cluster node with ID equals to '0' and using the default JBoss AS port assignments.

Warning

The configuration that has just been created uses a generic mysql service descriptor. Check $JBOSS_HOME/server/messaging-node<id>/deploy/mysql-ds.xml and verify that that:

1. Your database is indeed mysql.
2. It is accessible from every physical node you installed Messaging on.
3. Contains a schema (database/tablespace) named 'messaging'.
4. The URL (hostname and port), username and password are correct.
5. The installed mysql-driver.jar's version maches your database.

To start the cluster, from four different terminals, run:

cd $JBOSS_HOME/bin
./run.sh -c messaging-node0

cd $JBOSS_HOME/bin
./run.sh -c messaging-node1

cd $JBOSS_HOME/bin
./run.sh -c messaging-node2

cd $JBOSS_HOME/bin
./run.sh -c messaging-node3

A successful two node cluster startup produces a log similar to:

Node 0:

...

00:24:04,796 WARN  [JDBCPersistenceManager]

JBoss Messaging Warning:
   DataSource connection transaction isolation should be READ_COMMITTED, but it
   is currently REPEATABLE_READ.
  Using an isolation level less strict than READ_COMMITTED may lead to data
   consistency problems.
  Using an isolation level more strict than READ_COMMITTED may lead to deadlock.

00:24:05,718 INFO  [ServerPeer] JBoss Messaging 1.2.0.CR1 server [0] started
00:24:06,328 INFO  [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.1:2452
-------------------------------------------------------
00:24:08,406 INFO  [DefaultClusteredPostOffice] ClusteredPostOffice
[0:Clustered JMS:127.0.0.1:2452] got new view [127.0.0.1:2452|0] [127.0.0.1:2452]
00:24:08,468 INFO  [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.1:2455
-------------------------------------------------------
00:24:10,906 INFO  [ConnectionFactory] Connector socket://10.11.14.105:4457 has leasing
enabled, lease period 10000 milliseconds
00:24:10,921 INFO  [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory,
java:/ConnectionFactory, java:/XAConnectionFactory] started
00:24:10,953 INFO  [QueueService] Queue[/queue/DLQ] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:10,953 INFO  [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:10,953 INFO  [TopicService] Topic[/topic/testTopic] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:10,953 INFO  [TopicService] Topic[/topic/securedTopic] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:10,968 INFO  [TopicService] Topic[/topic/testDurableTopic] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:10,968 INFO  [QueueService] Queue[/queue/testQueue] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:10,968 INFO  [QueueService] Queue[/queue/A] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:10,968 INFO  [QueueService] Queue[/queue/B] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:10,968 INFO  [QueueService] Queue[/queue/C] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:10,968 INFO  [QueueService] Queue[/queue/D] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:10,968 INFO  [QueueService] Queue[/queue/ex] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:10,984 INFO  [QueueService] Queue[/queue/PrivateDLQ] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:10,984 INFO  [QueueService] Queue[/queue/PrivateExpiryQueue] started,
fullSize=75000, pageSize=2000, downCacheSize=2000
00:24:10,984 INFO  [QueueService] Queue[/queue/QueueWithOwnDLQAndExpiryQueue] started,
fullSize=75000, pageSize=2000, downCacheSize=2000
00:24:10,984 INFO  [TopicService] Topic[/topic/TopicWithOwnDLQAndExpiryQueue] started,
fullSize=75000, pageSize=2000, downCacheSize=2000
00:24:10,984 INFO  [QueueService] Queue[/queue/QueueWithOwnRedeliveryDelay] started,
fullSize=75000, pageSize=2000, downCacheSize=2000
00:24:10,984 INFO  [TopicService] Topic[/topic/TopicWithOwnRedeliveryDelay] started,
fullSize=75000, pageSize=2000, downCacheSize=2000
00:24:11,000 INFO  [QueueService] Queue[/queue/testDistributedQueue] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:11,000 INFO  [TopicService] Topic[/topic/testDistributedTopic] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:24:11,093 INFO  [ConnectionFactoryBindingService] Bound
ConnectionManager'jboss.jca:name=JmsXA,service=ConnectionFactoryBinding' to JNDI
name 'java:JmsXA'
00:24:11,375 INFO  [TomcatDeployer] deploy, ctxPath=/jmx-console,
warUrl=.../deploy/jmx-console.war/
00:24:12,171 INFO  [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
00:24:12,421 INFO  [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
00:24:12,453 INFO  [JkMain] Jk running ID=0 time=0/47  config=null
00:24:12,515 INFO  [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0
date=200611221632)]
Started in 30s:375ms

00:27:21,343 INFO  [DefaultClusteredPostOffice] ClusteredPostOffice
[0:Clustered JMS:127.0.0.1:2452] got new view [127.0.0.1:2452|1]
[127.0.0.1:2452, 127.0.0.1:2474]

Node 1:


...

00:33:54,468 WARN  [JDBCPersistenceManager]

JBoss Messaging Warning:
DataSource connection transaction isolation should be READ_COMMITTED, but it is
currently REPEATABLE_READ.
Using an isolation level less strict than READ_COMMITTED may lead to data consistency
problems.
Using an isolation level more strict than READ_COMMITTED may lead to deadlock.

00:33:55,062 INFO  [ServerPeer] JBoss Messaging 1.2.0.CR1 server [1] started
00:33:55,609 INFO  [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.1:2514
-------------------------------------------------------
00:33:57,734 INFO  [DefaultClusteredPostOffice]
ClusteredPostOffice[1:Clustered JMS:127.0.0.1:2514] got new
view [127.0.0.1:2452|3] [127.0.0.1:2452, 127.0.0.1:2514]
00:33:57,765 INFO  [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.1:2519
-------------------------------------------------------
00:34:00,203 INFO  [ConnectionFactory] Connector socket://10.11.14.105:4557 has leasing
enabled, lease period 20000 milliseconds
00:34:00,203 INFO  [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory,
java:/ConnectionFactory, java:/XAConnectionFactory] started
00:34:00,234 INFO  [QueueService] Queue[/queue/DLQ] started, fullSize=75000, pageSize=2000,
downCacheSize=2000
00:34:00,234 INFO  [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:34:00,234 INFO  [TopicService] Topic[/topic/testTopic] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:34:00,250 INFO  [TopicService] Topic[/topic/securedTopic] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:34:00,250 INFO  [TopicService] Topic[/topic/testDurableTopic] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:34:00,250 INFO  [QueueService] Queue[/queue/testQueue] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:34:00,250 INFO  [QueueService] Queue[/queue/A] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:34:00,250 INFO  [QueueService] Queue[/queue/B] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:34:00,250 INFO  [QueueService] Queue[/queue/C] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:34:00,250 INFO  [QueueService] Queue[/queue/D] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:34:00,250 INFO  [QueueService] Queue[/queue/ex] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:34:00,265 INFO  [QueueService] Queue[/queue/PrivateDLQ] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
00:34:00,265 INFO  [QueueService] Queue[/queue/PrivateExpiryQueue] started,
fullSize=75000, pageSize=2000, downCacheSize=2000
00:34:00,265 INFO  [QueueService] Queue[/queue/QueueWithOwnDLQAndExpiryQueue]
started, fullSize=75000, pageSize=2000, downCacheSize=2000
00:34:00,265 INFO  [TopicService] Topic[/topic/TopicWithOwnDLQAndExpiryQueue]
started, fullSize=75000, pageSize=2000, downCacheSize=2000
00:34:00,265 INFO  [QueueService] Queue[/queue/QueueWithOwnRedeliveryDelay]
started, fullSize=75000, pageSize=2000, downCacheSize=2000
00:34:00,265 INFO  [TopicService] Topic[/topic/TopicWithOwnRedeliveryDelay]
started, fullSize=75000, pageSize=2000, downCacheSize=2000
00:34:00,296 INFO  [QueueService] Queue[/queue/testDistributedQueue]
started, fullSize=75000, pageSize=2000, downCacheSize=2000
00:34:00,296 INFO  [TopicService] Topic[/topic/testDistributedTopic]
started, fullSize=75000, pageSize=2000, downCacheSize=2000
00:34:00,343 INFO  [ConnectionFactoryBindingService] Bound
ConnectionManager 'jboss.jca:name=JmsXA,
service=ConnectionFactoryBinding' to JNDI name 'java:JmsXA'
00:34:00,453 INFO  [TomcatDeployer] deploy, ctxPath=/jmx-console,
warUrl=.../deploy/jmx-console.war/
00:34:00,796 INFO  [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8180
00:34:01,078 INFO  [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8109
00:34:01,125 INFO  [JkMain] Jk running ID=0 time=0/125  config=null
00:34:01,125 INFO  [Server] JBoss (MX MicroKernel)
[4.0.5.GA (build: CVSTag=Branch_4_0 date=200611221632)] Started in 22s:547ms

Note

The installation script may fail while installing Messaging with source-generated JBoss 4.0.5.GA-ejb3 instance. This is because release-admin.xml relies on finding $JBOSS_HOME/docs/examples/binding-manager/sample-bindings.xml. 4.0.5.GA-ejb3 installations seem not to have a "docs" sub-directory. A very simple work-around for this situation is to recursively copy the "docs" sub-directory available under a regular (non-EJB3) source-generated 4.0.5.GA instance and retry the installation process.

Prev	Up	Next
Chapter 5. JBoss Messaging Non-Clustered Installation	Home	Chapter 7. Running the Examples