We have a live Java-based Interactive Provider (server side provider with a single socket accepting requests from multiple clients) application that uses the following libraries from 2016 or earlier (legacy UPA Java API bundle):
This has been working with TREP 2.6 ADH clients without issue for some time.
Now, this same code base is no longer working with TREP 3.2 ADH clients as the individual client Channels become inactive and so the ADH client login requests time out since the Java Interactive Provider ends up closing/removing the Channel as its state is INACTIVE. The implementation follows the spirit of the example documented in the Java API documentation (UPAJDevGuide.pdf).
1) Do we need to update the corresponding Java API libraries (jar) to work with TREP 3.2+?
2) Is there anything that's changed in the API that would require an update to how we instantiate the UPA server (e.g. BindOptions, etc.), accept incoming client requests, etc?