This content has been marked as final.
Show 4 replies
-
1. Re: Improvement suggestions: Messaging in a clustered enviro
adrian.brock Apr 1, 2009 9:53 AM (in response to frankthetank)bind.address:1100 should always be able to see things bound into jndi somewhere in the cluster.
Improvements:
* Use hajndi-jms-ds.xml to create a pool of connections (this is what is used in the "all" config anyway) bound at connection factory java:/JmsXA.
* Use jndi tricks to use the in-memory connector when co-located with the server
in which the singleton jms server is running<mbean code="org.jboss.naming.LinkRefPairService" name="jboss.jms:alias=MyConnectionFactory"> <!-- jndi binding MyConnectionFactory --> <attribute name="JndiName">MyConnectionFactory</attribute> <!-- Use TCP/IP when remote --> <attribute name="RemoteJndiName">ConnectionFactory</attribute> <!-- Use the in-memory connector when local --> <attribute name="LocalJndiName">java:/ConnectionFactory</attribute> <depends>jboss:service=Naming</depends> </mbean>
* Use JBoss Messaging to get a proper clustered solution -
2. Re: Improvement suggestions: Messaging in a clustered enviro
frankthetank Apr 2, 2009 12:02 PM (in response to frankthetank)"adrian@jboss.org" wrote:
bind.address:1100 should always be able to see things bound into jndi somewhere in the cluster.
Yes, it works with bind.addres.
I was just mentioning that the example uses 'localhost' which would lead to false results if JBoss is bound to a different address."adrian@jboss.org" wrote:
* Use JBoss Messaging to get a proper clustered solution
Would this save me the hassle of doing all the below?"adrian@jboss.org" wrote:
Improvements:
* Use hajndi-jms-ds.xml to create a pool of connections (this is what is used in the "all" config anyway) bound at connection factory java:/JmsXA.
Might you have an example for this?
Or need I not do anything except use it (java:/JmsXA) instead of ConnectionFactory?"adrian@jboss.org" wrote:
* Use jndi tricks to use the in-memory connector when co-located with the server
in which the singleton jms server is running<mbean code="org.jboss.naming.LinkRefPairService" name="jboss.jms:alias=MyConnectionFactory"> <!-- jndi binding MyConnectionFactory --> <attribute name="JndiName">MyConnectionFactory</attribute> <!-- Use TCP/IP when remote --> <attribute name="RemoteJndiName">ConnectionFactory</attribute> <!-- Use the in-memory connector when local --> <attribute name="LocalJndiName">java:/ConnectionFactory</attribute> <depends>jboss:service=Naming</depends> </mbean>
Thanks for the help! -
3. Re: Improvement suggestions: Messaging in a clustered enviro
adrian.brock Apr 6, 2009 10:17 AM (in response to frankthetank)"FrankTheTank" wrote:
* Use hajndi-jms-ds.xml to create a pool of connections (this is what is used in the "all" config anyway) bound at connection factory java:/JmsXA.
Might you have an example for this?
Its in docs/examples/jca in the jboss download. -
4. Re: Improvement suggestions: Messaging in a clustered enviro
frankthetank Apr 7, 2009 7:59 AM (in response to frankthetank)"adrian@jboss.org" wrote:
"FrankTheTank" wrote:
* Use hajndi-jms-ds.xml to create a pool of connections (this is what is used in the "all" config anyway) bound at connection factory java:/JmsXA.
Might you have an example for this?
Its in docs/examples/jca in the jboss download.
Great, thanks.
I have already tried out JBossMessaging for 4.2.3 and after following the guide it seems to run ok.
Two issues had popped up but I was able to resolve them.
1) each node needs a unique id.
2) I had already configured the datasources for clustering (no longer using hypersonic) and I still had to replace my *-persistence-service.xml with the one from the examples folder because of DB configuration issues.
Just a heads up for anyone that might think of doing a similar migration.
Thanks for the help!