Hi, we were recently told Java server version 281 has possible vulnerability risks and to upgrade to version 291 or 301. When I a searched for how to apply this, we found a warning message here at Pega that changing the version used by JVM could mean the Clipboard may not function as expected. Is there a process/method to update the java server version so Pega Application can be updated to utilize it safely? We found the version the product is running by selecting the 'PEGA' option on bottom right of Designer Studio for System Information.
@KevinZheng_GCS@MUELM Any thoughts on this version change concern? We're getting a strong push to present a remediation strategy before the end of year freeze happens.
***Edited by Moderator Marissa to update Capability tags****
@Niladri Thanks for the feedback, I will try to push this in that direction and hopefully get some guidance. I have literally been learning Pega with my team by being tossed onto the fire for about 6 weeks. No background prior so this is all pretty much raw learning. I hadn't heard about Pega GCS, but I gather its the better place to pose the question.
@DennisM99 , @KevinZheng_GCS , @MUELM This is Dennis, and I'm still looking for some advice or thoughts on this. From Pega Community the content is found in Home> System administration > Managing your system > Monitoring the health of your system > Viewing the JVM in use on your server. And on that screen there is a Result box, where the last sentence contains a warning that changing the JVM version from the installed version could impact the clipboard. Has this been explored further, risk reduced in any way, or a patch/fix defined that allows a safe and stable upgrade to occur?
@DennisM99 Hi Dennis, apologies for the late response. Let me see if I can ask internally regarding this. You may be seeing some standard boiler plate warning to ensure you test thoroughly. Per the the above suggestion by @Niladri , it is not a bad idea to open an SR in my Support Portal to get GCS to help out as well with these technical questions.
@DennisM99 Hi Dennis, so what I have found to mitigate the risk is to ensure that, as part of the upgrade to the JVM, you should also clear cache including the caching tables which should remove compiled code. This will cause the system to compile rules again and run first use assembly using the new java version. Also, after the jvm is updated, make sure you recompile all function libraries by clicking the "compile" button on each library rule instance. This will mitigate the risk that is listed in the community page you mention. I hope this helps clarify.