Issue Details (XML | Word | Printable)

Key: JMS_SPEC-98
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Nigel Deakin
Votes: 1
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
jms-spec

Fix findbugs warnings in JMSException, JMSRuntimeException, QueueRequestor, TopicRequestor

Created: 14/Aug/12 10:02 AM   Updated: 20/Mar/13 03:42 PM   Resolved: 04/Sep/12 03:04 PM
Component/s: None
Affects Version/s: 1.1
Fix Version/s: 2.0PD, 2.0

Time Tracking:
Not Specified

Tags: pd20-added
Participants: Nigel Deakin


 Description  « Hide

The following JMS 1.1 classes give the following findbugs warnings:

javax/jms/JMSException.java:86: UG_SYNC_SET_UNSYNC_GET: 
javax.jms.JMSException.getLinkedException() is unsynchronized, 
javax.jms.JMSException.setLinkedException(Exception) is synchronized

javax/jms/QueueRequestor.java:62: URF_UNREAD_FIELD:
Unread field: javax.jms.QueueRequestor.queue

java/javax/jms/TopicRequestor.java:61: URF_UNREAD_FIELD: Unread field:
javax.jms.TopicRequestor.topic

It should be possible for fix all these without breaking backwards compatibility.

Also, the following new JMS 2.0 class givs the following findbugs warnings:

javax/jms/JMSRuntimeException.java:118: UG_SYNC_SET_UNSYNC_GET:
javax.jms.JMSRuntimeException.getLinkedException() is unsynchronized,
javax.jms.JMSRuntimeException.setLinkedException(Exception) is synchronized

This should be fixed.



Nigel Deakin added a comment - 04/Sep/12 03:04 PM

Now fixed.