ah...figured it out. In my activemq.xml I had the property useDatabaseLock
set as "true" on the JDBCPersistenceAdapter. This was working fine with 5.0
but with 5.1 , this is causing the broker to be terminated? Is this per
design?
Setting this property to "false" fixed it but I was wondering if t
Hi Rob
I moved to 5.1 release but now I can't even start the broker :( using my
activemq.xml config for 5.0.0. After a couple of minutes I get the following
exception. Is there a keepAlive configuration I need to set in the URL now?
ERROR ManagedTopicRegion - Could not stop service:
Thank You!
Is 5.1 backwards compatible with 5.0 configurattion? i.e if we get 5.1, we
shouldn't need to change any of our previous configuration we did with 5.0,
correct? (e.g. connect Url parameters, wireformat parameters etc)
rajdavies wrote:
>
>
> On 16 Jun 2008, at 23:12, jaya_srini wrot
Thank You!
Is 5.1 backwards compatible with 5.0 configurattion? i.e if we get 5.1, we
shouldn't need to change any of our previous configuration we did with 5.0,
correct? (e.g. connect Url parameters, wireformat parameters etc)
rajdavies wrote:
>
>
> On 16 Jun 2008, at 23:12, jaya_srini wrot
On 16 Jun 2008, at 23:12, jaya_srini wrote:
hi all
I saw several posts regarding the async exception (listed below) in
logs
with ActiveMQ 5.0.0. We are also seeing this exception randomly in
the logs,
the bad part is it breaks the connection between Broker and the
client even
tho the br
