Kahadb - Getting Worried Message

[javixcm <ja...@gmail.com>]

Hi everybody,

Recently We implemented in production a ActiveMQServer. (It has 5 days
working),everything was perfect but today I saw in the hawtio-JMX Web
Console the following message(property health/current status):

"Getting Worried {org.apache.activemq.FreeDiskSpaceLeft: WARNING Store limit
is 19329 mb, whilst the data directory:
/.../apache-activemq-5.9.0/data/kahadb only has 19283 mb of usable space
from KahaDBPersistenceAdapter[/.../apache-activemq-5.9.0/data/kahadb] ,  }"

It means I have to delete the log files? or increase some property in
persistent?

thank you.





--
View this message in context: http://activemq.2283324.n4.nabble.com/Kahadb-Getting-Worried-Message-tp4679825.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: Kahadb - Getting Worried Message

[AmolG <am...@accelyakale.com>]

I am new to ActiveMQ. I am using latest stable release i.e ActiveMQ 5.12.1
Release.
 
I have taken ActiveMQ C client code from
“http://svn.apache.org/repos/asf/activemq/sandbox/openwire-c/”, compiled it
and started ActiveMQ server and trying to execute C client producer.
But programs prompts “No space left on device (28)” error. 

After executing C client, ActiveMQ server shows error like “Transport
Connection to: tcp://127.0.0.1:52546 failed: java.io.EOFException”.
 
 
Please guide me.



--
View this message in context: http://activemq.2283324.n4.nabble.com/Kahadb-Getting-Worried-Message-tp4679825p4705740.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: Kahadb - Getting Worried Message

[javixcm <ja...@gmail.com>]

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.

Re: Kahadb - Getting Worried Message

[artnaseef <ar...@artnaseef.com>]

Congrats on getting ActiveMQ into production!

That warning, although it's not clear from the message, indicates that the
store limit is too high for the amount of space available on the disk and
won't prevent running out of disk space -- at least, if I'm reading the code
correctly.

                    if ((storeLimit - storeSize) > dirFreeSpace) {

So, either free up disk space from other sources (not ActiveMQ data files)
or decrease the store limit in order for it to be effective.

Never remove kahadb files unless you want to wipe all of the messages, in
which case, wipe the entire directory - while the broker is down.



--
View this message in context: http://activemq.2283324.n4.nabble.com/Kahadb-Getting-Worried-Message-tp4679825p4679839.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.