Zagan wrote
> Can you please check if your .log files in the /data directory are cleaned
> up? On basis of the information I suppose this behaviour is due to a
> misconfiguration of your clients.
> If this is the case often broken log file cleanup is a symptom.

I get the same error as brought up in this thread (KahaDB failed to store to
Journal).  And yes, I also have a problem with the numbered .log files not
all getting cleaned up (most files are removed appropriately).  I have
suspected a client configuration problem for a long time, but can't figure
out what's wrong -- even with TRACE logging turned on.  In the meantime, I
have to cope with ActiveMQ crashing (i.e., shutting itself down) about every
two days.  The logs point to a disk storage problem, but I have plenty of
space, so that's not the issue!  I've tried a couple of different Linux
boxes and both local and NFS mounts, and this issue occurs on both of them.

I'm at a loss!!  I'm running 5.8.0...

Mark



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/ActiveMQ-crashes-frequently-tp4305407p4666469.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to