James, this is related to a bug:
https://issues.apache.org/jira/browse/AMQ-4210
Will have a fix in shortly.
On Tue, Oct 30, 2012 at 8:52 AM, James Green wrote:
> Gary,
>
> Spoke config:
>
>name="plenty-hub-01"
>duplex="true"
>c
Hi All,
Am getting exception like
javax.jms.JMSException: Wire format negotiation timeout: peer did not send
his wire format.
when am using in heavy traffic middle of the process getting this exception
after some time it will automatically solved and processing.
Can you conform why it is gett
No, it's not.
the memoryUsage limit is for messages cached within the broker ready for
dispatch. it should be a portion of the heap usage (50-70%). you still need
heap memory for normal usage (threads, object creation, etc). if you set
memoryLImit to the same as the JVM heap, you can run OOM.
Hope
I've added those checks after... so this is problem.
Thanks!
2012/12/6 gtully [via ActiveMQ]
> note: the attributes checkForCorruptJournalFiles="true" and
> checksumJournalFiles="true"
> must be enabled when the journal files are originally created. In
> other words. they dont apply retrospecti
note: the attributes checkForCorruptJournalFiles="true" and
checksumJournalFiles="true"
must be enabled when the journal files are originally created. In
other words. they dont apply retrospectively.
On 6 December 2012 13:44, RJtokenlanring wrote:
> HI, thank you.
> No, this not worked. File is
Not sure if it helps in your case but can you try deleting the db.data index
file and restart your broker? It will then rebuild the index based on the
journal files. If the journal files are complete bogus though, this approach
may not help.
Regards,
Torsten Mielke
tors...@fusesource.com
tmi
Hello,
Not sure about your actual problem but the FuseSource Security Guide for
ActiveMQ has a good tutorial for configuring LDAP based authentication and
authorization. Perhaps this can help you?
http://fusesource.com/docs/broker/5.5/security/LDAP.html
Perhaps this blog post is also of inter
