[
https://issues.apache.org/jira/browse/GEODE-8765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248863#comment-17248863
]
ASF subversion and git services commented on GEODE-8765:
--------------------------------------------------------
Commit 4c00984eb3c32972b4b03fdbe2b6397decdc177f in geode's branch
refs/heads/develop from Alberto Gomez
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4c00984 ]
GEODE-8765: Fix NullPointerException when group-transaction-events an… (#5829)
* GEODE-8765: Fix NullPointerException when group-transaction-events and events
in and not in transactions are sent.
> NullPointerException if group-transaction-events enabled and mix of puts with
> transactions and without transactions
> -------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-8765
> URL: https://issues.apache.org/jira/browse/GEODE-8765
> Project: Geode
> Issue Type: Bug
> Components: wan
> Affects Versions: 1.14.0
> Reporter: Alberto Gomez
> Assignee: Alberto Gomez
> Priority: Major
> Labels: pull-request-available
>
> When group-transaction-events is enabled and Geode receives a mix of puts,
> some inside transactions and some not in transactions, in the case it is
> needed to add extra events to the batch in order to have all the events for
> each transaction in the given batch, if the sender runs into an event not
> belonging to a transaction while looking for events in the queue, a
> NullPointerException is thrown when trying to get the transactionId for the
> event. The exception is caught by the sender processor and a warning message
> is written in the log but some undesired effects are provoked:
>
> * In parallel gateway senders, this situation provokes that the batch is
> sent without completing the transactions and also some events are left in the
> queues forever without ever being drained (although all the events are sent
> to the other side).
> * In serial gateway senders, this situation provokes that once the exception
> is thrown, no more events are sent to the other side as the events in the
> last batch that could not be sent because the exception was thrown are tried
> to be sent over and over without success.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
