Issue between Informatica Cloud and Dynatrace

[kk00734604]

Hello Everyone,

We have identified an issue between Informatica Cloud and Dynatrace. The issue is documented in the links below, and Informatica Support is already tracking it.

Dynatrace (APM Tool) Impact on Informatica Cloud Agent Services and Tasks.

https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/No-access-to-classes-jsa-might-be-thrown-...

https://community.dynatrace.com/t5/Open-Q-A/OneAgent-Process-Injection-Incompatibility-with-classes-...

Based on the latest information provided by Informatica, the incompatibility should be resolved in OneAgent version 1.301 and later.

However, we currently have a newer version of OneAgent installed on our SE Informatica EC2 instances (infapwcnp and infaiicsnp), and the issue still persists.

Could anyone help on this?

[p_devulapalli]

@kk00734604 Can you please reach out to DT Support incase not already raised ?

[kk00734604]

Thanks for your response, I already raised a support case, they suggested us to raise RFE.

[sujit_k_singh]

Hi @kk00734604 

I have gone through Informatica article, my observation is the DTM crash stack trace explicitly shows OneAgent version 1.303 (agent/bin/1.303.62.20241129-131342). This is newer than 1.301, confirming your original report the fix in 1.301 addressed the classes.jsa file lock issue specifically, but did not resolve the liboneagentjava.so deadlock or the JVM init crash, which are separate bugs.

The Four Issues Are Not All the Same Bug
This is the key point Informatica's article makes clear. There are at least four distinct incompatibilities, not one:

1. classes.jsa file lock — fixed in 1.301 (upgrade blocker)
2. pthread_rwlock_rdlock deadlock in liboneagentjava.so — present in 1.303, status unknown
3. liboneagentproc.so conflict at JVM init — separate injection timing issue
4. TechnologyDetectionIntrospectionUtils OOM — introduced or worsened post-July 2025 IDMC release
Issues 2, 3, and 4 are not covered by the 1.301 fix and require separate Dynatrace support engagement.

The 1.301 fix only resolved the classes.jsa file lock. Your environment is hitting at least two additional bugs (liboneagentjava.so deadlock, introspection OOM) that are present in 1.303 and require separate fixes or explicit process exclusions. The safest path right now is process-level deep monitoring exclusion for all Informatica executables, followed by a Dynatrace support escalation referencing the specific stack traces above.

Thanks,

Sujit