How to Avoid Conflicting Third Party Jar Files Being Loaded in The CLASSPATH for All NEPs (Doc ID 2101899.1)

Last updated on FEBRUARY 16, 2024

Applies to:

Symptoms

We are unable to implement a new cartridge as an existing cartridge already has jar files that conflict with the new cartridge jar files. We have 2 Network Elements that require conflicting versions of third party jar files. As a workaround, we created a second NEP and separated the elements whose cartridges have the conflicting jars, in two separate NEPs. However, after restart, both JNEP.diag files for both NEPs contain all jar files from all deployed cartridges.

We need the different NEPs to default to execute separate Java JVMs, to load different sets of jar files on each Java process - each Java process should load only the cartridge jar files for the network elements which are on the corresponding "parent" NEP.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.