Thanks,
where to mention this property vm://localhost?create=false&async=false
i mean which configuration file is it broker-config.xml?
or to use following the code,
ActiveMQConnectionFactory factory = new
ActiveMQConnectionFactory("vm://localhost?create=false");
i go this error
An error oc
Actually async is faster normally - this is a work around until 5.2 -
the issue is fixed in trunk
On 10 Jul 2008, at 16:47, Demian Mrakovich wrote:
Thanks for the bump and for the work-around!
But - turning off async dispatch reduces performance with slow
consumers if
I understand correct
Thanks for the bump and for the work-around!
But - turning off async dispatch reduces performance with slow consumers if
I understand correctly, so I would prefer having it on. Is there a "better"
solution to this? Is it a bug or do I have bad config somewhere?
rajdavies wrote:
>
> Great! thx
Great! thx Benoitx!
On 9 Jul 2008, at 16:31, Benoitx wrote:
let me answer my own question... the config is in an xml file...
this works:
vm://localhost?create=false&async=false
We'll get back to the list if it re-occurs but... it seems to have
fixed the
clientID issue.
Thanks!!!
Benoit
let me answer my own question... the config is in an xml file...
this works:
vm://localhost?create=false&async=false
We'll get back to the list if it re-occurs but... it seems to have fixed the
clientID issue.
Thanks!!!
Benoit
Benoitx wrote:
>
> Thanks a lot for this.
>
> Could you confirm
Thanks a lot for this.
Could you confirm the syntax to add more than one parameter?
We already have: vm://localhost?create=false
so I tried vm://localhost?create=false&async=false but this is rejected...
Sorry, it is a very basic question...
Benoit
rajdavies wrote:
>
> work around could b
work around could be to turn async dispatch off in the vm://
transport - e.g. vm://localhost?async=false
On 8 Jul 2008, at 23:42, Benoitx wrote:
Same here.
This error seems to happen on the FIRST message sent by thread in
JBoss...
After the first message, it seems to go away... Quite a
Same here.
This error seems to happen on the FIRST message sent by thread in JBoss...
After the first message, it seems to go away... Quite annoying.
Any suggestion ? Solution? workaround?
Thanks
Benoit
Demian Mrakovich wrote:
>
> Just upgraded from 4.1 to 5.1 and get this exception now r
