When this is happening, how often are full GCs happening and how long are they taking on average, and are young gen GCs occurring between the old gen GCs?
Also, do you believe that the compaction phase ( https://www-01.ibm.com/support/knowledgecenter/mobile/#!/SSYKE2_6.0.0/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_gc_compact.html) is occurring during the full GCs? Old Gen fragmentation can cause near-continuous GCs under HotSpot's CMS strategy because its Old Gen GCs don't compact Old Gen, so I wonder if something similar could be happening here. Tim On Jun 29, 2015 2:38 AM, "cdelgadob" <carlos.delg...@proyecti.com> wrote: > Hi Tim, Paul, > > Thanks a lot for your suggestions, both very concise and thoughtfull. > > Re your questions: > > - Message size: Actually they are quite small, it's just a, identifier that > points to a record in a DB. So the DB has to be accesed in order to process > the message (I know it's odd and probably wrong, but I can't figure out why > this is done like that :S) > > - Message processing: Not too memory intensive. There's something in the > code called top and bottom transaction, which I can't figure out what they > mean. Maybe they are blocking something and I haven't seen it yet. > > - Memory usage: When a full GC is performed, the memory level falls to it's > previous usage, so there's no memory leak, it's just something it's doing > and GCed. What I don't know is what it is. I'll try to use VisualVM to find > out... > > - GC algorithm: We are using gencon, and I think what you say about the old > and new object heap zone *might* be relevant. I'll check this out. > > - Update Java and ActiveMQ versions: Yes, that was my first proposal. It > should be done even without problems. But this is an enterprise > environment, > and everything goes really slow. I'll try to update the AMQ libraries, > assuming the can tal with a 5.9 broker without problem, right? :D Tha Java > update will come afterwards. > > - Broker logs: There's nothing that shows errors in the broker, not even > the > PFC (unfortunatelly). > > Paul I fully agree with your bottomline: figure out what's going on befor > changind parameters and everything, let's see if I'm lucky today. > > > Thanks again for your suggestions, I'll keep working on this. > > Best > > Carlos > > > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/JMS-Client-HANGING-AMQ-5-9-AIX-6-1-tp4698204p4698321.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
