I’ve come across a problem which has similar sounding symptoms & have done a
bit more investigation (no resolution yet though).
My problem is that when a network connector failed back to the remote broker
specified by the "priorityBackup" uri, the remote broker doesn't seem to
recognise that the c
I've come across a problem with similar symptoms & have done a bit more
investigation (no resolution yet though):
See JIRA https://issues.apache.org/jira/browse/AMQ-4720
Business Computer Projects Ltd is a limited company registered in England and
Wales.
Regis
tabish...@gmail.com wrote
> You would need to download the NMS source, and start debugging to see
> what's different. You can enable tracing on the transport layer with
> transport.useLogging=true in NMS to see each command that's sent in the
> logs and compare that to the Java or C++ client va
On 08/27/2013 09:02 AM, cannifx wrote:
Hi,
thanks for quick feedback and advises, ceposta, sadly i'm not a java guy :)
I have some additional input, for sending i use .NET Messaging API and
message do not going through brokers, then i compiled sender on c++ with
usage of ActiveMQ-CPP and it work
Hi,
thanks for quick feedback and advises, ceposta, sadly i'm not a java guy :)
I have some additional input, for sending i use .NET Messaging API and
message do not going through brokers, then i compiled sender on c++ with
usage of ActiveMQ-CPP and it works after reconnect, more then that, if i
s
So to get the best chance of getting help, I recommend you reproduce this
in a unit test. Then we will be able to see exactly what's going on and
give you the best answer. Networks of brokers can be tricky to get correct.
I would advise you take a look at this test (which has 4 brokers like
yours):
