[jira] [Issue Comment Deleted] (QPID-6518) Cyclic errors on thread interruption thru resetting interrupted flag

["Nikita Konev (JIRA)" <ji...@apache.org>]

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

Nikita Konev updated QPID-6518:
-------------------------------
    Comment: was deleted

(was: Thank you for responce!

"Rather than looping on "
Unfortunately, this is our business logic. Sad but true.

I tested you revision 1676956, but it not resolves my troubles. 
According to our business logic, should to save setted state of interrupted flag.
And why in filally statement? It brokes normally cycle works.

Please, see attached BasicMessageConsumer.java - there I writed code that works fine.)

> Cyclic errors on thread interruption thru resetting interrupted flag
> --------------------------------------------------------------------
>
>                 Key: QPID-6518
>                 URL: https://issues.apache.org/jira/browse/QPID-6518
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: 0.32
>         Environment: WildFly 8.2.0.Final, RabbitMQ 3.5.1
>            Reporter: Nikita Konev
>            Assignee: Rob Godfrey
>         Attachments: BasicMessageConsumer.java, OurBean.java, wildfly-log.txt
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> When i attempt undeploy application caused backgroundProcess.interrupt() in OurBean.java:72, sometimes may occur InterruptedException in BasicMessageConsumer.receive(). It resets interrupted flag of thread that resulting cyclic errors because thread is not interrupted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org