View feed: JBoss Messaging Releases
Navigation
Posts of this feed on this page
- JBossMessaging 1.4.0.GA Released
- "JBossMessaging 1.4.0.CR3 Released"
- "JBossMessaging 1.4.0.CR2 Released"
- JBoss Messaging 1.4.0.CR1 released
- JBoss Messaging 1.3.0.GA released
- JBoss Messaging 1.0.1 SP5 released
- JBoss Messaging 1.2.0.GA Released
- JBoss Messaging 1.2.0.CR1 Released
- JBoss Messaging 1.0.1.SP4 Released
- JBoss Messaging 1.2.0.Beta2 Released
- (to view more posts, click the next/previous link)
Recent posts from all feeds
JBossMessaging 1.4.0.GA Released
JBoss Messaging 1.4.0.GA has been released and is available for download .
The messaging team is pleased to announce the release of JBoss Messaging 1.4.0.GA. We have worked extensively to provide a production ready product, where we have improved several aspects and fixed bugs along the way.
On the cluster side we have improved the communication between nodes, and we have also improved the way Clustered Connection Factories will receive notifications of topology changes. A Clustered Connection Factory will aways have the most updated list of nodes.
Full details of the contents can be found in the release notes.
JBoss Messaging 1.4.0 is also Java 5 only. This is because we build against JBoss AS 4.2 whose libraries are built against Java 5 only. We need to have our libraries synched up with AS 4.2 in order to be fully integrated with it.
This release requires a patched version of JBoss Remoting to operate. JBoss Remoting 2.2.2.SP1. This is available here . See the installation guide for more details
"JBossMessaging 1.4.0.CR3 Released"
JBoss Messaging 1.4.0.CR3 has been released and is available for download.
The messaging team is pleased to announce the release of JBoss Messaging 1.4.0.CR3.
This is a candidate release for JBoss Messaging 1.4.0.
Full details of the contents can be found in the release notes.
JBoss Messaging 1.4.0 is also Java 5 only. This is because we build against JBoss AS 4.2 whose libraries are built against Java 5 only. We need to have our libraries synched up with AS 4.2 in order to be fully integrated with it.
This release requires a patched version of JBoss Remoting to operate. JBoss Remoting 2.2.2.SP1. This is available here . See the installation guide for more details
"JBossMessaging 1.4.0.CR2 Released"
JBoss Messaging 1.4.0.CR2 has been released and is available for download.
The messaging team is pleased to announce the release of JBoss Messaging 1.4.0.CR2.
This is a candidate release for JBoss Messaging 1.4.0.
This release fixes several important bugs from the previous release, full details of which can be found in the release notes.
The other major changes in this release relate to improvements on the persistence and fixes on ClusteredConnectionFactories.
Before CR2 the ClusteredConnectionFactory would receive notifications only if a Connection were still alive. After CR2, every time you lookup for a new CF on the JNDI the ClusteredConnectionFactory will have a special callback to receive any topology changes from the server. The LoadBalancing and Failover will aways have the most updated info.JBoss Messaging 1.4.0 is also Java 5 only. This is because we build against JBoss AS 4.2 whose libraries are built against Java 5 only. We need to have our libraries synched up with AS 4.2 in order to be fully integrated with it.
Enjoy!
JBoss Messaging 1.4.0.CR1 released
JBoss Messaging 1.4.0.CR1 has been released and is available for download.
The messaging team is pleased to announce the release of JBoss Messaging 1.4.0.CR1.
This is a candidate release for JBoss Messaging 1.4.0.
This release fixes several important bugs from the previous release, full details of which can be found in the release notes.
The other major changes in this release relate to a simplification in clustering configuration.
The clustered and non clustered post offices have merged to give a single post office which can work both in a cluster and standalone.The cluster router and message pull policies have been completely removed since it was identified that users were having trouble configuring this properly, and frankly they were too complex too configure.
The idea from now on is that clustering should work pretty much out of the box with little or no configuration. That goal has been achieved in 1.4.0.CR1, where distributed queues and topics act as distributed queues and topics without you having to configure anything.
JBoss Messaging 1.4.0 is also Java 5 only. This is because we build against JBoss AS 4.2 whose libraries are built against Java 5 only. We need to have our libraries synched up with AS 4.2 in order to be fully integrated with it.
Enjoy!
JBoss Messaging 1.3.0.GA released
JBoss Messaging 1.3.0.GA has been released and it is available for download.
This is an important release, the main theme of which is better useability for JBoss Messaging users, and better integration in JBoss Application Server.
Previous releases of JBoss Messaging used different versions of various thirdparty jars compared to JBoss Application Server. This meant, that when running JBoss Messaging inside the app server it was either necessary to do a "scoped" deployment, where JBoss Messaging is configured to run in its own classloading domain, or to copy the newer jars into the application server, overwriting what was previously there.
Scoped deployments introduced a whole slew of issues, not least of which is they are very difficult to configure and meant that other services using JBoss Messaging had to specify the classloading domain. This resulted in a lot of headaches for our users. Overwriting jars in the application server came with its own problems and gave incompatibilties with other services e.g. EJB3 and web services, and also gave support issues since the user was now using a version of the AS with a customer configuration of jars - something that's hard to support.
Another compatibility issue we previously had was that the jboss-messaging-client.jar packaged up all its dependent libraries in it. This caused problems with users who wanted to use different versions of jars, e.g. log4j.jar.
With JBoss Messaging 1.3.0.GA, the product is no longer deployed as scoped deployment, and we now supply a thin client jar. The installation guide describes what other jars you will need on your client classpath to get it to work (not many). We have ensured that JBoss Messaging 1.3.0.GA and JBoss AS 4.2.0.GA have their dependencies all aligned, this means JBoss Messaging works smoothly with 4.2.0.GA, but also that we no longer recommend (in fact we highly recommend against) installing JBoss Messaging in earlier versions of JBoss AS. You can probably get JBoss Messaging to work in JBoss AS 4.0.x, but we don't guarantee you won't have issues with compatibility with other services, in particular clustering, EJB3 and web services.
From now on we are going to keep our dependencies aligned with the application server which will typically mean the latest version of JBoss Messaging will only work with the latest version of JBAS. This makes a lot of sense, since before very long, JBoss Messaging is going to be the default JMS provider for JBoss AS, so it will be an intrinsic part of the application server.
This release also includes many important bug fixes - please see the release notes for full details, it also includes some new functionality like an implementation of clustered JMS temporary queues.
We also have changed the clustering behaviour a little. The default connection factories at /ConnectionFactory and /XAConnectionFactory are now *non clustered*, i.e. they don't support automatic failover or automatic connection load balancing. This is to provide better compatibility with applications originally written against JBoss MQ which don't expect load-balancing or automatic failover. If you want a clustered connection factory, one is available at /ClusteredConnectionFactory, or you can deploy your own. See the userguide for more details.
We have also expanded the documentation in this release, and produced a section on how to use the message bridge, which was there in JBoss Messaging 1.2.0 but undocumented, so no-one knew how to use it!
Similarly there is a new section on how to enable XA transaction recovery with JBoss Messaging.
We have also created a couple of new examples - one demonstrating the message bridge in action, and another demonstrating using HAJNDI to talk to a clustered EJB which talks to JBoss Messaging.
The year ahead will be an exciting time for JBoss Messaging, as it will become the default JMS provider in JBoss AS, and is also a key part of Red Hat's messaging strategy - which we will have more to say about over the next few weeks!
Stay tuned, and thanks most of all to you, our users.
JBoss Messaging 1.0.1 SP5 released
JBoss Messaging 1.0.1.SP5. has been released and it is available for download.
This release is fixes several important bugs and introduces a new version of jboss remoting which fixes several remoting issues.
This will be the last public release on the 1.0 codebase. All future releases will be on the 1.2 codebase.
Release notes are available here: http://jira.jboss.com/jira/secure/ReleaseNote.jspa?projectId=12310061&styleName=Html&version=12311211
JBoss Messaging 1.2.0.GA Released
JBoss Messaging 1.2.0.GA has been released and it is available for download on jboss.org (http://labs.jboss.com/portal/jbossmessaging/downloads) and sourceforge (http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=157261).
The 1.2.0.GA release comes with too many changes to fit in this short announcement. The main achievment is that we finally we have production quality clustering with load balancing and transpartent failover. The messaging team will start blogging about the new features shortly. In the mean time, you have access to brand new User Guide, that ships with the release and it is also available on-line, for an overview of the new features.
In order to install JBM 1.2, you will need ant 1.7.0 or newer.
Please remember that 1.2 data schema is not compatible with the 1.0.x series, so in order to upgrade, you will need to either drop the 1.0 database tables, or wait for a migration tool we might write, if there is enough demand. Starting with this release, we guarantee forward and backward compatibility.
Also, keep in mind that even if this is a GA release, it is also a "0" release. It contains tremendous amounts of new functionality, which has been extensibly tested in our QA labs, but has't been battle tested, and as any programmer knows, there's no substitute for that. Use your best judgment and do plenty of back-ups before upgrading.
Enjoy.
JBoss Messaging 1.2.0.CR1 Released
JBoss Messaging 1.2.0.CR1 has been released and it is available for download on jboss.org (http://labs.jboss.com/portal/jbossmessaging/downloads) and sourceforge (http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=157261).
CR1 is functionally equivalent with Beta2, the only notable addition being the JBoss Remoting "bisocket" transport, which replaces the unidirectional "socket" as default Messaging transport. This new transport eliminates the need for a ServerSocket on the client side. Aside from that, the rest of the changes are mostly bug fixes. The complete list of the bug fixes introduced by this release is available here: http://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12310920&styleName=Html&projectId=12310061.
We will be waiting for community feedback for a while before releasing the GA, which is scheduled for the end of this month (Feb 28).
The Messaging road map is available here: http://jira.jboss.org/jira/browse/JBMESSAGING?report=com.atlassian.jira.plugin.system.project:roadmap-panel.
JBoss Messaging 1.0.1.SP4 Released
JBoss Messaging 1.0.1.SP4 has been released and it is available for download on jboss.org (http://labs.jboss.com/portal/jbossmessaging/downloads) and sourceforge (http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=157261).
This service pack fixes several major bugs present in 1.0.1.SP2 and previous releases.
The most serious bug is JBMESSAGING-721, which was causing message redelivery not to function properly. This bug fix alone should justify an upgrade to 1.0.1.SP4, especially if you use Message Driven Beans and Container Managed Transactions.
Another critical bug is JBMESSAGING-787, which was causing long-running invocations (such as sending a large transaction to the server) to time out inadvertently. The root cause was identified to be JBREM-691. The new Remoting library incorporated by 1.0.1.SP4 contains the fix for this bug.
Other bugs fixes address the following 1.0.1.SP2 problems:
- Broken QueueBrowser behavior (JBMESSAGING-803)
- Non-compliant client ID behavior - the previous version allowed simultaneous clients with same client ID (JBMESSAGING-791)
- Incorrect handling of the replyTo property for persistent messages in some situations (JBMESSAGING-757)
- Corruption of the security context in managed environment (JBMESSAGING-807)
- Potential deadlock during the client initialization (JBMESSAGING-800)
- Memory leaks (JBMESSAGING-638)
The complete list of changes introduced by this release is available at http://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12311164&styleName=Html&projectId=12310061
The JBoss Messaging project roadmap is available here: http://jira.jboss.org/jira/browse/JBMESSAGING?report=com.atlassian.jira.plugin.system.project:roadmap-panel
We would like to use this opportunity to thank Andrea Di Cesare, Ilya Bochkov and our colleague Amit Bhayani for identifying some of the previously mentioned bugs, taking the trouble to report them, provide test cases, workarounds and fix suggestions.
JBoss Messaging 1.2.0.Beta2 Released
JBoss Messaging 1.2.0.Beta2 has been released and it is available for download on jboss.org (http://labs.jboss.com/portal/jbossmessaging/downloads ) and sourceforge (http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=157261 ).
1.2.0.Beta2 is functionally complete, with the exception of the "unreliable link scenario" (http://jira.jboss.org/jira/browse/JBMESSAGING-676 ), whose development is still on-going on a parallel branch.
Beta2 includes full clustering, with load balancing and transparent failover. However, it is still a preview release, not all functional, stress and smoke tests pass, so do not attempt to use it in production. Also, the integration with the AS (installation, etc.) is at the moment a bit rough.
The messaging team is currently concentrating on releasing an almost-production-ready 1.2.0.CR1 shortly (a week from now). For CR1, the plan is to have all tests passing, and integrate seamlessly with the AS, but we will be waiting for the community feedback for a while after release before going GA.
The final 1.2.0.GA is expected to be out at the end of February 2007.
The Beta2 release ships with clustering examples (which also double as smoke tests) that demonstrate distributed destinations and transparent failover capabilities. For the transparent failover example, a vanilla JMS client creates a connection to the JMS provider and sends message over that connection. Separately, we kill the cluster node managing the connection (using System.halt(), to simulate an abrupt VM failure), but the event goes unnoticed by the client, which continues to send and receive messages over the same connection. Obviously, the example requires a cluster of at least two nodes in order to work.
The Messaging road map is available here: http://jira.jboss.org/jira/browse/JBMESSAGING?report=com.atlassian.jira.plugin.system.project:roadmap-panel .