Connection to server failing Closed HTTP connection with internal cause code: 10

[DarioCrivelli]

Hello,
The interface contract is that every time the session is terminated and a onFailure notification is sent, the notifications of the termination of the involved subscriptions are also sent.
Hence 1 is true and 2 is false.
If you see anything different, it may be a bug.
Unfortunately, the library in use is very old (it was overridden by a better library in 2016 and abandoned in 2019), hence it may be difficult to find and fix a bug.
Anyway, the observed behavior may also be associated to something particular that happens in your case or to other differences between the two scenarios you are comparing.

If the lack of the notification causes problems, we can investigate deeper by taking some log.
The library logs through the JDK's java.util.logging support.
I have attached the sample logging configuration file that was provided with that SDK (with a .txt suffix added).
You can have the JDK configured with it by adding

-Djava.util.logging.config.file=logCfg.properties.txt

to the client command line.
If you can replicate the behavior with a minimal and short interaction, you can set all loggers to the FINEST level.
Then we can compare the two cases.