-
1. Re: Clustering JBoss Messaging without Shared Database?
clebert.suconic Jun 17, 2008 8:26 PM (in response to ebenezersamuel)If you don't use Persistent messages, maybe you could use the Null-Persistence or HSQLDB?
-
2. Re: Clustering JBoss Messaging without Shared Database?
ebenezersamuel Jun 17, 2008 9:02 PM (in response to ebenezersamuel)Is there a link which tells how it can be done. We are not really concerned about persistent messages.
The 1.4 Messaging guide says that we need a shared database. How do I configure it so that I dont have to use the shared database.
Ebe -
3. Re: Clustering JBoss Messaging without Shared Database?
clebert.suconic Jun 17, 2008 9:10 PM (in response to ebenezersamuel)You need a shared database to guarantee delivery of persistent messages during failover, but if you don't have persistent messages, you should not have a problem.
On our examples, with our distribution, you will find several -persistence-service.xml. Look at null-persistence-service.xml.
Just replace that by the current -persistence.service.xml under your deployment.
Note: Even with Non Persistent Messages, we could still persist them if you produce more messages than you could consume (Paging). Make sure you are consuming your messages properly. -
4. Re: Clustering JBoss Messaging without Shared Database?
ebenezersamuel Jun 17, 2008 9:21 PM (in response to ebenezersamuel)Note: Even with Non Persistent Messages, we could still persist them if you produce more messages than you could consume (Paging). Make sure you are consuming your messages properly
But wouldnt load balancing take care of this? I mean when I have other consumers in different nodes in the cluster, wouldnt they consume the excess messages? Just curious :)
Thanks,
Ebe -
5. Re: Clustering JBoss Messaging without Shared Database?
ebenezersamuel Jun 18, 2008 10:51 AM (in response to ebenezersamuel)On our examples, with our distribution, you will find several -persistence-service.xml. Look at null-persistence-service.xml.
I searched in your distribution (jboss-messaging-1.4.0.SP3) and was able to fine several xxx-persistence-service.xml; however, I was not able to find the null-persistence-service.xml. Am I looking at the wrong place. I am using Messaging 1.4.0 SP3. I was looking at jira (http://jira.jboss.org/jira/browse/JBMESSAGING-1250) and Tim has told that the file is available in src/etc/server/default/deploy/null-persistence-service.xml and so I downloaded the source distribution and still was not able to find the file.Just replace that by the current -persistence.service.xml under your deployment.
When I find it, do I have to replace null-persistence-service.xml with the current mysql-persistence-service.xml or should I replace the current mysql-persistence-service.xml with null-persistence-service.xml?
Thanks,
Ebe -
6. Re: Clustering JBoss Messaging without Shared Database?
timfox Jun 18, 2008 1:31 PM (in response to ebenezersamuel)If you look at the JIRA it says fix version 1.4.0.SP3_CP02.
That means, you won't have it in 1.4.0.SP3 since 1.4.0.SP3 comes before 1.4.0.SP3_CP02 -
7. Re: Clustering JBoss Messaging without Shared Database?
ebenezersamuel Jun 18, 2008 3:24 PM (in response to ebenezersamuel)Hi Tim,
I was unable to find the download for 1.4.0.SP3_CP02 and that is why I thought it 1.4.0.SP3 and 1.4.0.SP3_CP02 were the same.
I looked at the http://www.jboss.org/jbossmessaging/downloads/
and I was unable to find the specified version. I even looked for 1.4.1.CR1 and was not able to see it.
Do I have to download the source from somewhere and do a manual build?
Before raising my hand for help, I always like to try things out; this time, I looked at some old posts for example http://jira.jboss.org/jira/browse/JBMESSAGING-1266 and from what Andrei Martchouk told in the last commentTim, thanks for the very quick fix.
We build it from subversion and tested, it works very well.
Are there any chance to get the fix officially included into a community release? Or is it scheduled ONLY for EAP as you mentioned? We use comunity versions , but we prefer to use the official jboss builds.
I figured that I had to download the distribution from svn. Therefore, I downloaded JBM 1.4.0.SP3_CP02 version from the svn branch http://anonsvn.jboss.org/repos/messaging/tags/.
After this, in command prompt, I went to the directory where I had downloaded and ran the build file by typing "ant". The result: I have got two directories 1) thirdparty and 2)output.
I am stuck at this point. I would like to build it and get a binary distribution like in 1.4.0.SP3 in the download link http://www.jboss.org/jbossmessaging/downloads/. I would appreciate any help on this.
Thanks,
Ebe -
8. Re: Clustering JBoss Messaging without Shared Database?
ataylor Jun 19, 2008 3:33 AM (in response to ebenezersamuel)'ant release-bundle' will build you a full release.
-
9. Re: Clustering JBoss Messaging without Shared Database?
timfox Jun 19, 2008 5:06 AM (in response to ebenezersamuel)"ebenezerlovelin" wrote:
Hi Tim,
I was unable to find the download for 1.4.0.SP3_CP02 and that is why I thought it 1.4.0.SP3 and 1.4.0.SP3_CP02 were the same.
CP stands for "cumulative patch".
CP binary releases are available to our paying support customers who get them first, you can always build them from source though if you want. If you have a support contract you'll have access to them.
Eventually, when we have some time, we'll get around to creating a new community version with these changes/fixes in too. -
10. Re: Clustering JBoss Messaging without Shared Database?
ebenezersamuel Jun 19, 2008 12:33 PM (in response to ebenezersamuel)'ant release-bundle' will build you a full release.
Thanks Andy; I was able to build it accordingly. However, I face a little (?) problem when starting the two server. I have described it below
CP stands for "cumulative patch".
CP binary releases are available to our paying support customers who get them first, you can always build them from source though if you want. If you have a support contract you'll have access to them.
Thanks Tim, for the reply. I have spoken to my boss about the support contract.
Now my issue is this;
I built the JBM 1.4.0.SP3_CP02. I have two instances of messaging in two physical machines. I wanted a null persistence approach and so, I used null-persistence-service.xml. I removed the hssqldb-persistence-service.xml. I did not bother about configuring a datasource (skipped those steps in the messaging guide since I was going for null-persistence approach)Configure a JCA datasource using an example from $JBOSS_HOME/docs/examples/jca and copying to $JBOSS_CONFIG/deploy JBoss Messaging uses DefaultDS by default so you should configure your datasource to bind to that Remove hsqldb-ds.xml from $JBOSS_CONFIG/deploy Copy your database driver to $JBOSS_CONFIG/lib
messaging-node0 is in machine 1; the Server Peer ID is 0
messaging-node1 is in machine 2; the Server Peer ID is 1
The application server version is 4.2.2.GA
JBoss Remoting jar version is 2.2.2.SP7-brew is used
Now, after completing the installation, I started instance 1 (messaging-node0 using run -b 0.0.0.0 -c messaging-node0) in machine 1 and it started with out any issue.
When I tried starting the instance 2 (messaging-node1 using run -b 0.0.0.0 -c messaging-node1) in machine 2, the server gives error.
I even changed the order in which the instances were started i.e., started instance 2 first and it started with out any issue. When I start instance 1 next, this gives error. Always, the instance that is being started second, gives the error.
The error occurs when trying to start the "testDistributedQueue". All the other queues and topics (including the "testDistributedTopic) starts with out any issue. I have pasted the error message that I received in the server console in instance 2.
The actual error is this
12:26:46,294 ERROR [ExceptionUtil] Queue[null, name=testDistributedQueue] startService
java.lang.IllegalStateException: Channel id map for node 0 already contains binding for queue 12
Please help...
Thanks,
Ebe
The console outputC:\Documents and Settings\esamuel>run -b 192.168.200.151 -c messaging-node0 =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: C:\Java\POC_2\jboss-4.2.2.GA JAVA: C:\Java\Java\jdk1.5.0_15\bin\java JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 CLASSPATH: C:\Java\Java\jdk1.5.0_15\lib\tools.jar;C:\Java\POC_2\jboss-4.2.2.GA\bin\run.jar =============================================================================== 12:26:25,700 INFO [Server] Starting JBoss (MX MicroKernel)... 12:26:25,700 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) 12:26:25,700 INFO [Server] Home Dir: C:\Java\POC_2\jboss-4.2.2.GA 12:26:25,700 INFO [Server] Home URL: file:/C:/Java/POC_2/jboss-4.2.2.GA/ 12:26:25,700 INFO [Server] Patch URL: null 12:26:25,700 INFO [Server] Server Name: messaging-node0 12:26:25,700 INFO [Server] Server Home Dir: C:\Java\POC_2\jboss-4.2.2.GA\server\messaging-node0 12:26:25,700 INFO [Server] Server Home URL: file:/C:/Java/POC_2/jboss-4.2.2.GA/server/messaging-node0/ 12:26:25,700 INFO [Server] Server Log Dir: C:\Java\POC_2\jboss-4.2.2.GA\server\messaging-node0\log 12:26:25,700 INFO [Server] Server Temp Dir: C:\Java\POC_2\jboss-4.2.2.GA\server\messaging-node0\tmp 12:26:25,700 INFO [Server] Root Deployment Filename: jboss-service.xml 12:26:25,966 INFO [ServerInfo] Java version: 1.5.0_15,Sun Microsystems Inc. 12:26:25,966 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_15-b04,Sun Microsystems Inc. 12:26:25,966 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 12:26:26,544 INFO [Server] Core system initialized 12:26:29,528 INFO [WebService] Using RMI server codebase: http://192.168.200.151:8083/ 12:26:29,528 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml 12:26:30,325 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 12:26:30,325 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 12:26:31,106 INFO [TransactionManagerService] Starting recovery manager 12:26:31,200 INFO [TransactionManagerService] Recovery manager started 12:26:31,200 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference 12:26:34,700 INFO [EJB3Deployer] Starting java:comp multiplexer 12:26:36,419 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its passwor d changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this. 12:26:36,434 INFO [ServerPeer] JBoss Messaging 1.4.0.SP3-CP02 server [0] started 12:26:36,919 INFO [STDOUT] ------------------------------------------------------- GMS: address is 192.168.200.151:4204 ------------------------------------------------------- 12:26:38,997 INFO [GroupMember] org.jboss.messaging.core.impl.postoffice.GroupMember$ControlMembershipListener@15925c0 got new view [192.168.200.124:2388|1] [192.168.200.124:2388, 192.168.200.151:420 4], old view is null 12:26:38,997 INFO [GroupMember] I am (192.168.200.151:4204) 12:26:38,997 INFO [GroupMember] New Members : 2 ([192.168.200.124:2388, 192.168.200.151:4204]) 12:26:38,997 INFO [GroupMember] All Members : 2 ([192.168.200.124:2388, 192.168.200.151:4204]) 12:26:39,716 INFO [STDOUT] ------------------------------------------------------- GMS: address is 192.168.200.151:7900 ------------------------------------------------------- 12:26:44,153 INFO [ConnectionFactory] Connector bisocket://192.168.200.151:4557 has leasing enabled, lease period 10000 milliseconds 12:26:44,169 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@109dcbb started 12:26:44,309 INFO [ConnectionFactory] Connector bisocket://192.168.200.151:4557 has leasing enabled, lease period 10000 milliseconds 12:26:44,309 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1360c93 started 12:26:45,903 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its passwor d changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this. 12:26:46,247 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its passwor d changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this. 12:26:46,262 INFO [ConnectionFactory] Connector bisocket://192.168.200.151:4557 has leasing enabled, lease period 10000 milliseconds 12:26:46,262 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@a8a314 started 12:26:46,262 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,262 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,262 INFO [TopicService] Topic[/topic/testTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,262 INFO [TopicService] Topic[/topic/securedTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,278 INFO [TopicService] Topic[/topic/testDurableTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,278 INFO [QueueService] Queue[/queue/testQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,278 INFO [QueueService] Queue[/queue/A] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,278 INFO [QueueService] Queue[/queue/B] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,278 INFO [QueueService] Queue[/queue/C] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,278 INFO [QueueService] Queue[/queue/D] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,278 INFO [QueueService] Queue[/queue/ex] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,278 INFO [QueueService] Queue[/queue/PrivateDLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,278 INFO [QueueService] Queue[/queue/PrivateExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,278 INFO [QueueService] Queue[/queue/QueueWithOwnDLQAndExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,278 INFO [TopicService] Topic[/topic/TopicWithOwnDLQAndExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,278 INFO [QueueService] Queue[/queue/QueueWithOwnRedeliveryDelay] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,294 INFO [TopicService] Topic[/topic/TopicWithOwnRedeliveryDelay] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:46,294 ERROR [ExceptionUtil] Queue[null, name=testDistributedQueue] startService java.lang.IllegalStateException: Channel id map for node 0 already contains binding for queue 12 at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBindingInMemory(MessagingPostOffice.java:2380) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.internalAddBinding(MessagingPostOffice.java:1868) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBinding(MessagingPostOffice.java:449) at org.jboss.jms.server.destination.QueueService.startService(QueueService.java:126) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196) at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595) 12:26:46,809 WARN [ServiceController] Problem starting service jboss.messaging.destination:service=Queue,name=testDistributedQueue java.lang.IllegalStateException: Channel id map for node 0 already contains binding for queue 12 at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBindingInMemory(MessagingPostOffice.java:2380) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.internalAddBinding(MessagingPostOffice.java:1868) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBinding(MessagingPostOffice.java:449) at org.jboss.jms.server.destination.QueueService.startService(QueueService.java:126) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196) at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595) 12:26:47,387 INFO [TopicService] Topic[/topic/testDistributedTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:26:47,966 INFO [STDOUT] ------------------------------------------------------- GMS: address is 192.168.200.151:4215 ------------------------------------------------------- 12:26:48,044 INFO [TreeCache] viewAccepted(): [192.168.200.104:4789|479] [192.168.200.104:4789, 192.168.200.21:11321, 192.168.200.124:2394, 192.168.200.151:4215] 12:26:48,059 INFO [TreeCache] TreeCache local address is 192.168.200.151:4215 12:26:48,059 INFO [TreeCache] received the state (size=1024 bytes) 12:26:48,091 INFO [TreeCache] state was retrieved successfully (in 32 milliseconds) 12:26:48,091 INFO [TreeCache] parseConfig(): PojoCacheConfig is empty 12:26:48,184 INFO [STDOUT] no object for null 12:26:48,184 INFO [STDOUT] no object for null 12:26:48,200 INFO [STDOUT] no object for null 12:26:48,216 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType 12:26:48,231 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType 12:26:50,262 INFO [NativeServerConfig] JBoss Web Services - Native 12:26:50,262 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=200710210837) 12:26:50,919 INFO [SnmpAgentService] SNMP agent going active 12:26:51,325 INFO [DefaultPartition] Initializing 12:26:51,372 INFO [STDOUT] ------------------------------------------------------- GMS: address is 192.168.200.151:4221 ------------------------------------------------------- 12:27:03,934 INFO [DefaultPartition] Number of cluster members: 4 12:27:08,341 INFO [DefaultPartition] Other members: 3 12:27:08,341 INFO [DefaultPartition] Fetching state (will wait for 30000 milliseconds): 12:27:11,044 INFO [DefaultPartition] state was retrieved successfully (in 2703 milliseconds) 12:27:12,200 INFO [HANamingService] Started ha-jndi bootstrap jnpPort=1100, backlog=50, bindAddress=/192.168.200.151 12:27:12,200 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on /192.168.200.151:1102, group=230.0.0.4, HA-JNDI address=192.168.200.151:1100 12:27:12,356 INFO [TreeCache] No transaction manager lookup class has been defined. Transactions cannot be used 12:27:12,466 INFO [STDOUT] ------------------------------------------------------- GMS: address is 192.168.200.151:4231 ------------------------------------------------------- 12:27:12,528 INFO [TreeCache] viewAccepted(): [192.168.200.104:4809|462] [192.168.200.104:4809, 192.168.200.21:11326, 192.168.200.124:2409, 192.168.200.151:4231] 12:27:12,528 INFO [TreeCache] TreeCache local address is 192.168.200.151:4231 12:27:12,622 INFO [STDOUT] ------------------------------------------------------- GMS: address is 192.168.200.151:4236 ------------------------------------------------------- 12:27:12,684 INFO [TreeCache] viewAccepted(): [192.168.200.104:4814|462] [192.168.200.104:4814, 192.168.200.21:11328, 192.168.200.124:2415, 192.168.200.151:4236] 12:27:12,684 INFO [TreeCache] TreeCache local address is 192.168.200.151:4236 12:27:13,200 INFO [CorbaNamingService] Naming: [IOR:000000000000002B49444C3A6F6D672E6F72672F436F734E616D696E672F4E616D696E67436F6E746578744578743A312E3000000000000200000000000001000001020000000010313 9322E3136382E3230302E313531000DC80000000000114A426F73732F4E616D696E672F726F6F74000000000000050000000000000008000000004A414300000000010000001C00000000000100010000000105010001000101090000000105010001000 000210000007400000000000000010000000000000024000000220000007E0000000000000001000000103139322E3136382E3230302E313531000DC90040000000000000000806066781020101010000001704010008060667810201010100000007646 56661756C7400000000000000000000000000000000000000002000000004000000000000001F0000000400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003] 12:27:13,294 INFO [CorbaTransactionService] TransactionFactory: [IOR:000000000000003049444C3A6F72672F6A626F73732F746D2F69696F702F5472616E73616374696F6E466163746F72794578743A312E3000000000020000000000 00010000010200000000103139322E3136382E3230302E313531000DC80000000000144A426F73732F5472616E73616374696F6E732F46000000050000000000000008000000004A414300000000010000001C0000000000010001000000010501000100 0101090000000105010001000000210000007400000000000000010000000000000024000000220000007E0000000000000001000000103139322E3136382E3230302E313531000DC9004000000000000000080606678102010101000000170401000806 066781020101010000000764656661756C7400000000000000000000000000000000000000002000000004000000000000001F0000000400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003] 12:27:13,684 INFO [Embedded] Catalina naming disabled 12:27:13,872 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Java\Java\jdk1.5.0_15\ bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Java\POC_2\jboss-4.2.2.GA\bin;C:\Java\Java\jdk1.5.0_15\bin;C:\Java\apache-ant-1.7.0\bin;C:\Program Files \MySQL\MySQL Server 5.0\bin;C:\Java\apache-maven-2.0.9-bin\apache-maven-2.0.9\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Java\POC_2\jboss-4.2.2.GA\bin;C:\Java\Java\jdk1.5.0_15\bin; C:\Java\apache-ant-1.7.0\bin;C:\Program Files\MySQL\MySQL Server 5.0\bin 12:27:14,091 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-192.168.200.151-8080 12:27:14,106 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-192.168.200.151-8009 12:27:14,106 INFO [Catalina] Initialization processed in 420 ms 12:27:14,106 INFO [StandardService] Starting service jboss.web 12:27:14,106 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA 12:27:14,153 INFO [Catalina] Server startup in 55 ms 12:27:14,309 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/ 12:27:15,137 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/httpha-invoker.sar/invoker.war/ 12:27:15,247 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/ 12:27:15,403 INFO [TomcatDeployer] deploy, ctxPath=/juddi, warUrl=.../deploy/juddi-service.sar/juddi.war/ 12:27:15,559 INFO [RegistryServlet] Loading jUDDI configuration. 12:27:15,559 INFO [RegistryServlet] Resources loaded from: /WEB-INF/juddi.properties 12:27:15,559 INFO [RegistryServlet] Initializing jUDDI components. 12:27:15,981 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/ 12:27:16,434 INFO [MailService] Mail Service bound to java:/Mail 12:27:16,575 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar 12:27:16,622 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar 12:27:16,653 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar 12:27:16,981 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar 12:27:17,091 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms-ra.rar 12:27:17,122 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar 12:27:17,169 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar 12:27:17,169 INFO [QuartzResourceAdapter] start quartz!!! 12:27:17,231 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main 12:27:17,262 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created. 12:27:17,262 INFO [RAMJobStore] RAMJobStore initialized. 12:27:17,262 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties' 12:27:17,262 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2 12:27:17,262 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 12:27:17,497 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA' 12:27:17,903 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 12:27:18,091 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/ 12:27:18,278 INFO [FarmMemberService] **** pullNewDeployments **** 12:27:18,278 INFO [ClusterFileTransfer] Start pull of file cluster-examples-service.xml from cluster. 12:27:18,294 INFO [ClusterFileTransfer] Finished cluster pull of file cluster-examples-service.xml to cluster-examples-service.xml 12:27:18,341 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.messaging.destination:service=Queue,name=testDistributedQueue State: FAILED Reason: java.lang.IllegalStateException: Channel id map for node 0 already contains binding for queue 12 I Depend On: jboss.messaging:service=ServerPeer jboss.messaging:service=PostOffice --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.messaging.destination:service=Queue,name=testDistributedQueue State: FAILED Reason: java.lang.IllegalStateException: Channel id map for node 0 already contains binding for queue 12 I Depend On: jboss.messaging:service=ServerPeer jboss.messaging:service=PostOffice 12:27:18,450 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-192.168.200.151-8080 12:27:18,684 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-192.168.200.151-8009 12:27:18,700 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 53s:0ms
-
11. Re: Clustering JBoss Messaging without Shared Database?
timfox Jun 20, 2008 4:12 AM (in response to ebenezersamuel)Hmm something fishy here, you say you have started instance 2, which according to what you said in your post should have a server peer id of 1, but the console output you posted says:
12:26:36,434 INFO [ServerPeer] JBoss Messaging 1.4.0.SP3-CP02 server [0] started
Which tells me it thinks its id is 0og.info("JBoss Messaging " + getVersion().getProviderVersion() + " server [" + getServerPeerID()+ "] started");
So probably you haven't configured the nodes with unique ids. -
12. Re: Clustering JBoss Messaging without Shared Database?
ebenezersamuel Jun 20, 2008 9:00 AM (in response to ebenezersamuel)Hi Tim,
I posted the code of the second test; I had started the second (node 1) first, which started fine and then I started the first instance (node 0).
From my previous post...
I even changed the order in which the instances were started i.e., started instance 2 first and it started with out any issue. When I start instance 1 next, this gives error. Always, the instance that is being started second, gives the error.
I apologize for the confusion caused.
Thanks,
Ebe -
13. Re: Clustering JBoss Messaging without Shared Database?
ebenezersamuel Jun 20, 2008 10:15 AM (in response to ebenezersamuel)Hi Tim,
In messaging-service.xml,
Node 0 has<attribute name="ServerPeerID">${jboss.messaging.ServerPeerID:0}</attribute>
and Node 1 has<attribute name="ServerPeerID">${jboss.messaging.ServerPeerID:1}</attribute>
That is the only place where I have configured the server peer ID; do I have to configure it else where?
Thanks,
Ebe -
14. Re: Clustering JBoss Messaging without Shared Database?
ebenezersamuel Jun 21, 2008 1:05 PM (in response to ebenezersamuel)Have I done something wrong in my configuration some where? I followed the 1.4 guide. Instead of hssqldb-persistence-service.xml, I have used null-persistence-service.xml.
The remoting version is 2.2.2.SP7.
I would apppreciat any help.
Thanks,
Ebe