Open GoogleCodeExporter opened 8 years ago
I've found out the problem. JAXB is not thread-safe for
marshal/unmarshal/validate
http://stackoverflow.com/questions/3584821/jaxbcontext-newinstance-memory-leak
There is also link on how to fix this.
http://jaxb.java.net/guide/Performance_and_thread_safety.html
Can you guys make this thread-save/servlet safe for the next version?
Original comment by anb1...@gmail.com
on 16 Sep 2011 at 5:18
Was your problem about memory not being freed after marshalling (due to memory
leaks?) or just about the total amount of memory required for marshalling.
For the second case, I'm exploring the possibility of marshalling chunk by
chunk, see:
http://stackoverflow.com/a/9297719/809536
Original comment by theb...@emanueleziglioli.it
on 15 Jan 2013 at 9:32
Original issue reported on code.google.com by
anb1...@gmail.com
on 15 Sep 2011 at 9:59Attachments: