did you upgrade your Tomcat version when you moved to 9.1.04?
1 of 1 people found this helpful
We did upgrade our Mid Tier from 8.1.02 to 9.1.04 as well and we did upgrade the Tomcat server at that time.
For the Mid Tier upgrade we performed the following:
- Uninstalled Mid Tier/Tomcat/Java
- Upgraded Java to 8
- Installed Tomcat 8.5
- Installed Mid Tier pointing to the new Tomcat directory
We did find this communities article which seems to have cleared up the problem, though we are monitoring it. Remedy - Server - How to set a specific SOAP version by default used by a Webservice in 9.1.02
We also found this article that didn't specifically address this issue, and we haven't put it in place, but we are considering it should it pop back up. Connection Errors - Unable to setup data connection, which is preventing the application from working correctly. HTTP Communication Error: 413 (ARWARN 9351)
If you have any thoughts on the matter, I would be happy to hear them just in case the problem rears its ugly head.
Glad to see you have a fix and it is working.
The reason I asked is that the TLS version used is dependent on the Java version installed and configured for use with Tomcat. This affects the SOAP protocol (and other permutations) also and what is "used" as a default, based on the version of Java installed.
Granted these Java/Tomcat settings I am referring too are directly related to incoming (Tomcat) and not outgoing (Filters - run via the Remedy plugin process) requests [however, as the latest versions of the Remedy stack have been ported to Java .. this information is relevant to how the JVM operates], but it is something to note when using Web Services/HTTP protocols i.e. the older Java version only supported certain TLS versions, where as latest versions support a and implement TLS 1.2 by default e.g. JDK 8 uses TLS 1.2 by default, which may not be compatible with legacy integrations and you may need to explicitly enable legacy versions in the Tomcat/related application config.
There are a number of different parameters that are configurable in Tomcat/Java where you can specify what options to use over the defaults that are enabled for that version.
Primarily, the changes/updates to Java are always related to security concerns over vulnerabilities e,g, TLS versions enabled, Cyphers configured, etc.
With Tomcat 8, you may need to configure a legacy cookie process (in the Tomcat config) for the Mid-Tier to work correctly dependant on your setup ....
Although I am explaining a slightly different issue to what you encountered, but the information is also relevant to note as you may need to enable legacy protocols with the newer versions of Java/Tomcat for integrations that use older protocols - as they may be disabled with a standard installation or the applications "default" to a non compatible configuration.
As this applies to any process that is running on Java, you may have to "extend" the configuration to use certain protocols (as listed in the KB article you reference). Glad to see BMC addressed this and provided a fix.
Thanks for your response. I did encounter the legacy cookie processing issue in previous testing so we included that in our upgrade. I forgot to include that in my original post.
Thank you so much for taking the time to respond I really appreciate it.