Hi,
From the documentation on Performance and Thread Safety there is a suggestion of caching Unmarshallers ( potentially Thread locally ) to improve performance.
http://jaxb.java.net/guide/Performance_and_thread_safety.html
However by doing this we have seen that the unmarshallers seem to hold onto large amounts of internal state, even post unmarshal, and therefore you can get memory spikes depending on the concurrency level and message size.
Is this a known issue and do these unmarshallers hold onto to this structure for any necessity ?
Thanks,
Liam
Liam Knox, Vice President
Morgan Stanley MUFG Securities Co., Ltd. | Post-Trade Technology
Yebisu Garden Place Tower | 4-20-3 Ebisu, Shibuya-ku
Tokyo, 150-6008
Phone: +81 3 5424-6436
Liam.Knox_at_morganstanleymufg.com<mailto:Liam.Knox_at_morganstanleymufg.com>
--------------------------------------------------------------------------
NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or views contained herein are not intended to be, and do not constitute, advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform and Consumer Protection Act. If you have received this communication in error, please destroy all electronic and paper copies and notify the sender immediately. Mistransmission is not intended to waive confidentiality or privilege. Morgan Stanley reserves the right, to the extent permitted under applicable law, to monitor electronic communications. This message is subject to terms available at the following link:
http://www.morganstanley.com/disclaimers. If you cannot access these links, please notify us by reply message and we will send the contents to you. By messaging with Morgan Stanley you consent to the foregoing.