[activemq-user] OutOfMemoryError with ActiveMQ3.0

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[activemq-user] OutOfMemoryError with ActiveMQ3.0

Matias Otero
Hi,
 
ActiveMQ3.0 has crashed on me with an OutOfMemoryError after having been
running for about a week. There is very little information in the log file:
 
caught exception consuming packet: CONSUMER_INFO: id = -25818 ConsumerInfo{
browser = false, destination = PAYMENT_FDRA, consumerIdentifier =
'ID:trawler-40050-1118378610110-41030:0.3.17535' , clientId =
'ID:trawler-40050-1118378610110-41030:0' , sessionId = '3' , consumerName =
'' , selector = '' , startTime = 1118787962308, started = true, consumerNo =
17535, noLocal = false, prefetchNumber = 10, consumerKey =
'[ID:trawler-40050-1118378610110-41030:0:]'  }
java.lang.OutOfMemoryError
 
The maximum heap size is set 512Mb (which is the default I believe), and I
am using the default configuration supplied. Are there any known issues with
the default configuration?
 
Cheers,
Matias.

Reply | Threaded
Open this post in threaded view
|

Re: [activemq-user] OutOfMemoryError with ActiveMQ3.0

Thomas Sauzedde
Matias Otero a ?crit :

>Hi,
>
>ActiveMQ3.0 has crashed on me with an OutOfMemoryError after having been
>running for about a week. There is very little information in the log file:
>snip
>The maximum heap size is set 512Mb (which is the default I believe), and I
>am using the default configuration supplied. Are there any known issues with
>the default configuration?
>  
>
I don't know what is the default config, but what you described looks
like a "in-memory" persistence or message TTL(Time To Live) issue.

If you're using persistence and if you're using ActiveMQ without a DB
for message persistence and/or if the message TTL is set to a big big
value or  infinite (0 => infinite, and this is the default for what i
remember), your broker will store all the messages  "in-memory" until
OutOfMemoryException !

So :
 - check your config for the "<persistence>" block
 - check if you are using persistence or not in you send / publish
method call
 - check if you set a TTL in your send / publish method call