Supplying/Posting thread dumps and log files would be advantageous, especially without any systematic way to reproduce via integration test. More info the better :)
Locally I'm struggling to reproduce the issue using your broker xml and killing clients manually, but not able to reproduce so flying blind really. Any of the above would help possible tracking down of the issue. > On 29 Jun 2017, at 11:29, francesco81 <francesco.padov...@bticino.it> wrote: > > Hi Michael, > I can confirm that the thread is scheduled, because I see the log > "connection id 1643635981 calling fail executor thread". > Then I see "RemotingServiceImpl::removing connection ID 1643635981". > And then ....nothing more: no trace. Like if the thread never takes in > charge the effective execution. > > Francesco > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Artemis-rejects-the-clientid-after-client-disconnection-tp4727426p4728051.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
