[
https://issues.apache.org/jira/browse/KAFKA-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331377#comment-15331377
]
Simon Cooper edited comment on KAFKA-3837 at 6/15/16 8:23 AM:
--------------------------------------------------------------
I would say the thread name is much more useful - this is specifically aimed at
debugging when this exception happens, often the process has crashed out, so
the thread id doesn't tell you anything. The thread name is descriptive, and
often has info on what the thread's purpose is.
was (Author: thecoop1984):
I would say the thread name is much more useful - this is specifically aimed at
debugging when this exception happens, often the process has crashed out, so
the thread id doesn't tell you anything. The thread name is descriptive.
> Report the name of the blocking thread when throwing
> ConcurrentModificationException
> ------------------------------------------------------------------------------------
>
> Key: KAFKA-3837
> URL: https://issues.apache.org/jira/browse/KAFKA-3837
> Project: Kafka
> Issue Type: Improvement
> Components: clients
> Affects Versions: 0.9.0.1
> Reporter: Simon Cooper
> Assignee: Bharat Viswanadham
> Priority: Minor
>
> {{KafkaConsumer.acquire}} throws {{ConcurrentModificationException}} if the
> current thread it does not match the {{currentThread}} field. It would be
> useful if the name of the other thread was included in the exception message
> to help debug the problem when this exception occurs.
> As it stands, it can be really difficult to work out what's going wrong when
> there's several threads all accessing the consumer at the same time, and your
> existing exclusive access logic doesn't seem to be working as it should.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
