Hi again,
To the respected ActiveMQ Team, appreciate your kind response on this matter
as I have performed the action based on the following advise given by
Oracle.
The result was the lock did not occurred for some time. But after 5 to 6
hours, the message is getting displayed again.
The messag
It appears to me that org.apache.activemq.network.ForwardingBridge does not
have the appropriate constructor and setters for the localBroker and
remoteBroker 'String' params. You may want to check and see if there is a
jira out for this.
Joe
Get a free ActiveMQ user guide at www.ttmsolutions.com
Have you checked out
http://activemq.apache.org/message-cursors.html
4.1.1 seems to store some kind of message reference in memory so broker may
run out of memory even if persistence is enabled.
Maarten Dirkse-2 wrote:
>
> Allright, the sleuthing continues. I did a heap dump of the broker vm
