So what exactly is the ha parameter for?
Does it treat servers somehow differently? E.g. *non-ha* pool of servers,
vs. *ha* pool of servers?
Form what I am seeing, even without it, client fails over to slave after
retrying master 5 times and then fail over to the slave... So the fail over
is someh
I realised that my original post had some omitted error traces, so I have now
corrected it.
It seems that quoted stack traces do not get posted correctly and they
result in empty space.
I have now instead just pasted text normally and marked it bold.
--
Sent from: http://activemq.2283324.n4.nabb
Phu,
You can use any shared filesystem for storing the data, but to act as the
shared lock, the filesystem must support specific lock operations. NFSv4
supports those options. NFSv3 and before does not. Other filesystems may or
may not, though your experiment makes it sound like ESXi may not.
How
The next time this happens, could you please use JVisualVM to capture a
minute or so of CPU sampling to give us an understanding of what code paths
are/aren't being executed? Please make sure that messages are coming into
the virtual topic in question during the time you do the sampling. Note
that
