Uploaded image for project: 'Corda'
  1. CORDA-1355

Reduce amount of classpath scanning during integration tests execution

    Details

    • Feature Team:
      Enterprise Robustness
    • Target Version/s:
    • Sprint:

      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

        Attachments

          Activity

            People

            • Assignee:
              Viktor.Kolomeyko Viktor Kolomeyko
              Reporter:
              Viktor.Kolomeyko Viktor Kolomeyko
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: