Reduce amount of classpath scanning during integration tests execution

Description

It has been noted by multiple people that classpath scanning that we do causes:

  1. OutOfMemory errors when out-of-process node or webserver is started;

  2. Affects performance of test pack execution since classpath scanning is happening multiple times.

Few code pointers in this regard:

  • AbstractAMQPSerializationScheme.customSerializers does an extensive scan across all the jars in the classpath including 3rd party libraries for instances of SerializationCustomSerializer;

  • ClassloaderUtils.scanJarForContracts performs scan for instances of Contract including our core module. Every such scan takes approximately 1 second. When core excluded scan takes around 50ms

CVSS Vector

None

Status

Assignee

Viktor Kolomeyko

Reporter

Viktor Kolomeyko

Labels

CVSS Score

None

Feature Team

Enterprise Robustness

Target Version/s

Corda 3.3

Ported to...

None

Fix versions

Priority

Medium