Pavel Chertalev

How did u reporoduce this case? I tryed exchange.disconnect() and orderBookObserver.dispose(); - I don't see problem. There is known issue that netty thread can't be stopped after disconnect and java...

@badgerwithagun

Guys, I'm not clear what is the problem I started BitstampManualExample and trades are recieved well: ``` 15:43:29.390 [main] INFO info.bitrich.xchangestream.bitstamp.v2.BitstampStreamingExchange - Calling Remote Init... 15:43:29.398 [main] DEBUG si.mazi.rescu.HttpTemplate -...

Ah! I got - subscriber is not recieving trades - there is just JsonNettyStreamingService log.

Guys, sorry I don't like changes from @jurepetrovic. I have opened my PR regarding this issue.

https://github.com/bitrich-info/xchange-stream/pull/456

In the last version loop without delay has been fixed, delay NettyStreamingService.DEFAULT_RETRY_DURATION (15 sec) is used between reconects. CPU to 100% should not happaned. But anyway 15 sec is not...

I created pool request for limiting BFX open connection operations

https://github.com/bitrich-info/xchange-stream/pull/269