When I try to open a connection using proton-j while my machine doesn't have internet access, I see that proton-j leaks file descriptors. Attached is the sample I wrote that repro's this issue. I'm looking either for guidance on how to handle IOExceptions in the onTransportError callback, or for a confirmation that what I'm doing to handle them is correct, and that there is a bug in proton-j around this scenario.
If you need help viewing the file descriptor count growing over time, the process explorer tool is what I've been using. Running the sample in a loop will make this leak more obvious, but it isn't required to leak the file descriptors. This same bug seems to happen in Linux and MacOS as well.