@Mark Takata (Adobe) or @priyank_adobe Can one of you confirm that the previous issues with 11.0.20 and the update JARs, etc., have been addressed before we get started testing this?
@rstewart - yes - i saw that the version from Oracle can cause issues with doing updates from within CF admin. we did install the Adobe version on one box and it seems to be working fine, but it was already running at the highest CF update level, so maybe we won't experience that pain until another update comes out. i'm hoping @Mark Takata (Adobe) will give us some good news regarding this version, like perhaps it's somehow different from the Oracle version. 🤷♂️
👍🏻 1
r
rstewart
08/14/2023, 7:45 PM
The thought of it being a different version of the same Java release makes my stomach do weird things (green face emoji goes here). In the past, they have been binary-identical and I think the widely-held assumption has been that they are in fact the Oracle packages.
m
Mark Takata (Adobe)
08/14/2023, 7:59 PM
@Bagish Mishra is there anything you can comment on here?
c
carehart
08/14/2023, 10:46 PM
There's no "different jvm version" from Adobe that I'm aware of. The problem is in the latest jvm, released by Oracle in July. There have been no new jvm updates from Oracle since.
For those interested, my blog post offers a workaround--and raises an issues that this problem may have wider impact than just the cf updates. And my workaround (a JVM arg introduced by Oracle with this update) may be worth adding to address those.
As I conclude in my post, other Java apps are hitting issues. I offered an update today listing some of them at the bottom of my post. This does not exonerate Adobe. We still need clarity from them.