java.lang.LinkageError: loader constraint violation: loader 'app' (instance of jdk.internal.loader.ClassLoaders

[adobe]

java.lang.LinkageError: loader constraint violation: loader 'app' (instance of jdk.internal.loader.ClassLoaders

[baubakg]

Problem resolved but not reproduced as unit test.
Adding the package in the IBS.CLASSLOADER.STATIC.INTEGRITY.PACKAGES environment variable solves this.

[baubakg]

Have been able to reproduce issue. Problem related to lazy instantiation of a class which is not loaded in the class loader.

[baubakg]

The issue shows up it seems due to lazy instantiation of classes which are not in the static integrity path. In this case neither of the calls actually accesses Element.

The exact use case definition is, given a call similar to the following:

{
	"timeout": 1200000,
	"callContent": {
		"call1": {
			"class": "com.adobe.campaign.tests.bridge.testdata.issue34.callerpkg.CalledClass1",
			"method": "calledMethod",
			"returnType": "java.lang.String",
			"args": [
			]
		},
		"call2": {
			"class": "com.adobe.campaign.tests.bridge.testdata.issue34.callerpkg.CalledClass2",
			"method": "calledMethod",
			"returnType": "java.lang.String",
			"args": [
			]
		}
	}
}

Here are the circumstances:

• At least two calls.
• None of the called methods actually use the class MiddleMan
• The first call, call1, accesses a class that contains an unused method that "returns" MiddleMan.
• The second call, call2, accesses a class that has a constant is if the type MiddleMan. The constant is initiated using a factory in a different package.
• The factory class should be in a different package than the packages for call1 and call2.
• None of the packages (even in a higher package level) are declared in the bridgeService property : IBS.CLASSLOADER.STATIC.INTEGRITY.PACKAGES

[baubakg]

This is not a regression.

The difference is the dynmic loading of the classes.
Here is the exact problem definition:

We have two classes a.lass1, a.Class2 each calling a.ClassA.
If we include a. in our path, all is well.
If Class2 calls another class b.Class3 which initself calls a.ClassA you will get the LinkageError. This is because b.Class3 will NOT be loaded by our classloader, and it will access a.ClassA.

Two solutions exist:

1. Our classloader systematically loads anything it can load.
2. We require users to load their packages.

Option 1 will probably load a lot of data in memory.
Option 2 will be less memory, but requires that users configure the project better.