[
https://issues.apache.org/jira/browse/CASSANDRA-17422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555776#comment-17555776
]
shylaja kokoori commented on CASSANDRA-17422:
---------------------------------------------
>From my analysis, it looks like a timing issue.
Occasionally in this test, by the time code flow reaches the line
_try (OutboundMessageQueue.WithLock lock = queue.lockOrCallback(0, () -> {}))_
lock acquired on the queue prior to it has not been released. Therefore, lock
has a null value resulting in the {_}NullPointerException{_}.
When I added _Uninterruptibles.awaitUninterruptibly(lockUntil)_ before the line
of code mentioned above, test ran for a long time without failing.
Another option to fix this test, perhaps is to add a callback and check for the
content of the queue in the callback.
> Test Failure: org.apache.cassandra.net.OutboundMessageQueueTest.testRemove-cdc
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-17422
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17422
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
> Reporter: Josh McKenzie
> Priority: Normal
> Fix For: 4.0.x
>
>
> Branch: 4.0
> https://ci-cassandra.apache.org/job/Cassandra-4.0/350/testReport/org.apache.cassandra.net/OutboundMessageQueueTest/testRemove_cdc/
> {code}
> java.lang.NullPointerException
> at
> org.apache.cassandra.net.OutboundMessageQueueTest.testRemove(OutboundMessageQueueTest.java:91)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Failure: 1 of 3
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
