Recommendations for a stable version for v24

[Olgun Onur Ozmen]

Hi,

The bug fixes in v24.4.xxx releases are a little scary.

I wanted to ask those who have migrated or upgraded their production environment to v24 and are actively using it.

• Which version are you using on v24? Are you experiencing any issues with that version?
• Is anyone using the latest release, 24.4.1 HF1 on production with heavy load?
• 24.4.1.hf2 (end of August) - 24.4.2 (end of September) are listed. Is anyone waiting for these before migrating to production?

Thanks.

------------------------------
Olgun Onur Ozmen
https://www.linkedin.com/in/olgunonurozmen/
------------------------------

[Leon Carroll]

I've got around six open cases with 24.4.1 in our dev environment so we're staying with 24.3.0 HF3 for the time being in test and production.  I'm hoping that hf2 or 2.4.4.2 fixes a few of these.

• SQL adapter doesn't handle termination characters in quoted string
• RA JMS doesn't support Activemq 6.x but JDK 17 doesn't support activemq 5.x
• Unix agent fails to update using CAU - (Fixed in 24.4.1_HF2)
• LDAP sync fails to log in to LDAP
• SAP BOBI integration fails to run scheduled report - SAP JCE not trusted
• A workflow scheduled to cancel with a maximum runtime, cancels early when a get_var from a SQL_Vara is used in the process tab

-------------------------------------------

[Keld Mollnitz]

Hi @Olgun Onur Ozmen,

My advice is to wait as long as possible to upgrade your Production environment to v24, especially if you are running business critical workloads. and if you think that the list of bug fixes is scary, then you can expect many more bugs as more and more customers start using v24..

My personal experience is that a new major version is not stable until after 5 or 6 service packs...

/Keld.

-------------------------------------------

[Olgun Onur Ozmen]

Hi @Keld Mollnitz , @Leon Carroll , 

Thanks for comment.

In v21, the 5-6 service packs you mentioned arrived before the EOS expired, but in v24, new features are constantly being added, so it naturally takes longer to reach that number of service packs. The EOS expiring is a bit of a problem. That's why we may have to opt for an earlier version. That's why I wanted to bring up this topic.

------------------------------
Olgun Onur Ozmen
https://www.linkedin.com/in/olgunonurozmen/
------------------------------

[Leon Carroll]

v24.4.1 works well and is stable with a few workarounds. Use 24.3 agents for Unix, SQL Agent, RA_JMS with JDK11, LDAP sync.  Use a v21 agent for Windows where a credential manager is used though this should be fixed in the next hotfix. If you are doing a fresh linux install you may be able to use the 24.4.1 agent directly.

Search the schedules for where Maximum runtime is set, check if there is any code in the process tab and move it to a script if it causes an error.  With events, swap pset to set for anything in the process tab where max runtime is set.

Otherwise, I think everything else is ok.  We've been running v24.3 in prod for six months.   There are quite a few issues fixed in 24.4.1 that are in 24.3.  24.4.1 is effectively the 5th service pack since the name freezes at 24.4 

-------------------------------------------

[Leon Carroll]

The Unix agent issue is now fixed in 24.4.1 HF2, I've tested upgrading agents and running jobs.  whoami returns the correct username.  I'm testing the Windows agent now but that looks ok so far.  There was a fix related to schedules and max runtime so I will retest this tomorrow.

-------------------------------------------