NO-JIRA Fix double check locking in ActiveMQJMSContext
Double checked locking was operating on a non-volatile field this is not threadsafe, make field volatile.
This commit is contained in:
parent
05d893036e
commit
b2d40b716d
|
@ -58,7 +58,7 @@ public class ActiveMQJMSContext implements JMSContext {
|
|||
private volatile Message lastMessagesWaitingAck;
|
||||
|
||||
private final ActiveMQConnectionForContext connection;
|
||||
private Session session;
|
||||
private volatile Session session;
|
||||
private boolean autoStart = ActiveMQJMSContext.DEFAULT_AUTO_START;
|
||||
private MessageProducer innerProducer;
|
||||
private boolean xa;
|
||||
|
@ -91,6 +91,7 @@ public class ActiveMQJMSContext implements JMSContext {
|
|||
}
|
||||
|
||||
public Session getSession() {
|
||||
checkSession();
|
||||
return session;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue