> http://activemq.2283324.n4.nabble.com/Garbage-collecter-out-of-memory-tp4702160p4702243.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
arn a lot
about GC in the process.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Garbage-collecter-out-of-memory-tp4702160p4702243.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
as for the ActiveMQ process. This is
> the application process:
>
> <http://activemq.2283324.n4.nabble.com/file/n4702192/cpuMem2.png>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Garbage-collecter-out-of-memory-tp4702160p4702192.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
FYI the image from the previous post was for the ActiveMQ process. This is
the application process:
<http://activemq.2283324.n4.nabble.com/file/n4702192/cpuMem2.png>
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Garbage-collecter-out-of-memory-tp4702160p470219
ith the relatively large and complex application
(24,000 classes). Thanks.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Garbage-collecter-out-of-memory-tp4702160p4702191.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
rospect.BasicClassIntrospector.forDeserialization(BasicClassIntrospector.java:11)
>>
>> 11:12:56,835 INFO [stdout] (Deferred Command #1) at
>>
>> com.fasterxml.jackson.databind.DeserializationConfig.introspect(DeserializationConfig.java:547)
>>
>> 11:12:56,835 INFO [stdout] (Deferred Command #1) at
>>
>> com.fasterxml.jackson.databind.deser.DeserializerCache._createDeserializer(DeserializerCache.java:325)
>>
>> 11:12:56,835 INFO [stdout] (Deferred Command #1) at
>>
>> com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCache2(DeserializerCache.java:263)
>>
>> 11:12:56,835 INFO [stdout] (Deferred Command #1) at
>>
>> com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCacheValueDeserializer(DeserializerCache.java:2
>>
>>
>> I can't figure out why the garbage collector would be working so hard.
>> Any
>> advice would be greatly appreciated? Thanks
>>
>>
>>
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/Garbage-collecter-out-of-memory-tp4702160.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
; com.fasterxml.jackson.databind.deser.DeserializerCache._createDeserializer(DeserializerCache.java:325)
>
> 11:12:56,835 INFO [stdout] (Deferred Command #1) at
>
> com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCache2(DeserializerCache.java:263)
>
> 11:12:56,835 INFO [stdout] (Deferred Command #1) at
>
> com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCacheValueDeserializer(DeserializerCache.java:2
>
>
> I can't figure out why the garbage collector would be working so hard. Any
> advice would be greatly appreciated? Thanks
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Garbage-collecter-out-of-memory-tp4702160.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
View this message in context:
http://activemq.2283324.n4.nabble.com/Garbage-collecter-out-of-memory-tp4702160.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.