De-Marshalling Of Web Service Method Call Argument Objects That Contain HashMap Properties, Can Lead To The Corruption Of the HashMap Property
Last updated on NOVEMBER 05, 2016
Applies to:Oracle GlassFish Server - Version 2.1.1 to 2.1.1 [Release 2.1]
Information in this document applies to any platform.
Only seen with 2.1.1 p7 and later.
Due to the nature of this problem, it is hard to provide a definitive set of symptoms. Problems could be seen with incorrect processing or results from a Web Service invocation, or potentially NullPointerExceptions could been seen. It's possible that the number of entries in the encapsulated HashMap in a web service parameter object would appear to change during the processing of the web service method call.
The problem can be first seen in GlassFish 2.1.1 p7 through to 2.1.1 p20, which included JAXB 2.1.13 as part of the Metro web services stack.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms