Closed brianoliver closed 8 years ago
The SOAP message marshaller and unmarshaller in the Windows SoapConnection class should both be properly synchronised to stop concurrent access.
This issue was imported from JIRA ORACLETOOLS-295
Reported by @thegridman
Marked as fixed by @thegridman on Monday, February 29th 2016, 3:30:42 am
The SOAP message marshaller and unmarshaller in the Windows SoapConnection class should both be properly synchronised to stop concurrent access.