Slashdot Mirror

← Back to Stories (view on slashdot.org)

Red Hat Spins Off JBoss 2.x As HornetQ

Posted by ScuttleMonkey on from the strip-mine-rename-and-release dept.

Several sources are reporting that Red Hat has spun off the 2.x release of the JBoss messaging protocol as HornetQ. The 1.x version of JBoss is still being supported in maintenance mode and will continue to be known by its original name. "HornetQ is an open source project to build a multi-protocol, embeddable, high performance, clustered, asynchronous messaging system. HornetQ is an example of Message Oriented Middleware. [...] HornetQ is designed with flexibility in mind: It's elegant POJO based design has minimal third party dependencies: Run HornetQ as a stand-alone messaging broker, run it in integrated in your favorite JEE application server, or run it embedded inside your own application. It's up to you."

4 of 50 comments (clear)

  1. Misleading by Anonymous Coward · · Score: 3, Insightful

    What a badly written and misleading headline.

  2. Does this mean the end of QPID? by Anonymous Coward · · Score: 1, Insightful

    Red Hat also makes an AMQP (Another Message Queue Protocol) broker called QPid. But it seems JBoss is much, much more successful. Does the explicit message focus in HornetQ mean that Red Hat will abandon AMQP? (Ok, it's "advanced message whatever")

  3. Lets hope they fixed the major flows from 1.x by thammoud · · Score: 3, Insightful

    In 1.x, a server would hang if a client died (OS Crash, Pull the plug). That is a cardinal sin in the world of MOM. The excuse for not fixing it in 1.x was that they were using some internal networking library. 2.x looks impressive indeed, but you know what my first will be. Pull the f'ing plug.

  4. Re:And why should we care? by Anonymous Coward · · Score: 0, Insightful

    Do you have any idea what message passing is? Any idea whatsoever? Clearly not.

    We aren't talking about fucking emails or newsgroup postings here, for the love of God. We are talking about small messages passed within nanoseconds between highly time-sensitive componentry running on mainframes.

    The latency of UUCP is fucking massive compared to that of a good message passing engine. That said, you are right, most Java software is shit, and the message queues implemented in Java are no exception.

    The best message passing engines are implemented in pure C, and are often proprietary.