I am deadly waiting for solution or a work around to this problem.
But till now that issue created on JIRA is still open and not assigned.
--
View this message in context:
I will get a chance (hour or so) to look at this later today and see
if I can reproduce and/or diagnose.
2008/7/25 Bryan.Shaw [EMAIL PROTECTED]:
I am deadly waiting for solution or a work around to this problem.
But till now that issue created on JIRA is still open and not assigned.
--
View
We have a distributed architecture with two brokers connnected to each other
through WAN.
We configured it using network of brokers.
One producer sends messages to a distributed queue named aqueue on broker
A.
One consumer consume messages from the queue aqueue on broker B.
I thought activemq
I discovered that the message transfer between network of brokers is handled
by DemandForwardingBridgeSupport class and there is some comment on async
send mode will be assumed between brokers if the producer send the message
to the queue using async send mode which will cause small probability
It is sad that the activemq message sending is default to sync send.
So this issue is still open.
Please provide help!
Bryan.Shaw wrote:
I discovered that the message transfer between network of brokers is
handled by DemandForwardingBridgeSupport class and there is some comment
on async
This is currently only the case if you are using duplex connections -
or the message was originally sent using async send from the client
(e.g. non-persistent) - as the network tries to maintain the same QOS
as used by the original producer
cheers,
Rob
On 10 Jul 2008, at 10:34,
I am not using async send from the client.
But, I am using duplex connection because one of the two brokers do not have
fixed IP Address.
How can I avoid using duplex connnection if only one IP is fixed?
rajdavies wrote:
This is currently only the case if you are using duplex connections -
You can't avoid duplex in this case unfortunately - will see if can
get this fixed for 5.2.
Would you like to raise an issue for it - so I don't forget ?
On 10 Jul 2008, at 17:01, Bryan.Shaw wrote:
I am not using async send from the client.
But, I am using duplex connection because one of
I have already reported this issue in JIRA.
The issue key is AMQ-1845.
rajdavies wrote:
You can't avoid duplex in this case unfortunately - will see if can
get this fixed for 5.2.
Would you like to raise an issue for it - so I don't forget ?
On 10 Jul 2008, at 17:01, Bryan.Shaw
