[ 
https://issues.apache.org/jira/browse/KAFKA-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15330751#comment-15330751
 ] 

ASF GitHub Bot commented on KAFKA-3837:
---------------------------------------

GitHub user bharatviswa504 opened a pull request:

    https://github.com/apache/kafka/pull/1505

    KAFKA-3837: Report the thread id of the blocking thread when throwing 
ConcurrentModificationException

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bharatviswa504/kafka KAFKA-3837

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1505.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1505
    
----
commit 3cabc5d2883cb3b611b377750989d65931c282e9
Author: Bharat Viswanadham <bhar...@us.ibm.com>
Date:   2016-06-14T21:37:36Z

    KAFKA-3837: Report the thread id of the blocking thread when throwing 
ConcurrentModificationException

----


> 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)

Reply via email to