In case of http/https URL not returning valid WSDL definition, RuntimeWSDLParser does not close the first URL InputStream opened before trying the same URL with ?wsdl appended, leading to a resource leak, which is typically constant, but can start accumulating in case WSDL definitions are resolved dynamically in runtime.
It can also interfere with bytecode advices around URLConnections.
Affected version: jaxws-rt:4.0.2
In case of http/https URL not returning valid WSDL definition, RuntimeWSDLParser does not close the first URL InputStream opened before trying the same URL with ?wsdl appended, leading to a resource leak, which is typically constant, but can start accumulating in case WSDL definitions are resolved dynamically in runtime.
It can also interfere with bytecode advices around URLConnections.