topic Re: OneAgent Process Injection Incompatibility with classes.jsa (ONE-19712) in Open Q&A

OneAgent Process Injection Incompatibility with classes.jsa (ONE-19712)

GaborBernics — Mon, 03 Mar 2025 11:15:34 GMT

Hello,

The issue has already been registered under ONE-19712 and was fixed in OneAgent release 1.159.

However, OneAgent release 1.293.153.20240702-150912 is still blocking the update mechanism of Informatica Secure Agent 72.32 (February Release).

2025-02-28 14:21:23,201 UTC tid="31" tn="pool-2-thread-1" ERROR [agentAuditLogger] - [AGENT_10023] AgentCore dependency download error. Error [Download failed for zip file {/informatica_agents/downloads/package-agentcoreupgrade.7232.zip} from CDN URL {https://icsdownloadsecure.informatica.com/IICS/pkgmgr_dmus/files/package/agentcoreupgrade/7232/linux64/package-agentcoreupgrade.7232.zip} with error /informatica_agents/downloads/package-agentcoreupgrade.7232/package/jdk17/lib/server/classes.jsa

(Ignore the download in the output; it's not related to the file transfer. The ZIP file has already been fetched with the proper MD5 hash.)

It seems the issue was not properly fixed or has reoccurred with the new JDK.
Disabling Process Injection does NOT provide a workaround, as it does not ensure compatibility with Informatica Secure Agent and reduces Dynatrace's capabilities.

Has this already been reported to the Dynatrace Product Team?

Best regards,
Gabor

Re: OneAgent Process Injection Incompatibility with classes.jsa (ONE-19712)

PacoPorro — Mon, 03 Mar 2025 07:22:01 GMT

For updates related to a support ticket, it would be best to inquire directly within the ticket itself.

Re: OneAgent Process Injection Incompatibility with classes.jsa (ONE-19712)

GaborBernics — Mon, 03 Mar 2025 07:27:06 GMT

It's the first response to Dynatrace.
Do you already have a support ticket or an open change for the issue?
Can we check it?

I don't want to duplicate it.

Re: OneAgent Process Injection Incompatibility with classes.jsa (ONE-19712)

GaborBernics — Mon, 03 Mar 2025 09:20:01 GMT

@PacoPorro
Based on the official (?) Dynatrace feedback, the issue already resolved in OneAgent release notes version 1.301 — Dynatrace Docs