[
https://issues.apache.org/jira/browse/KAFKA-14771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695434#comment-17695434
]
Luke Chen commented on KAFKA-14771:
-----------------------------------
[~pierDipi] , the suggestion makes sense to me. Welcome to submit a PR for it.
Thanks.
> Include current thread ids in ConcurrentModificationException message
> ---------------------------------------------------------------------
>
> Key: KAFKA-14771
> URL: https://issues.apache.org/jira/browse/KAFKA-14771
> Project: Kafka
> Issue Type: Improvement
> Components: clients
> Affects Versions: 2.8.2, 3.2.3
> Reporter: Pierangelo Di Pilato
> Priority: Minor
> Labels: consumer
>
> In the KafkaConsumer.acquire method a ConcurrentModificationException
> exception is thrown when
>
> {code:java}
> threadId != currentThread.get() &&
> !currentThread.compareAndSet(NO_CURRENT_THREAD, threadId){code}
> however, the exception message doesn't include:
>
> * Thread.currentThread().getId()
> * currentThread.get()
>
> I think including the aforementioned variables is very useful for debugging
> the issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
