[
https://issues.apache.org/jira/browse/AMQ-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-4035.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.7.0
Assignee: Timothy Bish
Added check for null before using the ack value.
> Null pointer in class KahaDBStore programmed
> --------------------------------------------
>
> Key: AMQ-4035
> URL: https://issues.apache.org/jira/browse/AMQ-4035
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Environment: Windows 7, Active MQ 5.6.0
> Reporter: Matthias Vetter
> Assignee: Timothy Bish
> Fix For: 5.7.0
>
>
> The method "protected void doAcknowledge(ConnectionContext context, String
> subscriptionKey, MessageId messageId, MessageAck ack)" in KahaDBStore, line
> 705, contains a get-operation on parameter "ack" in line 711:
> command.setTransactionInfo(transactionIdTransformer.transform(ack.getTransactionId()));
> Unfortunately, the method is called from inside with setting ack=null!
> (same class, method "run" of internal class StoreTopicTask, line 1268):
> this.topicStore.doAcknowledge(context, key, this.message.getMessageId(),
> null);
> Thus, a null pointer exception is guaranteed, whenever the run-method is
> called (which is the case, for instance, when topic messages are synchronized
> in a network cluster).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
