Open glassfishrobot opened 12 years ago
@glassfishrobot Commented Reported by @nigeldeakin
@glassfishrobot Commented @nigeldeakin said: This will be evaluated by the expert group for possible inclusion in the JMS 2.0 public draft. Tagging accordingly.
@glassfishrobot Commented This issue was imported from java.net JIRA JMS_SPEC-84
The javadoc for javax.jms.DeliveryMode (http://docs.oracle.com/javaee/6/api/javax/jms/DeliveryMode.html) states:
This introduces several important features of JMS which are not described in such explicit terms in the JMS specification itself, in particular the statement that a JMS provider may drop (delete from storage) an unacknowledged message if the client is somehow running out of resources. The expression "message retention policy" is not used in the spec.
Section 4.10 "Reliability" is the relevant section. This states that "Once-and-only-once message delivery, as described in this specification... does not cover loss due to resource restrictions" but does not mention that messages may be dropped from the server because the client was short of resources.
This should be clarified.