Community
Participate
Working Groups
To reproduce, connect the desktop Eclipse client to flux, then kick/restart the flux server. Eclipse instance now consumes 100% CPU (on my quadcore machine!) Only way to fix that seems to be to shutdown and restart Eclipse.
I ran into that situation once. Number of threads grows all the time. It tries to connect, but fails as the result there is a non-terminated Socket IO thread. Every attempt to reconnect ends up with a new not terminated thread. Perhaps there is some sort of a workaround can be implemented on the Eclipse client to avoid this situation with non-terminated socket IO thread. However, the long term fix for this would be to update our socket IO java client.
I could not reproduce this with turning off the Flux server. However I could get it to get into the same state and this is 100% reproducible: 1. Ensure that there is a Flux server on CF at https://flux.cfapps.io:4443 for example. 2. Start Eclipse client and set the connection to Flux where Flux URL is https://flux.cfapps.io (no port) and your valid GitHub credentials. Upon the Eclipse restart watch the debug view listing all threads. Note that there will be more and more threads created every second.
maybe this can be solved via bug 447098.
