Hi, I'm running a tomcat application which uses the AdWords API version 1.27.0.
I have found that after around 7-10 days of running, the application gets closer and closer to the 2GB heap limit and the JVM is unable to GC efficiently. Then, I get an OutOfMemory exception and the application needs to be restarted. I have taken a heap dump and have found that most of the objects on the heap are strings containing XML messages, referenced from SAX2EventRecorder objects. It looks like this is part of Apache Axis 1.4, pulled in by the adwords-axis dependency required by the AdWords API. Does anyone know what would cause a memory leak here, and how it could be prevented? Thanks! -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
