- [jms-spec users] JMS 2.0 errata: final request for comments
- [jms-spec users] JMS 2.0 Errata: JMS_SPEC-161 (serialVersionUID of JMSException has changed from JMS 1.1 to JMS 2.0 )
- [jsr368-experts] [jms-spec users] JMS 2.0 Errata: JMS_SPEC-160 (JMS API source contains self-closing HTML tags)
- [jsr368-experts] JMS 2.0 errata: final request for comments
- [jsr368-experts] JMS 2.0 errata: JMS_SPEC-125 (Define whether a JMS provider should call reset after sending a BytesMessage asynchronously)
- [jsr368-experts] JMS 2.0 Errata: JMS_SPEC-157 (JMS 2.0 introduced an incompatible restriction on creating two sessions per connection in Java EE)
- [jsr368-experts] JMS 2.0 Errata: JMS_SPEC-162 (Typos in section 7.3 "Asynchronous send")
- [jsr368-experts] JMS 2.0 Errata: JMS_SPEC-163 (Javadoc for JMSContext#setClientID contains obsolete MessageContext reference)
- [jsr368-experts] JMS 2.0 errata: Summary of proposed changes
- [jsr368-experts] JMS_SPEC-133: Update javadoc comments for QueueConnection#createQueueSession and TopicConnection#createTopicSession
- [jsr368-experts] JMS_SPEC-155 (JMS 2.0 introduced incompatible changes to createSession(bool,int))
- JMS 2.0 errata: JMS_SPEC-125 (Define whether a JMS provider should call reset after sending a BytesMessage asynchronously)
- JMS 2.0 Errata: JMS_SPEC-157 (JMS 2.0 introduced an incompatible restriction on creating two sessions per connection in Java EE)
- JMS 2.0 Errata: JMS_SPEC-158 (JMS 2.0 introduced incompatible changes to Connection.stop and close and Session.close)
- JMS 2.0 errata: Summary of proposed changes
- JMS_SPEC-155 (JMS 2.0 introduced incompatible changes to createSession(bool,int))