I recently received (via the Java EE spec leads) the following comments from community member Florian Beaufumé. With his
permission I am forwarding them here.
Nigel
> ----- JMS -----
>
> JMS.1 - There should be a portable way to specify a send delay (I mean in pure JMS, not with EJB timer or other API)
> to make a message available only after some time. See https://forums.oracle.com/forums/thread.jspa?threadID=2124412
> for details.
>
> JMS.2 - Poison messages handling is unspecified. Non portable application server specific features include: dead
> letter queue configuration, retry count configuration, resend delay configuration... We need portable solutions. See
> https://forums.oracle.com/forums/thread.jspa?threadID=2124413 for details.
>
> JMS.3 - The number of deliveries of a message sent to a topic is unspecified. See
> https://forums.oracle.com/forums/thread.jspa?threadID=2124417 for details.
>
> JMS.4 - Durable topic subscription lifecycle for MDB is not specified. See
> https://forums.oracle.com/forums/thread.jspa?threadID=2124418 for details.
>
> JMS.5 - @MessageDriven configuration specification is unclear and non portable.
>
> JMS.6 - 'clientID' and 'subscription name' should be better defined in the specification.
>
> JMS.7 - JMS clustering is completely unspecified. Yet there is a lot to say: first about the load-balancing and
> fail-over between the JMS producer and the JMS engine, then the load-balancing between JMS engine instances and then
> the load-balancing between a JMS engine instance and the JMS consumers.