-
1. Re: The same node id
ataylor Jan 29, 2013 10:26 AM (in response to guangquanhao)the node id is written to th ejournal and you have probably copied this over to another server, you will need to delete your journal.
Also, you seem to have raised this discussion twice in the forum!
-
2. Re: The same node id
guangquanhao Jan 30, 2013 12:55 AM (in response to ataylor)Is the journal in the directory of ./data/journal?
-
3. Re: The same node id
ataylor Jan 30, 2013 4:24 AM (in response to guangquanhao)delete the whole data dir
-
4. Re: The same node id
drisal Feb 27, 2013 2:13 AM (in response to ataylor)Thanks Andy, this slove my problems too...
But, I want to know how could i use clustered in different machines?
-
5. Re: The same node id
ataylor Feb 27, 2013 3:11 AM (in response to drisal)But, I want to know how could i use clustered in different machines?
Im not exactly sure what you mean by this, could you be clearer please?
-
6. Re: The same node id
drisal Feb 27, 2013 7:38 AM (in response to ataylor)Hello Andy,
I have succefully run different instances of hornetq and implement balancing message load using different nodes in single machine.
But i am confuse how could i run different node in different machine using clustering with hornetq.Please tell me how broadcast group, discover group and cluster- connection works in different machine.
<broadcast-groups>
<broadcast-group name="bg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>5000</broadcast-period>
<connector-ref>netty</connector-ref>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="dg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-groups>
<cluster-connections>
<cluster-connection name="my-cluster">
<address>jms</address>
<connector-ref>netty</connector-ref>
<discovery-group-ref discovery-group-name="dg-group1"/>
</cluster-connection>
</cluster-connections>
thank you in advance.
-
7. Re: The same node id
ataylor Feb 27, 2013 7:43 AM (in response to drisal)It works exactly the same, there is no difference. If you find it isnt working then its probably a firewall issue or maybe your network doesn't support/allow multicast traffic
-
8. Re: The same node id
drisal Feb 28, 2013 11:06 PM (in response to ataylor)Hello Andy,
I'm using two different linux machine to run different node of hornetq. Both hornetq server started like as following:
In one machine:
[jboss@bvdipd1 bin]$ ./run.sh
***********************************************************************************
java -Djnp.port=1099 -Djnp.rmiPort=1098 -Djnp.host=192.168.28.123 -Dhornetq.remoting.netty.host=192.168.28.123 -Dhornetq.remoting.netty.port=5445 -Dhornetq.remoting.netty.batch.port=5455 -XX:+UseParallelGC -XX:+AggressiveOpts -XX:+UseFastAccessorMethods -Xms512M -Xmx1024M -Dhornetq.config.dir=../config/stand-alone/clustered -Djava.util.logging.config.file=../config/stand-alone/clustered/logging.properties -Djava.library.path=. -classpath ../lib/twitter4j-core.jar:../lib/netty.jar:../lib/jnpserver.jar:../lib/jnp-client.jar:../lib/jboss-mc.jar:../lib/jboss-jms-api.jar:../lib/hornetq-twitter-integration.jar:../lib/hornetq-spring-integration.jar:../lib/hornetq-logging.jar:../lib/hornetq-jms.jar:../lib/hornetq-jms-client-java5.jar:../lib/hornetq-jms-client.jar:../lib/hornetq-jboss-as-integration.jar:../lib/hornetq-core.jar:../lib/hornetq-core-client-java5.jar:../lib/hornetq-core-client.jar:../lib/hornetq-bootstrap.jar:../config/stand-alone/clustered:../schemas/ org.hornetq.integration.bootstrap.HornetQBootstrapServer hornetq-beans.xml
***********************************************************************************
[main] 07:24:42,068 INFO [org.hornetq.integration.bootstrap.HornetQBootstrapServer] Starting HornetQ Server
[main] 07:24:43,429 INFO [org.hornetq.core.server.impl.HornetQServerImpl] live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=../data/journal,bindingsDirectory=../data/bindings,largeMessagesDirectory=../data/large-messages,pagingDirectory=../data/paging)
[main] 07:24:43,430 INFO [org.hornetq.core.server.impl.HornetQServerImpl] Waiting to obtain live lock
[main] 07:24:43,475 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager] Using AIO Journal
[main] 07:24:43,499 WARNING [org.hornetq.core.server.impl.HornetQServerImpl] Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.
[main] 07:24:43,816 INFO [org.hornetq.core.server.impl.AIOFileLockNodeManager] Waiting to obtain live lock
[main] 07:24:43,817 INFO [org.hornetq.core.server.impl.AIOFileLockNodeManager] Live Server Obtained live lock
[main] 07:24:45,858 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.queue.DLQ
[main] 07:24:45,883 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.queue.ExpiryQueue
[main] 07:24:45,892 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.queue.ExampleQueue
[main] 07:24:46,026 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 192.168.28.123:5455 for CORE protocol
[main] 07:24:46,030 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 192.168.28.123:5445 for CORE protocol
[main] 07:24:46,055 INFO [org.hornetq.core.server.impl.HornetQServerImpl] Server is now live
[main] 07:24:46,058 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.2.5.Final (HQ_2_2_5_FINAL_AS7, 121) [56d2d241-5d4c-11e1-8f6d-005056b44749] started
In another machine:
[jboss@RHEL_direintegration bin]$ ./run.sh
***********************************************************************************
java -Djnp.port=1099 -Djnp.rmiPort=1098 -Djnp.host=192.168.72.11 -Dhornetq.remoting.netty.host=192.168.72.11 -Dhornetq.remoting.netty.port=4445 -Dhornetq.remoting.netty.batch.port=4455 -XX:+UseParallelGC -XX:+AggressiveOpts -XX:+UseFastAccessorMethods -Xms512M -Xmx1024M -Dhornetq.config.dir=../config/stand-alone/clustered -Djava.util.logging.config.file=../config/stand-alone/clustered/logging.properties -Djava.library.path=. -classpath ../lib/twitter4j-core.jar:../lib/netty.jar:../lib/jnpserver.jar:../lib/jnp-client.jar:../lib/jboss-mc.jar:../lib/jboss-jms-api.jar:../lib/hornetq-twitter-integration.jar:../lib/hornetq-spring-integration.jar:../lib/hornetq-logging.jar:../lib/hornetq-jms.jar:../lib/hornetq-jms-client-java5.jar:../lib/hornetq-jms-client.jar:../lib/hornetq-jboss-as-integration.jar:../lib/hornetq-core.jar:../lib/hornetq-core-client-java5.jar:../lib/hornetq-core-client.jar:../lib/hornetq-bootstrap.jar:../config/stand-alone/clustered:../schemas/ org.hornetq.integration.bootstrap.HornetQBootstrapServer hornetq-beans.xml
***********************************************************************************
[main] 17:33:19,864 INFO [org.hornetq.integration.bootstrap.HornetQBootstrapServer] Starting HornetQ Server
[main] 17:33:21,329 INFO [org.hornetq.core.server.impl.HornetQServerImpl] live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=../data/journal,bindingsDirectory=../data/bindings,largeMessagesDirectory=../data/large-messages,pagingDirectory=../data/paging)
[main] 17:33:21,329 INFO [org.hornetq.core.server.impl.HornetQServerImpl] Waiting to obtain live lock
[main] 17:33:21,371 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager] Using AIO Journal
[main] 17:33:21,769 INFO [org.hornetq.core.server.impl.AIOFileLockNodeManager] Waiting to obtain live lock
[main] 17:33:21,770 INFO [org.hornetq.core.server.impl.AIOFileLockNodeManager] Live Server Obtained live lock
[main] 17:33:33,314 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.queue.DLQ
[main] 17:33:33,342 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.queue.ExpiryQueue
[main] 17:33:33,352 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.queue.ExampleQueue
[main] 17:33:33,357 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.queue.com.bloodhound.rtn.task.DeepThoughtTask
[main] 17:33:33,371 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.queue.com.bloodhound.rtn.task.TxPersistenceTask
[main] 17:33:33,379 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.queue.com.bloodhound.rtn.task.NoOpTask
[main] 17:33:33,394 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.queue.com.bloodhound.rtn.task.RedirectTask
[main] 17:33:33,407 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.queue.com.bloodhound.rtn.task.Error
[main] 17:33:33,418 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.queue.com.bloodhound.rtn.task.CifReportingTask
[main] 17:33:33,423 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.queue.com.bloodhound.rtn.task.WhatIfSequencerTask
[main] 17:33:33,428 INFO [org.hornetq.core.server.impl.HornetQServerImpl] trying to deploy queue jms.topic.ExampleTopic
[main] 17:33:33,586 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 192.168.72.11:4455 for CORE protocol
[main] 17:33:33,588 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 192.168.72.11:4445 for CORE protocol
[main] 17:33:33,621 INFO [org.hornetq.core.server.impl.HornetQServerImpl] Server is now live
[main] 17:33:33,622 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.2.5.Final (HQ_2_2_5_FINAL_AS7, 121) [ba76bd03-80ac-11e2-9e15-005056b422be] started
Here i don't think clustered is run successfully, is it due to firewall issue or i have to change in cofiguration file?
I'm not understanding what is happening...please tell me what should i do...
Thank you in advance....
-
9. Re: The same node id
ataylor Mar 1, 2013 4:40 AM (in response to drisal)If your configuration is correct (i dont know as you havent attached it) then it will be a netwok issue, either firewall or the network doesnt support multicast traffic, i cant help you with that as its onyour network.
-
10. Re: The same node id
drisal Mar 7, 2013 2:46 AM (in response to ataylor)hello Andy,
I think its due to using two node of different network i.e. 192.168.72.11 and 192.168.28.123.
When i used two node of same network then cluster is working properly.
I think running cluster in the node of two different network is another issue..how this is solved in hornetq?
Thank you
-
11. Re: The same node id
ataylor Mar 7, 2013 3:24 AM (in response to drisal)I will refer to my last answer, If your configuration is correct (i dont know as you havent attached it) then it will be a netwok issue, either firewall or the network doesnt support multicast traffic, i cant help you with that as its onyour network.
-
12. Re: The same node id
jbansal Mar 23, 2018 5:03 PM (in response to drisal)Hi Deep,
i setup standalone cluster for hornetq, but i can not run both node at same time. could you please help me in this?
Thanks
Jitendra Bansal