Allow null strings in MapMessage.
This breaks serialization compatibility with earlier versions of JBossMQ for
MapMessages (previous versions used a Hashtable which did not allow null).
There is code in place that can recover the old map message format from the
persistent store, converting it to the new format.
Correct the expecptions thrown by BytesMessage to be spec compliant
BUG FIX: StreamMessage
Fix some exceptions to be spec compliant
Correct the boolean parsing
Don't advance the pointer when an exception occurs
Fix the bytes processing
BUG FIX: Major improvements to the selector parsing
Add support for numeric promotion in eq and ne
IS NOT IN should not return true for non string properties
Improve the error reporting
Don't throw JMSException for invalidation selectors,
log a warning and return false instead
Type checking at subscription time
BUG FIX: Temporaries
Keep track of temporaries by session.
Don't allow consumers in different sessions to where
the temporary was created.
Don't allow temporary deletion when it has consumers
Removed copy on write semantics from the session
Force the correct acknowledgement mode for transacted sessions
Allow the same ClientID to be logged in twice.
Replace with a check for duplicate Topic subscriptions using the same client id
and subscription name which is where the check belongs.
Add configuration for minimal standalone JBossMQ server
Improved logging both client and server side.
This should make it easier for users to debug problems.
TRACE logging needs to be enabled to see it:
See the user forums for TRACE configuration
The default configuration now only contains UIL2.
All other remote connection factories are aliased to it.
Real deployments for the other connection factories can be found in the all configuration.
Change Notes between 3.2.4RC1 and 3.2.4RC2
Regression: reapply fix for UIL2 bind-address (lost in 3.2.4RC1)
Close all subscriptions to a Destination when the Destination is closed rather than
logging an exception about it being in use.