24.4.0.HF2 Released

[Timothy Yanosko]

FYI  -- 24.4.0.HF2 has been released.

[Olgun Onur Ozmen]

they will have to release a fix. just last week I saw that awi could not work on tomcats in my new v24.4.hf1 installation. hf2 also seems to be fixed, we will see.

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

[Keld Mollnitz]

Hi @Olgun Onur Ozmen,

do you have issues with AWI v24 on Tomcat...? pls elaborate. I'm struggling to get my v24.4 AWI up and running on Tomcat, so this might be due to a bug ?

/Keld.

[Olgun Onur Ozmen]

Hi @Keld Mollnitz ,

v24.4.hf1 awi had a lot of bugs like websocket errors on tomcat 9/10, we had difficulty even creating objects or navigate menu's. i progressed for now by using jetty instead of tomcat. i suggest jetty on v24.4.hf1.   i opened a case. 4-5 days later a HF2 was released bugfix about awi not working on tomcat 9/10. i will try it HF2 today. i hope it is solved.

thanks.

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

[Timothy Yanosko]

I just got an HTTP 500 error message after we patched the tomcat web server.  In order to get the AWI running again I needed to delete the war file, install the war file and restart tomcat.   This is somewhat the same problem / symptoms I encountered before HF2.   I've opened a case.  Stay tuned.

[Timothy Yanosko]

As it turns out the file Automic.Automation_24.4.0.HF2_2025-04-30.zip which was downloaded on 5/1/25 @ 1:32 PM CDT US contained the HF1 web component.  Downloaded "HF2" again yesterday and ran the scenarios which generated the error and they did not reoccur.

[Maria Joseph Vimalan]

Dear all

After we patched our Automic to Version 24.4. HF2 we noticed that agent is working as expected and we received the article that the issue is fixed in 24.4 HF2 but wasn't. The agent is not using the username mentioned in the login object but always uses root user or in which agent is running. Is there a way to get a fix for it as we are planning for production in August. 

Unfortunately workaround is also not working as mentioned. 

https://knowledge.broadcom.com/external/article?articleNumber=392027

From my view, this is serious bug which should be resolved and update to be released.  We have hundreds of agents connected and making changes in each agent is time consuming and not affordable..

Any inputs possible from anyone please.  

[Shannon Hebert]

Hi Maria,

If you haven't yet created a support ticket, please do so, and we'll be glad to work with you toward a resolution.

Thank you,

-Shannon

------------------------------
_______________________________________
Shannon Hebert
Head of AOD Automation Support
Broadcom Software | Agile Operations Division
_______________________________________
------------------------------