A Web Service Being Invoked with a MTOM Attachment in Oracle Glassfish Server is Not Aware the Attachment is Truncated as a Result of a Connection Failure
(Doc ID 1333669.1)
Last updated on OCTOBER 15, 2020
Applies to:Oracle GlassFish Server - Version 3.0 to 3.1 [Release 3.0 to 3.1]
Oracle GlassFish Server - Version 3.1 and later
Information in this document applies to any platform.
***Checked for relevance on 15-Aug-2013***
When attempting to upload a large SOAP MTOM (Message Transmission Optimization Mechanism) attachment as part of the invocation of a web service, if the upload is interrupted by some sort of communications failure, then:
- No error is seen by the web service being invoked.
- The system JAXWSServlet that acts as an intermediary does see an exception, but does not relay this information to the web service when it invokes it.
The issue is that the web service receives an incomplete upload and is not aware that this has happened unless it has its own checks built in so that the web service can confirm that the upload matches what the client said it sent.
The error reported by the JAXWSServlet would be similar to this one:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document