Thanks a lot for your answer, I cleaned the server,some daemons are running
in there, they had big log files .
Also I changed some configurations in Activemq.xml, because I saw another
log with a conflict between kahaDB maxFileLength and tempUsage.
My initial configuration was:
.....
<kahaDB directory="${activemq.data}/kahadb"/>
.........
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage percentOfJvmHeap="70" />
</memoryUsage>
<storeUsage>
<storeUsage limit="50 gb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="30 gb"/>
</tempUsage>
</systemUsage>
</systemUsage>
.........................
I changed it for this:
<kahaDB directory="${activemq.data}/kahadb" journalMaxFileLength="32mb"/>
....................
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage percentOfJvmHeap="70" />
</memoryUsage>
<storeUsage>
<storeUsage limit="50 mb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="32 mb"/>
</tempUsage>
</systemUsage>
</systemUsage>
...................
Currently everything is running very fine, but I'm not sure if it is because
I restarted activeMQ or for this new configuration. So I will follow the
log and status in the next days.
I appreciate a lot your help, thanks!
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Kahadb-Getting-Worried-Message-tp4679825p4679843.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
