JBoss Messaging 1.2.0.CR1 Release Notes
February 21 2007
JBoss
Messaging is a new JBoss JMS 1.1-compliant JMS provider, aimed to
replace JBossMQ. The curent release is the first 1.2 candidate
release (1.2.0.CR1).
1.2.0.CR1 includes full
clustering, with load balancing and
transparent failover. However, it is still a candiate release, and even
if all functional, stress and smoke tests pass, use caution if you
consider using it in production.
An brief overview of the clustering
features and installation instructions are available in the "Clustering
Guide". The guide is bundled with this release and is
provided in HTML, HTML-single
and PDF
formats. The guide is also available on-line at http://labs.jboss.com/portal/jbossmessaging/docs/index.html
Warning
The current JBoss Messaging
distribution is a candidate release.
Use caution if consider deploying it in a production environment.
Summary of Changes
This is just a candidate release, the summary will be compiled for the
General Availability release. For a raw change list, see "Release
Notes" below.
Release Notes
Bugs
- [JBMESSAGING-371]
- MessageListener times out on inactivity, after receiving at least one
message
- [JBMESSAGING-417]
- JMS Client does not exit
- [JBMESSAGING-505]
- RoundRobinPointToPointRouter occasionally throws ArithmeticException:
/ by zero
- [JBMESSAGING-683]
- MSSQL configuration appears invalid
- [JBMESSAGING-693]
- Starting two node clusters simultaneously may end in failed messaging
server node boot
- [JBMESSAGING-695]
- We need to be able to run our functional testsuite with other
databses besides HSQLDB
- [JBMESSAGING-705]
- ConnectionFactory service is registered under JMX
"jboss.messaging.destination:" domain, it shoud be
"jboss.messaging.connectionfactory:" or similar.
- [JBMESSAGING-744]
- org.jboss.test.messaging.jms.QueueTest fails if executed using
Clustering configuration
- [JBMESSAGING-764]
- New failover update map code does not use MessagingMarshallable.
- [JBMESSAGING-777]
- Revise creation of Object*Stream on Remoting/our Marshallers
- [JBMESSAGING-783]
- Fix HAStressTest
- [JBMESSAGING-790]
- "DeadLock" If failover happens on a MessageConsumer::receive
- [JBMESSAGING-805]
- Fix JMSProviderResourceRecovery
- [JBMESSAGING-807]
- security context switch after sending a message
- [JBMESSAGING-809]
- Extra message created if server fails right after send is completed
- [JBMESSAGING-812]
- "Cannot find object in dispatcher..." intermittent failures
- [JBMESSAGING-816]
- Verify if pre-configured IDs are throwing an exception properly.
- [JBMESSAGING-820]
- ConnectionFactoryUpdate ClassCastException when using HTTP
- [JBMESSAGING-824]
- queue smoke test fails
- [JBMESSAGING-825]
- Transactions corrupted because sybase truncates trailing zeros
- [JBMESSAGING-826]
- Using Pre Configure clientIDs will invalidate the usage of a simple
createConnection
- [JBMESSAGING-827]
- ACK fails during failover on transacted session
- [JBMESSAGING-831]
- Simple (non-clustered) smoke test fails with Remoting exceptions on
client and server-side
- [JBMESSAGING-833]
- MDB smoke test fails (in both non-clustered and clustered
configurations)
- [JBMESSAGING-836]
- Deadlock on ServerConnectionEndpoint
- [JBMESSAGING-840]
- Shutting down the Messaging service on JBoss 4.0.1sp1 fails
- [JBMESSAGING-841]
- MDB smoke test fails in clustered configuration (caused by inability
to create temporary queues in a clustered configuration)
- [JBMESSAGING-842]
- The current clustered ConnectionFactory is not apropriate for use
with an MDB container.
- [JBMESSAGING-846]
- release-admin.xml installation script does not correctly configures
BindingManager for newly created clustered configurations, in some
situations
- [JBMESSAGING-847]
- Some installer-generated JBoss installations (4.0.3, 4.0.3SP1) do not
contain a BindingManager declaration in their jboss-service.xml, so
release-admin.xml doesn' t work properly
- [JBMESSAGING-852]
- Unacked message state is not cleaned up after failure in ack
- [JBMESSAGING-853]
- Smoke tests fail again after installing bisocket
- [JBMESSAGING-862]
-
org.jboss.test.messaging.jms.clustering.FailoverTest.testFailureRightBeforeACK()
fails
- [JBMESSAGING-863]
- Bisocket test fails with socket listen security violation on
client-side
Feature Requests
- [JBMESSAGING-694]
- Integrate, test and document the "bisocket" remoting transport.
- [JBMESSAGING-768]
- Add a test that makes sure there are no threads preventing VM to exit
on client side. There is a placeholder already:
org.jboss.test.thirdparty.remoting.DaemonThreadTest
- [JBMESSAGING-830]
- Random LoadBalanceFactory for Clustered Connection Factories
- [JBMESSAGING-849]
- Port the "mdb failure" smoke test from the 1.0 branch on the trunk
Tasks