It seems that version 5.3.2 solve the issue.
So, for all the people: if you have some problems with kahadb .log files,
try to updat to the last ActiveMQ version.
Best regards
rajdavies wrote:
>
> Firstly - upgrade to 5.3.2 - there are some minor bug fixes - but also
> performance enhancements.
hank you very much. I have updated to version 5.3.2. Now I'll monitor the
situation.
I'll also check via JMX the subscriber list. But the only subscriber are the
MDBs and all the MDBs are defined as follow:
@ActivationConfigProperty(propertyName = "destinationType", propertyValue =
"javax.jms.Top
Firstly - upgrade to 5.3.2 - there are some minor bug fixes - but also
performance enhancements. I would check that you don't have a durable
subscriber in your system that was active at some point - but is no loner - you
can use JMX to do this
On 2 Jul 2010, at 09:51, RJtokenlanring wrote:
>
