First of all, just to point out again, FP is Feature Pack, not Fix Pack, a lot of new things and stuff is inside.
Right new, we are preparing to roll update ASAP, to get JVM8 in production to get ourselves ready for FP10 and update on IBM Designer side.
This is stuff we run into so far:
- SMTP issue is a bit specific, but that is stuff that you don’t want to get to debug… As always, thanks goes to Daniel for pointing this to community, also, get IF1
- JVM upgrade (form 6 to 8) leads to change/upgrade of JDBC drivers, eg. MS SQL ; upgrade this also
- JVM change changed java.policy, …/lib/ext/*, etc… but we already know that, but this time java.security change is big change (as JVM 6 to 8 is), and for example, you might find yourself with JVM dropping connections to some old MS SQL server… something like this:
com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "SQL Server did not return a response. The connection has been closed.".
18.09.2017 11:24:35 Agent error: ??? 18, 2017 11:24:34 AM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL INFO: java.security path: C:\IBM\Lotus\Domino\jvm\lib\security Security providers: [IBMJSSE2 version 1.8, IBMJCE version 1.8, IBMJGSSProvider version 8.0, IBMCertPath version 1.8, IBMSASL version 1.8, IBMXMLCRYPTO version 8.0, IBMXMLEnc version 8.0, IBMSPNEGO version 8.0, SUN version 1.8] SSLContext provider info: IBM JSSE provider2 (implements IbmX509/PKIX key/trust factories, SSLv3/TLSv1/TLSv1.
Check out jdk.tls.disabledAlgorithms parameter, and enable algorithms you still need, or, thing that might sound to unorthodox, upgrade your SQL servers 🙂
Thing that should be double checked after every update, java.policy
Some related links: