-
Bug
-
Resolution: Not an Issue
-
P3
-
None
-
9-repo-jigsaw
-
generic
-
generic
NSK jdi and jdb tests fail when running with jdk-module-image.
Several issues:
1. ClassAnalyzer doesn't handle multiple service-provider configuration files of the same service (in different jars)
sa-jdi.jar and tools.jar both contains service providers for the JDI connector (i.e. both have META-INF/services/com.sun.tools.jdi.connect.Connector
The debugging and sajdi modules should both have the META-INF/services/com.sun.tools.jdi.connect.Connector file
2. The service provider class are loaded by the class loader of com.sun.tools.jdi.Connector and com.sun.jdi.connect.spi.TransportService classes.
These two service classes are in the debugging module while the SA service providers are in sajdi. The debugging module and sajdi module will need to be loaded by the same class loader.
3. SA tools such as jdb, jmap, jinfo, jstack, and jsadebugd requires sajdi module
Several issues:
1. ClassAnalyzer doesn't handle multiple service-provider configuration files of the same service (in different jars)
sa-jdi.jar and tools.jar both contains service providers for the JDI connector (i.e. both have META-INF/services/com.sun.tools.jdi.connect.Connector
The debugging and sajdi modules should both have the META-INF/services/com.sun.tools.jdi.connect.Connector file
2. The service provider class are loaded by the class loader of com.sun.tools.jdi.Connector and com.sun.jdi.connect.spi.TransportService classes.
These two service classes are in the debugging module while the SA service providers are in sajdi. The debugging module and sajdi module will need to be loaded by the same class loader.
3. SA tools such as jdb, jmap, jinfo, jstack, and jsadebugd requires sajdi module