[jboss-user] [JBoss Messaging] - Re: Understanding JBoss Messaging and SPOF (Single Point of

[timfox]

"seattle.golfer" wrote : 
  |     I've been away from JBoss for about 4+ years (working in Weblogic), and am finally coming back home.
  | 

Glad to hear it! :)

anonymous wrote : 
  |      I'm trying to get a better handle on JBoss Messaging's clustering capabilities. They way I read the documentation/installation guide, you still need to have a shared database instance. From the 1.4B1 docs, "For a clustered installation it is mandatory that a shared database is available to all nodes in the cluster."
  | 
  |       Which (to me) appears to be Single Point of Failure (SPOF). I realize the database itself could be clustered, but still.. 
  | 

Yes, JBoss Messaging 1.x uses a shared database for persistence. If it's not clustered that could provide a SPOF.

JBossMessaging 2.0, which is what we are currently at work on has major improvements in the area of persistence.

We will support:

1) Shared JDBC database  - like in 1.x
2) Unshared JDBC database per node (already working in TRUNK)
3) Unshared file based journal per node

For HA we will also support replication between nodes for a "shared nothing" approach.

Also we'll support failover via a shared file sytem (e.g., GFS over a SAN) in the case one is available.

Lots of other great new things in JBM 2.0 including a brand new super fast NIO transport using Apache MINA. (Trustin Lee the author of MINA is now a JBoss employee), and many other features.

Also see JIRA for JBM 2.0 tasks and provisional timescales. We should have a GA released towards the end of the year.

There is also a little bit more info on the jboss labs JBM project page.

JBM 2.0 is the subject of my talk at JBoss World in a couple of weeks. Why don't you come along and find out more?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125039#4125039

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125039