ChangeNotes: 3.2.4

[adrian.brock]

The following are the JBossMQ changes between 3.2.3 and 3.2.4
starting with the 3.2.4RC1 changes

DO NOT POST ANYTHING EXCEPT CHANGE NOTES HERE

If you have user questions about these changes use the user forum:
http://www.jboss.org/index.html?module=bb&op=viewforum&f=48

Discussions on the implementation or JBossMQ design should be
in a separate topic in this forum.

[adrian.brock]

Add JMX operations to list messages in queue and topic subscriptions.
See the WIKI for more information

http://www.jboss.org/wiki/Wiki.jsp?page=ConfigQueue
http://www.jboss.org/wiki/Wiki.jsp?page=ConfigTopic

[adrian.brock]

Message and TransactionID Object Pooling has been disabled.
This reduces some of the complexity of the implementation.
User space pooling is only relevent for objects that take a long
time to construct (these objects do not).

[adrian.brock]

New JDBC3 Persistence manager.
Examples configurations are in docs/examples/jca
More information is on the WIKI
http://jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQJDBC3Persistence

[adrian.brock]

Performance improvement:
Messages are now queued to the client outside the synchronization block in BasicQueue
giving other threads access to the queue earlier.

[adrian.brock]

Null Persistence Manager:
Allows configuration of JBossMQ or optionally some destinations as not persistent
(including message softening/caching).
See the WIKI for more information:
http://jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQNullPersistence

[adrian.brock]

Performance improvement:
Added primary key index to JMS transaction table for JMS/HSQLDB
Without this PK, performance is really rotten.
Also added it to jdbc3

[adrian.brock]

BUG: UIL2 fails to cleanup threads
Replace the log.error(...) calls on object stream creation failure in the
read and write thread tasks with handleStop(...) calls to clean up both
threads. See bug#885053.
http://sourceforge.net/tracker/?group_id=22866&atid=376685&func=detail&aid=885053

[adrian.brock]

Notify all waiting threads on a message consumer that it is closing.
This is a defensive fix for a problem that could be caused when a consumer is misused

[adrian.brock]

Lazy create timer thread to avoid leaks
Refer to bug #890030 on Sourceforge
http://sourceforge.net/tracker/?group_id=22866&atid=376685&func=detail&aid=890030

[adrian.brock]

BUG FIX:
Throw the spec defined exception when a subscription does not exist

[adrian.brock]

Tidyup: Don't wrap plain JMSExceptions in SpyJMSExceptions

[adrian.brock]

BUG FIX:
Add checks for trying to configure/use a closed MessageProducer.
Keep track of a session's message producers and close them when the session
is closed.

[adrian.brock]

Add support for sending thirdparty messages that are not serializable.

[adrian.brock]

BUG FIX:
Disallow QueueSession operations on TopicSessions and vice-versa.
This is because JBossMQ is really JMS 1.1 underneath but only 1.0.2b interfaces
are exposed in jboss-j2ee.jar in 3.2.x