This is known bug in Jboss fuse 6.1 and the issue is fixed in JBoss Fuse 6.1
R2P5 rollup patch5.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I am using NFS.
amq...@txnref1.nyc:/u/amqgod> stat -f ~/kahadb/
File: "/u/amqgod/kahadb/"
ID: 0Namelen: 255 Type: nfs
Block size: 65536 Fundamental block size: 65536
Blocks: Total: 245760 Free: 210550 Available: 210550
Inodes: Total: 1048576Free: 1043878
Is thi
thanks for sharing this info Paul :-)
On 10 September 2014 17:33, Paul Gale wrote:
> All of the following is assuming you're using Linux. I'm using RHEL 6.3 to
> mount an NFSv3 based device using autofs.
>
> I should have added that the issue for me was that I had specified the
> wrong block size
All of the following is assuming you're using Linux. I'm using RHEL 6.3 to
mount an NFSv3 based device using autofs.
I should have added that the issue for me was that I had specified the
wrong block size values for the rsize/wsize parameters in the autofs mount
configuration for the device I was
In my particular case I fixed it when I realized that I had the NFS mount
settings for the mount where the KahaDB message store was located
mis-configured. Since correcting the settings I've not had a single
problem.
Are you using NFS?
Thanks,
Paul
On Tue, Sep 9, 2014 at 2:49 AM, khandelwalanuj
I am also seeing the same exception with ActiveMQv5.10. It comes infrequent
and non-reproducible.
I have already posted
http://activemq.2283324.n4.nabble.com/ActiveMQ-exception-quot-Failed-to-browse-Topic-quot-td4683227.html#a4683305
ActiveMQGods can you please help us out here. ?
Thanks,
Hi Gary,
I'd love to be able to provide a failing unit test for you. However, this
exception occurs infrequently and so far only on one machine. I made a
backup copy of the message store prior to rebuilding it if you think that
examining it might help? It contains only a single 32mb journal file,
I really thought all of these kahaDB index corruption issues were
sorted, but if you can reproduce in 5.9 we have a problem that needs
work. the key to any resolution is a reproducible test case.
In any event, you should be able to recover by rebuilding the index,
just deleting the db.data file be
Anyone have any some thoughts about this?
Thanks,
Paul
On Tue, Oct 1, 2013 at 12:50 AM, Paul Gale wrote:
> Hi,
>
> I'm using ActiveMQ 5.8.0 on RHEL 6.1
>
> I have noticed the following exception appearing in my broker's log
> file. It appears to be related to the once hourly check for expired
>
Hi,
I'm using ActiveMQ 5.8.0 on RHEL 6.1
I have noticed the following exception appearing in my broker's log
file. It appears to be related to the once hourly check for expired
messages, as these occur at _exactly_ the same time past the hour, as
given by the expireMessagesPeriod attribute on our
10 matches
Mail list logo
