You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Pierangelo Di Pilato (Jira)" <ji...@apache.org> on 2023/03/02 14:16:00 UTC

[jira] [Updated] (KAFKA-14771) Include current thread ids in ConcurrentModificationException message

     [ https://issues.apache.org/jira/browse/KAFKA-14771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierangelo Di Pilato updated KAFKA-14771:
-----------------------------------------
    Fix Version/s: 3.3

> 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
>            Assignee: Pierangelo Di Pilato
>            Priority: Minor
>              Labels: consumer
>             Fix For: 3.3
>
>
> 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)