Hello Everyone,Happy Friday to everyone. Just joined today and wanted post this in hopes of somebody can provide some suggestions for a couple of things we are experiencing with Automic " Workload Automation Suite/ Applications Manger.Automic Release: v9.2.1_28679_28815 Build: 28815* Users on Windows 10 PC's that are running JAVA 1.8.0_162 and are unable to make connection to the "Applications Manager Client" thru the downloaded "Client.jnlp" using chrome or firefox. It appears only JAVA 1.8.0_161 will reliably make a connection. Given the latest release available for JAVA client is 1.8.0_231. Does anyone know what is the stated/latest current JAVA compatibility for this product given it's reliance on this to function?* We often see this "RmiServerError and have not been able to pin down what causes this and if it can be safely ignored?This message is generated approximately every 6-8 minutes. I may need to submit a ticket on this particular one.Suggestions?
ErrorMsg: AwE-5102 Agent error (11/15/19 11:09 AM)Details: no cipher suites in common4f808e0a[SSL_NULL_WITH_NULL_NULL: Socket[addr=/10.69.1.12,port=6004,localport=1099]]About details:Butler Community College #2052805Release: v9.2.1_28679_28815 Build: 28815 Fri Dec 22 13:36:42 PST 2017VM Memory: 20.4 of 39.6 MB used, 19.2 MB freeWorkstation Java VM: Oracle Corporation 1.8.0_161Server Java VM: Oracle Corporation 1.8.0_111Workstation: 201EAPS-3NZKSD2 (201EAPS-3NZKSD2/10.101.1.3)Remote host: automic.xxxx.xxx (xxx.xxx.xxx.xxx)RMI Port: 1099Oracle Database 12c Enterprise Edition Release 18.104.22.168.0 - 64bit ProductionWith the Partitioning, OLAP, Advanced Analytics and Real Application Testing optionsOracle JDBC driver 22.214.171.124.0Thanks in Advance,Darrin C.
Hello Darrin,Cipher Suites are a set of SSL/TLS algorithms that Java uses to secure a connection. With newer versions of Java being released, more secure algorithms are introduced while older algorithms may be disabled. When you open the Applications Manager client to connect to the master, client side Java will communicate to server side Java (java used by the master) and negotiate a common algorithm to be used to authenticate and secure the connect.A "no cipher suites in common" error indicates that during the negotiation or handshake process, no common algorithms were found between Java 8 update 162 that is installed on the client PC and Java 8 update 111 installed on the master. This is likely due to Java 8 update 162 disabling one or more algorithms which is still being used on Java 8 update 111. The first step resolving this issue is to make sure that client and server Java version match, meaning you may need to upgrade your Java on the master to Java 8 update 162. This should likely resolve your client issue.Below is the current Java compatibilityWhat Java versions are supported by Applications Manager?Note that compatibility matrix simply list the major versions of Java which means all minor versions within each major version is included. If there is an issue, it is likely due to Java versions between the Master, Remote Agent, and Client PC being too far apart so matching Java versions is important.There is an issue with Java 8 update 201 and above which either requires you to upgrade to Applications Manager version 9.3 or use a workaround. See below KE:Applications Manager connection error after installing or upgrading to Java 1.8.0_201Regards,Phearith Mao